Why is the ExecuteSQL() function limited to SELECT statements? For that matter, why can't the ExecuteSQL  script step be directed at FileMaker without an ODBC connection? Plug-ins (some of them free!) have been accessing the full depth of FileMaker's SQL functionality for years. That the native feature should be released with less functionality has been confusing at best to developers with experience in other database technologies.