database on multi machines

[kdspec]

I have created a shortcut which has been placed on multiple machines at work. A few of the machine (XP) have a problem opening the database from the shortcut if someone else has the database open. This problem does not occur on all machines. I have gone to the machine and used MS Explorer to find the database on the network and open it that way. Again as long as no one has the file open it is not a problem opening the database. However if the file is open on another machine it will not open. If I open from within Access it is not a problem. This does not occur with all machines but it seems to be spreading.

[emsik1001]

Hi

My personal experience is that Access will lock the database if someone is using it in design view.

Regards
Emil

[kdspec]

Hi

My personal experience is that Access will lock the database if someone is using it in design view.

Regards
Emil

It does not seem to matter. I have machines opening it in just the runtime and it seems to lock the file to the other machines. Not all of the machines just a few. Thanks KD

[DonRayner]

I have created a shortcut which has been placed on multiple machines at work. A few of the machine (XP) have a problem opening the database from the shortcut if someone else has the database open. This problem does not occur on all machines. I have gone to the machine and used MS Explorer to find the database on the network and open it that way. Again as long as no one has the file open it is not a problem opening the database. However if the file is open on another machine it will not open. If I open from within Access it is not a problem. This does not occur with all machines but it seems to be spreading.

Is the Database on a server or workstation, If it's a workstation then you're limited to 10 concurrent connections. Depending on how long it takes for the connections to be released after someone exits the database, that number could continue to drop with use.

If you have your database on a server, you would probally be better off splitting your database into a front end and back end. Leave the backend on the server and install the frontend on the individual workstations. If you are using the access user level security you will also have to leave a copy of the mdw file on the server and have the workstation shortcuts refer to that mdw in their command line.

Don