Linked tables

[J Holtendehouzer]

I split my database into a frontend and a backend. When I install my
application as an .mde on another computer (using the package wizard/MS
installer), will it automatically update the links to the tables, or do I
have to manually do so before packaging the application?

Thanks!
Joe

 

[Allen Browne]

In your startup code, check that the data is available--typically by trying
to OpenRecordset on a uniquely named table that will not be in any other
database. If it opens okay, the data is available. If not, trigger the
FileOpen dialog asking the user to locate the data file.

There is a sample of how to do that in the module of this sample database:
http://msdn.microsoft.com/library/officedev/bapp2000/mdbdownload.htm

If the user cannot locate the file, you close the application gracefully. It
never bothers the user if everything is fine, but it handles the case where
they change servers, rename paths, etc, or even if the network is broken.

I've been taking that approach for years. I once had a user who managed to
link to a backup copy of the mdb (which did have the uniquely named table.)
Other than that it's been flawless.