Sharing Databases

[cpinney1120]

I need help on sharing databases. I have a database located on a server that I want several people to be able to be in at a time and can not remember how to arrange that. Currently, some people just can not get in while others can. Can anyone help me please?

 

[Scooterbug]

You need to split the database into a front end/back end. You then provide each user with their own copy of the front end.

back end should only contain the tables and nothing else. The front end will contain the forms, queries, reports and modules. Link the tables from the back end to the front end.

There is a wizard that will split your database for you and set it up as described above. In Acess2003, it's under Tools --> Database Utilities

 

[MSAccessRookie]

I need help on sharing databases. I have a database located on a server that I want several people to be able to be in at a time and can not remember how to arrange that. Currently, some people just can not get in while others can. Can anyone help me please?

Scooterbug provided excellent advice as to how to share the database, but your post may have indicated something else that you need to consider as well.

You said:

"Currently, some people just can not get in while others can"
​

This could indicate that some of the users may also not have proper access to the server where that database is stored, and even when it is split, these users may continue to have problems. You may need to check with your network group to verify that alll of the users have the proper access the necessary server(s).

 

[cpinney1120]

Thank you! Will this allow multiple to access and add/view records simultaneously without locking up the system? Do I need to change permissions?

 

[cpinney1120]

Thank you! I appreciate your response. In this case, the other users Access programs on the shared all the time but using this "ACCESS" database is new. Could that effect it?

 

[MSAccessRookie]

Thank you! Will this allow multiple to access and add/view records simultaneously without locking up the system? Do I need to change permissions?

Scooterbug's advice will help to allow multiple to access and add/view records simultaneously without locking up the system.

As far as whether you need to change permissions or not, that may wind up being on a user to user basis. If any users have problems using the upgraded database, compare them to users that do not have access and make the necessary rights modifications.

 

[cpinney1120]

Ok, so I "split" the database and it is on a server in another state. Me and my college here in this state can access the db at the same time but when I tested adding someone from the other state and she can not get in unless we are out. After she is in, we can get in but not if we are in first. Please help! I really appreciate all the advise from this forum. It has been about 8 years since I've done this and can not remember all the "quirks".

 

[MSAccessRookie]

Ok, so I "split" the database and it is on a server in another state. Me and my college here in this state can access the db at the same time but when I tested adding someone from the other state and she can not get in unless we are out. After she is in, we can get in but not if we are in first. Please help! I really appreciate all the advise from this forum. It has been about 8 years since I've done this and can not remember all the "quirks".

You stated that you have split the database. Please verify that each of the following statements is true, and indicate any differences.

1. Your database is now in two pieces:
   1. A Front End containing the Forms, Queries, Macros, and VB Code Modules that exists on each workstation or laptop that belongs to a user of the database. The users MUST NOT be Sharing the Front End
   2. A Back End containing the Tables that exists on a server located in another state.
2. All Users of the Database have equal access to the directory where the Back End of the Database is stored.

Once the basics have been validated we can continue searching for the cause of your problems.

 

[cpinney1120]

I thought we were to share the front end? Should I be making copies of the front end on the desktop of each pc? NOT a shortcut, but a copy? 3 of us have to remotely log on the the server....?

 

[MSAccessRookie]

I thought we were to share the front end? Should I be making copies of the front end on the desktop of each pc? NOT a shortcut, but a copy? 3 of us have to remotely log on the the server....?

That is absolutely correct. Each user will require their own copy of the Front End. While the copy of the Front End can be located almost anywhere on the network, it should be on their desktop, because one of the highest Traffic Areas for a database is loading and processing Forms, and this should be done locally to limit the network access required to use the database.

 

[srs09]

I am just finishing up my first real database and getting ready to put it on a shared network drive and be done, then I read this:

Congratulations! Your database has become so popular that others would like to use it. Just copy it to a shared location on the network and create shortcuts, right? Wrong! This is perhaps the largest cause of Access database corruption. Multiple users accessing the same .MDB at the same time is just asking for problems.

-http://www.utteraccess.com/forums/showflat.php?Cat=&Board=53&Number=1264601

Front End? Back End?!

Will my database allow multiple user access (2-5 concurrent users) without problems if I were to drop it into a shared network location? Or is this FE and BE business unavoidable, even for such a small user base?

 

[MSAccessRookie]

I am just finishing up my first real database and getting ready to put it on a shared network drive and be done, then I read this:

Front End? Back End?!

Will my database allow multiple user access (2-5 concurrent users) without problems if I were to drop it into a shared network location? Or is this FE and BE business unavoidable, even for such a small user base?

If your users are sharing One single copy of your Access Program, then you need to change your method of database usage, because that is not a good idea, and could soon lead to trouble. Please read ALL of the posts in this thread, follow the advice given, and then let us know if you have further questions.

 

[srs09]

If your users are sharing One single copy of your Access Program, then you need to change your method of database usage, becasue that is not a good idea, and could soon lead to trouble. Please read ALL of the posts in this thread, follow the advice given, and then let us know if you have further questions.

Have successfully created FE/BE.

 

[gemma-the-husky]

did you mention earlier that your users were in different states?

if so, then be aware that running an access database over a WAN will not perform well. to try to get round performance probelms, you need to use advanced techniques to limit the amount of data required to move around the network.