ADO connection problems if I split a database?

[Guest]

I hope this makes sense, I have just started to learn this stuff.

I want to split a database and presently I have ADO connections set to
CurrentProject.Connection. IF, the database will only be used locally on a PC
(FE and BE) , will this connection string work or will I need to map the data
source for each different PC it goes on once it is split?

Also, is there a problem that I need to look out for with the curser and
lock when I use the open method to open the recordset?


So, in summary, I am assuming that all I have to do with a split database is
reset the links
to the backend tables for each PC (if drive map is different) and forget
about the ADO connection strings, cursers, etc…..I hope! Is this true?

Many thanks

 

[Brendan Reynolds]

CurrentProject.Connection will continue to work with linked tables.

The default ADO recordset type, if you accept default values for properties
and parameters, is a forward-only, read-only recordset, but that's the same
regardless of whether tables are local or linked. If your ADO code works
with local tables, then it should generally speaking continue to work with
linked tables.

 

[Guest]

Thanks Brendan!

CurrentProject.Connection will continue to work with linked tables.

The default ADO recordset type, if you accept default values for properties
and parameters, is a forward-only, read-only recordset, but that's the same
regardless of whether tables are local or linked. If your ADO code works
with local tables, then it should generally speaking continue to work with
linked tables.