>I know you found your solution, but I encountered this error recently and it was because my SQLGETPROP(0, 'Transactions') was somehow set to 0. When I set it back to 1 (default), I no longer had the problem. The zero setting was behaving like setting 2 for manual transactions. So I had to issue either a SQLCOMMIT() or SQLROLLBACK(). Just a guess, but using TABLE buffering may also help.

On the mark, Mark.

In this case connection 0 has not been defined and SQLGETPROP(0,'Transactions') is 0. I created a connection and saved its number in a variable. SQLGETPROP(1,'Transactions')=1, the default. However, I later reset the variable with the connection number back to 0 !

Thanks,

Alex