Jason,

yes, a flag (or 3 perhaps for ins/del/upd) is what I had in mind.
Serg's suggestion of removing the "offending" xxxSQL property seems
ineffective to me.
First, I don't really want to loose the SQL string, as the next user
to log on might have permission to use it (without application
restart). Removing it from the query would mean I would have to store
it some place else and that's difficult from a central point
Second, when opening the query (up to) 4 statements get prepared.
Closing the dataset and reopening it causes this process to begin
again. Thus, if the 3 xxxsql statements fail (one after the other) I
would have to reopen the query 3 times, causing 7 statements to be
prepared...

Mirco