myFMbutler DoSQL remains a legendary utility tool among legacy Claris FileMaker developers seeking to bypass native relationship graph limitations through SQL. While the official myFMbutler website announced the discontinuation of active product support, the plug-in is still heavily discussed and utilized in maintenance environments. It provides direct data manipulation inside calculations using standard SQL syntax.
This review covers the core features, architectural impacts, and modern context of utilizing myFMbutler DoSQL. Core Features
The plug-in functions primarily by executing data-definition and data-manipulation queries directly inside FileMaker’s calculation engine.
Full CRUD Lifecycle Execution: Unlike FileMaker’s native ExecuteSQL function—which is strictly limited to SELECT queries—DoSQL allows developers to perform INSERT, UPDATE, and DELETE queries directly on database tables.
Context-Independent Writes: Developers can write data directly to entirely unrelated tables without needing to map out new Table Occurrences (TOs) or establish visual lines on the relationship graph.
Advanced Portal Filtering: It allows complex SQL criteria to govern portal displays, removing the dependency on heavy multi-predicate relationship filters.
Zero Driver Dependencies: The plug-in interacts natively with the underlying FileMaker database engine, requiring no external ODBC or JDBC client configuration to process statements. Architectural Benefits
The primary advantage of deploying DoSQL is the massive reduction in layout and schema clutter. In standard Claris FileMaker Pro development, performing an action in an unrelated table requires either switching layouts via script context or adding another spiderweb layer to the Relationship Graph.
DoSQL eliminates this requirement. An entire audit trail or change log system can be compiled into a single calculation string that triggers automatically upon record modification. This creates cleaner, faster-loading database structures. Performance Limitations
While powerful, developers evaluating DoSQL on older deployments must account for several structural performance bottlenecks:
The Open Record Bottleneck: Like all FileMaker SQL implementations, queries executed against a target table can face massive lag spikes or temporary hangs if another user has an uncommitted record open in that specific target set.
Syntax Fragility: Because SQL queries are written as text strings within FileMaker calculations, changing a field or table name in the native database schema will break the hidden SQL string, requiring manual code adjustments. Current Status and Modern Alternatives
Because myFMbutler officially discontinued active product support, installing DoSQL into modern, multi-user deployments introduces platform risks regarding operating system compatibility and security updates.
Leave a Reply