Comments on: Executing direct SQL statements

By: Tommy Skaue

Tommy Skaue — Wed, 08 Jun 2011 11:51:38 +0000

I had to wrap my code with ttsbegin and ttscommit in order for this to work.

By: Klaas Deforche

Klaas Deforche — Tue, 16 Nov 2010 14:04:01 +0000

Hi Jan,

Sorry, I haven’t used a File DSN yet, so I can’t help you with that. I always use a System DSN; are you able to get it working with that?

By: Jan

Jan — Tue, 16 Nov 2010 12:19:16 +0000

HI,
Tried to use a File DSN, but no connection was made. Anything spesial to do when using File DSN?
Regards,
Jan

By: Victor

Victor — Thu, 21 Oct 2010 03:04:59 +0000

Hi Michael,

I’ve got the same issue with the executeUpdate() method always returning 0, however many rows have been updated. If you ever happen to have more info on this, I would greatly appreciate if you could share it with me. Thanks!

By: Michael

Michael — Thu, 19 Aug 2010 12:14:26 +0000

Just one comment to the executeUpdate() Method of statement class.

There seems to be (still) a bug in this method – when using it with DML (insert/update/delete) commands. The result values normally should deliver the number of affected rows. (updated, inserted, deleted)

I always get 0 as result value even if records where affected.

Any ideas how to get this number.

According to documentation in MSDN executeUpdate should return the updated row count.