Not allowing multiple users unless file opened through Access

[Degs29]

I have a database with three users, only one of whom has editing privileges. As such, I didn't see the need to setup a front end and back end (nor did I know how at the time). Anyway, that's not the issue. The database is saved on a networked computer that all users can access. Unfortunately, when accessing the database in the shared network folder, only the first user can access it. Other users will double click the file and virtually nothing happens.



However, users can instead open Access first, and open the file through the program fine. Any ideas why this would be the case and how I can have multiple users open the file from the shared folder?

[ssanfu]

The first person can do edits, everyone has read only privileges. If the dB is in shared mode and not exclusive mode.

The safest way is to split the database into a front end (FE) and a back end (BE).

The BE resides on the server or a computer that everyone can access.
EACH user has a FE on their computer.

Having more than one used using a non split dB will result in corruption. Just a question of when it will corrupt......

[Degs29]

The first person can do edits, everyone has read only privileges. If the dB is in shared mode and not exclusive mode.

The safest way is to split the database into a front end (FE) and a back end (BE).

The BE resides on the server or a computer that everyone can access.
EACH user has a FE on their computer.

Having more than one used using a non split dB will result in corruption. Just a question of when it will corrupt......

This database is rather complex. Is there an easy way to split it into FEs and a BE, or do I manually have to change control sources in the FE?

[ssanfu]

It is relatively easy to split the database. You can use the wizard or do split it manually. If you use the wizard, test is out on a backup (copy) until you feel comfortable.

To split the database manually, make a copy of the database. rename the copy - I add "BE" to the name. Rename the other database to include "FE".

In the BE -
Delete everything EXCEPT the tables.

In the FE -
Delete the tables that will be in the BE. The "front-end" database can still contain local tables for storing a user's settings or temporary data; don't delete local tables.
Create a link to the BE tables by using FILE/GET EXTERNAL/LINK TABLES.
After that, you can use the Linked table manager to relink to the BE if the BE is moved.

Here is an article on how to split a database
http://www.fmsinc.com/MicrosoftAcces...ter/index.html

I don't know how useful this video will be - he jumps around a lot - but you might look at
http://www.youtube.com/watch?v=GEMuf1FGVFQ

[Degs29]

It is relatively easy to split the database. You can use the wizard or do split it manually. If you use the wizard, test is out on a backup (copy) until you feel comfortable.

To split the database manually, make a copy of the database. rename the copy - I add "BE" to the name. Rename the other database to include "FE".

In the BE -
Delete everything EXCEPT the tables.

In the FE -
Delete the tables that will be in the BE. The "front-end" database can still contain local tables for storing a user's settings or temporary data; don't delete local tables.
Create a link to the BE tables by using FILE/GET EXTERNAL/LINK TABLES.
After that, you can use the Linked table manager to relink to the BE if the BE is moved.

Here is an article on how to split a database
http://www.fmsinc.com/MicrosoftAcces...ter/index.html

I don't know how useful this video will be - he jumps around a lot - but you might look at
http://www.youtube.com/watch?v=GEMuf1FGVFQ

Thanks very much!

I've created a test copy that'll get updated along with the original, un-split version for a short while. If everything checks out, we'll go from there.