dbSeeChanges with SQL linked tables

  • Thread starter Thread starter snooka9
  • Start date Start date
S

snooka9

I'm in the process of converting my Access FE/BE setup to have an SQL BE and
I've come across the dbSeeChanges issue with recordsets. I see that I have to
add the dbSeeChanges option to the OpenRecordset command when the table has
an Identity/Autonum field, like so:

rsData = CurrentDb.OpenRecordset("SomeTable", dbOpenDynaset, dbSeeChanges)

My question is, would it have any negative side effects if I were to use
this on ALL of my Recordsets that are the type dbOpenDynaset, even the ones
that don't have an Identity field?

The reason I ask is that I have alot of different tables and alot of code
and just to get it up and running for my testing phase I'd love to just do a
Find/Replace to add in the dbSeeChanges option to ALL of my Dynasets. Then,
at some point down the road after I've worked out any other kinks I come
across, I could go back and remove the dbSeeChanges option from and
recordsets that don't actually have an Identity.

Thanks in advance.
 
As far as I know there should be no adverse impact. Why not make a
backup of the database (just in case) and then try it?

That's what I would do.

'====================================================
John Spencer
Access MVP 2002-2005, 2007-2008
The Hilltop Institute
University of Maryland Baltimore County
'====================================================
 
Back
Top