1 2 Previous Next 23 Replies Latest reply on Jul 21, 2017 1:15 PM by TSGal

    SQL statement length limit changes in FileMaker 10 for Execute SQL and ODBC import

    greglane

      Summary

      SQL statement length limit changes in FileMaker 10 for Execute SQL and ODBC import

      Description of the issue

      Hello,  The maximum length for SQL statements used in the Execute SQL script step and ODBC imports (scripted and manual) seems to have changed drastically. In most cases, the limit appears to be only about 4,096 characters. Here are results from specific cases I've tested:On Windows, FileMaker Pro 9 can execute a SQL insert command with over two million characters via the Execute SQL script step. This was tested with the DataDirect SequeLink 5.5 driver and a FMSA 9 data source. However, with the same ODBC driver and data source, FileMaker Pro 10 will only execute statements with up to 4,096 characters. Longer statements silently fail ( Get(LastError) = 0, Get(LastODBCError) = "", but no record created ).On Windows with the MySQL Connecter/ODBC 5.1.5 driver and a MySQL 5.1 data source, FileMaker Pro 9 can execute an insert with over 100,000 characters. However, the limit with FileMaker Pro 10 seems to be 32,766 characters. Longer statements result in an error dialog, "ODBC Error: [Microsoft][ODBC Driver Manager] Invalid string or buffer length".On the Mac side, I've tested with the Actual Technologies 2.9b driver with MySQL 5.1, the MySQL Connector/ODBC 5.1.5 driver with MySQL 5.1, and the DataDirect 5.5 driver with a FMSA 9 data source. Each of these appear to be limited to about 4,096 characters with FileMaker Pro 10. FileMaker Pro 9 is able to execute much longer statements with each of these data sources. Thanks,Greg Lane

        1 2 Previous Next