Originally posted by Paul O'Neill: This always worked with SQL2000 and jdk1.4.2_13. I'm guessing the new MS SQL2005 jdbc driver has a problem??? If I run the same code directly in SQL, there's no issue.
Has anybody got any information on this?
That means that your original driver was allowing invalid commands through. executeQuery() should not be used for an insert/update. If it worked you were lucky. However the problem is still in your code and not the configuration.