Patrick,

There can be only one SET IDENTITY_INSERT ON per session. QA is a separate session and can have it's own table with SET IDENTITY_INSERT ON. If another table has SET IDENTITY_INSERT ON, SQLEXEC() will return -1 and you can use AERROR() to get detailed odbc error and parse the name of the current table with SET IDENTITY_INSERT ON from it.

>>How do you know that it doesn't work for you?
>
>As SET IDENTITY_INSERT is able to be ON only for one only table of the database, I checked wether it was on in trying to set it from my Query Analyzer to ON for another table.
>
>I set it to Table1 (in Query Analyzer). I got a response that it worked. I Set it to Table2. I get the response that another table is set on ON.
>
>Than I did the same with setting table1 to ON from SQLEXEC. Than I set it to ON for Table2 in Query Analyzer and this time, unfortunately, id didn't complain that it was set to ON for another table.
>
>I'm not sure if there is another way within Sql Server to straight ahead if there is a table that has the IDENTITY_INSERT setting to ON and if so which is the name of the table (something like the SET(something)-Functions in VFP)?