Need permission to view backend of DB on network

[Steve S]

Have split db on PC 1. Copied front end to PC 2 but can't link to backend on
PC 1. I get the error message

The Microsoft Jet database engone cannot open the file\\…Twirl_be.mdb. It
is already opened exclusively by another user, or you need permission to view
its data.

the db is NOT opened by another user and I have no idea what changed about
the permissions.

Also to put a new copy of the front end on PC 2 I can't pull it over the
network, I have to push it by goint to PC 1 and doing a copy to PC 2.
Any and all help is appreciated.

 

[Tom Wickerath]

Hi Steve,

This peer-to-peer networking setup is certainly not optimum, since one of
the PCs will need to act as a file server for the other PC, while still
keeping busy with running all applications and processes for it's user.
Instead, you should have a server PC, where you copy the BE database file to,
so that both PC1 and PC2 get their data from this file server. I would think
you could get a proper file server setup without too much expense.

That said, it sounds to me like PC1 is not configured to share it's hard
drive, or at least the appropriate directories, with PC2. Can you use Windows
Explorer from PC2 to copy any files from PC1? Also, which operating systems
with service pack levels does each PC have?


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
__________________________________________

 

[Steve S]

Hi Tom,

There are 4 other access databases in the same directory as the one in
question and from PC2 I can open all of them with no problem. It is only the
backend for the one split db that I can't open across the network.

I solved tehe problem ( or just maybe covered it up) by using WinZip to zip
the backend, renamed the backend, rebooted PC1, and extracted the backend
into its original location. Now I can open the backend from any of 3
networked PCs. Go figure???

I hate 'fixes' that do not seem to make any sense but it is hard to argue
with success.

 

[Tom Wickerath]

Hi Steve,

Perhaps PC1 really did have the database opened in exclusive mode. This can
happen, for instance, if any object was opened in design view. One can also
open a database in exclusive mode by ticking an option under Tools |
Options..., on the Advanced tab (See Default open mode setting).

It may have also resulted from a locking database issue. By rebooting PC1,
you would have automatically marked a left over .ldb file as not being in
use. With Access closed on all machines that link to a BE (Back-End)
database, you should not see any evidence of a 1 KB locking database file for
the BE database. It would have the same name as the BE database, and be in
the same folder, but it would include the .ldb file extension.

Introduction to .ldb Files
http://support.microsoft.com/?id=299373


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
__________________________________________