Problems with linked databases...

[ChrisM]

Hi,

I have the following setup:
Largeish(~180Mb) Access Database containing Tables. Only 1 copy of this,
kept on the server.
10 users each with their own copy of an Access Database containing queries
only with linked tables into the server 'master db'
A dotNet application on each computer that uses the local database.

Every now and then, I do a 'compress and repair' on the master database, and
this (sometimes) causes database errors in the application (Jet - Undefined
Error). The fix for this is to re-link the local databases back to the one
on the Server.

Is this a known problem/issue?
All databases are in Access2000 format, and all computers are running
Win2000 except for a couple that run WinXP, and the server which is running
WinSBS2003.

Hope that the question is clear enough, and that I have supplied enough
information. If you believe I should ask this question elsewhere, I'd
appreciate it if you could suggest a better alternative.

 

[John Vinson]

Every now and then, I do a 'compress and repair' on the master database, and
this (sometimes) causes database errors in the application (Jet - Undefined
Error). The fix for this is to re-link the local databases back to the one
on the Server.

Is this a known problem/issue?

I haven't specifically seen problems with Compact... but I've got code
in all my frontends to check a table and relink programmatically if
there are any problems. Some developers even have code that relinks
the backend every time the frontend is opened.

Check the suggestions at Tony Toews' site:

http://www.granite.ab.ca/access/splitapp/

for best practices and cautions.

John W. Vinson[MVP]