Article ID: 195226 - View products that this article applies to.
This article was previously published under Q195226
When you run an action query by using Data Access Objects (DAO) and the Microsoft Jet database engine against an ODBC table, if you specify the dbFailOnError argument, the RecordsAffected property always returns 0, regardless of the number of records affected by the statement.
This is a confirmed problem in Microsoft Jet database engine versions 3.5 and 3.51.
To resolve this problem, do one of the following:
Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.
When you run an action query, you can find out how many records were affected by examining the RecordsAffected property of the Database or QueryDef object. If you specify the dbFailOnError argument so that you can trap for errors, the Microsoft Jet database engine incorrectly returns 0 for the RecordsAffected property.
Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.
Steps to Reproduce Problem
Article ID: 195226 - Last Review: January 23, 2007 - Revision: 4.3