PC Review


Reply
Thread Tools Rate Thread

dbSeeChanges with SQL linked tables

 
 
snooka9
Guest
Posts: n/a
 
      8th Aug 2008
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.


 
Reply With Quote
 
 
 
 
John Spencer
Guest
Posts: n/a
 
      8th Aug 2008
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
'====================================================


snooka9 wrote:
> 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.
>
>

 
Reply With Quote
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Re: dbSeeChanges problem in Access with linked SQL Server table Sylvain Lafontaine Microsoft Access ADP SQL Server 1 5th Jan 2010 06:58 PM
Re: dbSeeChanges problem in Access with linked SQL Server table Debra Microsoft Access ADP SQL Server 0 5th Jan 2010 07:18 AM
Appending Records from Linked Tables to the *Real* Linked Tables tbl Microsoft Access Queries 2 22nd Jun 2006 01:42 AM
Linked SQL tables and dbSeeChanges? Jefferson Berlin Microsoft Access Forms 2 4th Dec 2003 07:55 PM
Changing paths of linked tables without Linked Table Manger Ilka Microsoft Access Database Table Design 0 30th Jul 2003 01:43 AM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 01:05 AM.