Adobe Community: Message List - Executing the SQL statement is not allowed - Error

Re: Executing the SQL statement is not allowed - Error

forums_noreply@adobe.com — Tue, 11 Mar 2014 11:42:39 GMT

To help any searchers, please kindly mark the answer as correct.

Re: Executing the SQL statement is not allowed - Error

forums_noreply@adobe.com — Mon, 10 Mar 2014 15:59:47 GMT

Since this is the first google result for this error message I thought I'd also add that you will get this error message if the Datasource explicitly disallows the type of SQL statement you're attempting to run. For example if you're attempting to run an UPDATE statement, and the UPDATE checkbox is not turned on, then you will get this error .

To find this setting, edit the DSN and click the "Show Advanced Settings" button.

Re: Executing the SQL statement is not allowed - Error

forums_noreply@adobe.com — Wed, 03 Mar 2010 18:20:29 GMT

SOLVED: I decided to enter this in here, just to get it into web searches for others since I couldn't find anything.

- I was calling a function for one of the values in the query: get_db_status_code("initialize") Apparently CF parses the query to see if it's allowed BEFORE it runs the CFML in it, so something in that function name, or the parameter "initialize" was a key word that CF doesn't allow. I moved the function call outside of the query and loaded a temp variable for use in the query and it then worked.

Executing the SQL statement is not allowed - Error

forums_noreply@adobe.com — Wed, 03 Mar 2010 18:20:09 GMT

I am getting "Executing the SQL statement is not allowed" for an INSERT cfquery that I'm running. I checked the usual suspects:

- DSN allows INSERT

- I've seen reports online where certain field names or values are considered key words, so for protection CF blocks the query in this way (it would be nice if there was a different error message when it gets blocked this way vs. the DSN doesn't allow INSERT error message). The field names and values were all benign strings, so it didn't seem like that.

I took the same string for the query and ran it on another page and it ran fine (same DSN, too).