Skip to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Leaderboard

Popular Content

Showing content with the highest reputation since 02/15/2026 in all areas

  1. See the attached demo. A few notes: The script here is triggered on object exit. The default height is hard-coded into the script. The default height was measured using GetLayoutObjectAttribute() when the field is empty and active. This is different from the height dimension shown in Layout mode. This simple implementation has a flaw: if you edit an overflowing field and shorten the text so that it no longer overflows, the script will still mark it as overflowing. That's because the field only expands as you type, not shrink as you delete. To get the correct result, you would need to re-enter and re-exit the field. MeasureOverflow.fmp12
  2. MY-MCP vs OttoFMS MCP — A Head-to-Head Comparison With OttoFMS recently launching their MCP server feature, I thought it was worth comparing it against MY-MCP. Both connect AI clients like Claude to FileMaker data — but they take fundamentally different approaches. The Key Philosophical Difference OttoFMS MCP is a script gateway. The intelligence lives in your FileMaker scripts. It exposes your existing scripts as MCP tools, configured through the Otto Console GUI — no code required on the MCP side. MY-MCP is a query engine. The intelligence lives in the server itself. Schema discovery, OData query building, field quoting, date normalization, multi-tenant switching, and LLM-optimized output all happen automatically — no FM scripting required to get started. ( 1 script that returns DDL) Where OttoFMS Wins Write operations out of the box (create, update, delete via FM scripts) No code needed — GUI configuration Server-side hosting — no local install per user Where MY-MCP Wins Zero-config querying — connect and immediately query any table Automatic schema discovery at runtime Multi-tenant — one server, multiple FM databases In-memory analytics without additional FM round trips Bottom Line: They're Complementary Use MY-MCP for reads, discovery, and analytics. Use OttoFMS for write operations via existing FM scripts. They solve different problems and pair well together.
  3. Nick Hunter is starting a multi-week FileMaker LiveStream event on supercharging imports with MBS. We kick off Day 1 today at 1PM Pacific! Register for the LiveStream: https://fmtraining.tv/register.php?eventid=1116817859356653838668455889686670314554342801106723282545 If you miss a day, not to worry. We'll be uploading each stream with a unique title so you can find the topics that matter the most to you. [email protected] www.FMTraining.TV www.FMStartingPoint.com www.rcconsulting.com
This leaderboard is set to Los Angeles/GMT-07:00

Important Information

By using this site, you agree to our Terms of Use.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.