You must use the dbSeeChanges option with OpenRecordSet whenaccessing a SQL Server table that has an

  • Thread starter Thread starter iccsi
  • Start date Start date
I

iccsi

I got following error message when I migrate my MS Access backend to
SQL Server backend.

Once I added dbSeeChanges option, the programs works.
The only thing is that I had dbFailOnError option which does not allow
me to have 2 options.

Is it possible to have dbFailOnError and dnSeeChanges 2 optins
together, because I want to the application stop when any errors
during open recordset.

Your help is great appreciated,


You must use the dbSeeChanges option with OpenRecordSet when
accessing a SQL Server table that has an IDENTITY column
 
I got following error message when I migrate my MS Access backend to
SQL Server backend.

Once I added dbSeeChanges option, the programs works.
The only thing is that I had dbFailOnError option which does not allow
me to have 2 options.

Is it possible to have dbFailOnError and dnSeeChanges 2 optins
together, because I want to the application stop when any errors
during open recordset.

Your help is great appreciated,


You must use the dbSeeChanges option with OpenRecordSet when
accessing a SQL Server table that has an IDENTITY column
Click to expand...

These flags are bitmapped: dbFailOnError is 128, dbSeeChanges is 512. So you
can pass them both together by just adding them:

DoCmd.OpenRecordset ..., dbSeeChanges + dbFailOnError

You can even add other flags such as dbAppendOnly or dbDenyRead etc. in the
same way.

--

John W. Vinson [MVP]
Microsoft's replacements for these newsgroups:
http://social.msdn.microsoft.com/Forums/en-US/accessdev/
http://social.answers.microsoft.com/Forums/en-US/addbuz/
and see also http://www.utteraccess.com
 
Back
Top