If you mean the function ExecuteSQL(), it was only introduced in FM12:
If you mean the Execute SQL - the script step -, then I don't know. Can you post any of the script?
You are NOT using the Execute SQL script step (https://www.filemaker.com/help/15/fmp/en/index.html#page/FMP_Help/execute-sql.html) which would be using an ODBC connection.
You are using the ExecuteSQL() function.
The function was not in use when the file was .fp7, but you are seeing this with a NEW calculation in a previously converted database, right? To see the error code you can wrap the eSQL function with another:
There may be a problem in the naming of the fields and/or tables, but any error returned will help.
Thanks, Beverly. Error 8309, checking Community info on it.
2 of 2 people found this helpful
Do you have a table occurrence called Techs in the fp7-converted file? ExecuteSQL references tables by table occurrence name, not by actual table names. So if no table occurrence in the converted file has the exact same name as the table, that could be one possible explanation.
That was it exactly, David. I had in my head you were addressing the table name rather than the TO name.
Big thanks to you both!
There is a custom function out there called SQL.Debug that will actually get FileMaker to display actual text error messages when there is a syntax error in your SQL. It's used in the DataViewer as a watch expression.
//sql.debug (_executeSQL )
//the sql call results in an error, return empty so the error will be returned
_executeSQL = "?" ; "" ;
//the sql call is executed correctly, just return the result
This function is published on FileMaker Custom Functions
to check for updates and provide feedback and bug reports
please visit http://www.fmfunctions.com/fid/335
Prototype: sql.debug( _executeSQL )
Function Author: Andries Heylen (http://www.fmfunctions.com/mid/57)
Last updated: 28 July 2012
Yes. FMPA required to install any custom function. And required for Data Viewer.
Sent from my miPhone