How to make a database in multiuser?

[paxomar]

We have a Microsoft Access Database that we use here at work. The maintainance guy tried to install a new router on the network and he mesed up everything. I found the newtwork and made it work for all computers now we can access to the database but one at the time. Usually we were able to open the database at the same time all of us even with the same username.

Now we can't open it at the same time. How can I make it multiuse or something to be able to use it at the same time.

THis is URGENT because we use it all day. HELP PLEASE.

 

[BobMcClellan]

This is a simple straight forward approach....
If you want to share the data across the LAN, then
-create 2 new databases
-import all tables from existing database into one of the new dbs.
-import everything else into the other db.
Put the data .mdb on the file server
-Link the tables from the 2nd db (front end) to the 1st db (backend data db).
-put a copy of the 2nd db on each users PC.
Now each user has their own front end and they
all point to the same data back end...
hth,
..bob

 

[boblarson]

Yes, as Bob says - you need to have the database as SPLIT (backend - tables only and on the shared location) and the Frontend (everything but the tables) is a copy on EACH user's machine.

If you want to avoid the hassle of sending out a new version of the frontend everytime you update it, you can look into using my Free Frontend Auto Update Enabling tool. It is in the Access Tools section of my website (see the link in my signature).

 

[paxomar]

This is a simple straight forward approach....
If you want to share the data across the LAN, then
-create 2 new databases
-import all tables from existing database into one of the new dbs.
-import everything else into the other db.
Put the data .mdb on the file server
-Link the tables from the 2nd db (front end) to the 1st db (backend data db).
-put a copy of the 2nd db on each users PC.
Now each user has their own front end and they
all point to the same data back end...
hth,
..bob

Could you be a little more specific on each step? I'm a begginer on access. Like how to import to a nenw dbs. should I open a new databse and save it befor import it? and how do I link the tables? PLEASE???

 

[boblarson]

See if this helps:
http://support.microsoft.com/kb/304932

 

[paxomar]

[/QUOTE]

Got it, Thanks. Just to confirm the first dbs I copy the tables only and the other dbs should I link or copy everything else?

The second dbs is the one that I put on each coputer? can I put it on the server and just shortcut to all computers or I have to do one for each coputer?

 

[boblarson]

Got it, Thanks. Just to confirm the first dbs I copy the tables only and the other dbs should I link or copy everything else?

Yes, the rest would be in the second one and links to tables in the backend instead of having the tables actually in that file.

The second dbs is the one that I put on each coputer? can I put it on the server and just shortcut to all computers or I have to do one for each coputer?

Do NOT run the frontend from the server and EACH USER should have a copy on THEIR COMPUTER. Otherwise you will have problems including a much greater chance of corruption occuring and then all people will not be able to work. If one frontend goes bad when the users have it on their machine, it will only affect them and the rest can still work. You would just have to get the affected user a new copy of the frontend to replace their corrupted copy. If run from a single file, it would affect everyone if it corrupts. Access is susceptible to corruption, especially if there is a network disruption (no matter how brief) and it is more likely to have that happen if the users are using the same file. Plus Access has to run on the user's machine so everything from the frontend would need to be transferred over the network to their machine in a temporary space anyway which can lead to extra heavy network traffic and hence, slowness.

 

[paxomar]

Got it, Thanks. Just to confirm the first dbs I copy the tables only and the other dbs should I link or copy everything else?

Yes, the rest would be in the second one and links to tables in the backend instead of having the tables actually in that file.

Do NOT run the frontend from the server and EACH USER should have a copy on THEIR COMPUTER. Otherwise you will have problems including a much greater chance of corruption occuring and then all people will not be able to work. If one frontend goes bad when the users have it on their machine, it will only affect them and the rest can still work. You would just have to get the affected user a new copy of the frontend to replace their corrupted copy. If run from a single file, it would affect everyone if it corrupts. Access is susceptible to corruption, especially if there is a network disruption (no matter how brief) and it is more likely to have that happen if the users are using the same file. Plus Access has to run on the user's machine so everything from the frontend would need to be transferred over the network to their machine in a temporary space anyway which can lead to extra heavy network traffic and hence, slowness.[/QUOTE]

Oh ok, so like here at work we have 3 computers. I need to make 3 diferent frontended to put one on each coputer but all three are going to link everything to the backended. RIGHT? did I understood correct?

 

[boblarson]

It is the same frontend but just copied three times and one of the copies placed onto each machine. Once you have the master linked to the backend, you just need to copy that frontend and put that copy on one of the machines. It is already linked to the backend and so you don't need to do it again.