R
RichB
We have an Access Database (back end) that is being used
by several end-users (front end) on various network
drives throughout the company. We didn't use the
database splitter to create the front-end MBD's. Instead
we mapped to the folder containing the tables for
linking. This process has been working fine for almost
eight months.
Our problem is that over the past several days, the .LDB
file has been appearing on the back-end file (where the
tables reside) rather than in the folder containing the
users copy (linked tables) of the database. This causes
everyone to be locked out when a query is being run or
table opened on the user's desktop. Has anyone
encountered this problem, and if so how can we fix it?
by several end-users (front end) on various network
drives throughout the company. We didn't use the
database splitter to create the front-end MBD's. Instead
we mapped to the folder containing the tables for
linking. This process has been working fine for almost
eight months.
Our problem is that over the past several days, the .LDB
file has been appearing on the back-end file (where the
tables reside) rather than in the folder containing the
users copy (linked tables) of the database. This causes
everyone to be locked out when a query is being run or
table opened on the user's desktop. Has anyone
encountered this problem, and if so how can we fix it?