SET NOCOUNT ON

QwiqBart · Post by **QwiqBart** » Mon 10 Apr 2006 03:33

Hi,
When I SET NOCOUNT ON before applying updates I get the message 'record not found or changed by another user'. When I not issue this statement everything works fine. Is this a limitation of dbxpress ?

Jackson · Post by **Jackson** » Mon 10 Apr 2006 09:08

When SET NOCOUNT is ON, the count of rows affected by a SQL statement is not returned.
dbExpress raises exception 'Record not found or changed by another user' when RowsAffected < 1.
Set option NOCOUNT to OFF.