>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.

Thanks,
this helped me to understand BUT my problem is: I have a remote view and want to tableupdate it, sending a specific ID Value. Is there any chance to hook into the Tableupdate process and to send the SET IDENTITY_INSERT before (as doing it in the QA or Enterprise Manager is not doing it in the right session...)

Help?
Patrick