Multiple Users

[Supermansteel]

I have Access 2003. In my work environment we run a total of 30 tests between 5 people in my department. I am creating a database to combine all 30 tests so that way we can compile our results for all 30 tests in a monthly report. Which is becoming very complicated in itself because every test is different but that is a seperate issue. However, would this cause problems if more than one person is in the database at the same time trying to add there testing information. Or is there a way of creating the database so that this wouldn't be an issue with multiple users?

[Megalog]

I have Access 2003. In my work environment we run a total of 30 tests between 5 people in my department. I am creating a database to combine all 30 tests so that way we can compile our results for all 30 tests in a monthly report. Which is becoming very complicated in itself because every test is different but that is a seperate issue. However, would this cause problems if more than one person is in the database at the same time trying to add there testing information. Or is there a way of creating the database so that this wouldn't be an issue with multiple users?

Are you running a split DB? Do the test results share the same tables?

[Supermansteel]

Are you running a split DB? Do the test results share the same tables?

no I am not running a split DB.
They wouldn't using the same reports or tables.
The only reason why I am putting all 30 tests together is so that I can spit out a monthly report to reflect all 30 tests. Would it be better to have each test have there own DB and then build one main one that pulls in all the different tests into one report or the way I am doing it (in one DB)?

[Minion]

There's a number of ways to do this, and by no means am I the expert on it (still learning myself). However, from what I have read (and used) it seems the best method to do this if the users aren't going to be using the same tables is to create a central backend that contains all the tables. Then each user would have a seperate front end that links to their needed tables. Provided that the locks and permissions are set correctly this should allow five users to access the information with little to no problems. Primarily the issues occur when the users are trying to access the same information.

Hope this helps.

- Minion -

P.S. Front End / Backend Design is easy in Access using the link table wizard.

[Supermansteel]

There's a number of ways to do this, and by no means am I the expert on it (still learning myself). However, from what I have read (and used) it seems the best method to do this if the users aren't going to be using the same tables is to create a central backend that contains all the tables. Then each user would have a seperate front end that links to their needed tables. Provided that the locks and permissions are set correctly this should allow five users to access the information with little to no problems. Primarily the issues occur when the users are trying to access the same information.

Hope this helps.

- Minion -

P.S. Front End / Backend Design is easy in Access using the link table wizard.

thanks, so this process would be able to create 30 front end databases to input the data and will be linked to the Backend for final analysis.

[Minion]

Essentially yes. The backend would store the tables themselves that all the information is stored in. Then the users would have seperate (or share) front ends where all the queries and forms would reside calling upon linked tables verses local tables. Then for yourself you could create a personalized front end that would allow you to acces and generate all the necessary reports without the other users having access to that feature.

If the sharing of information or forms is not an issue just make one back end on a mapped (or unmapped if you want to set the paths for each front end individually) location and a one front end. Then each user can go out to the location and copy the front end to their local machine. As long as links were created using a static path that is identical between machines (ie a mapped drive) the front end can reside anywhere on the individual machines. This will save you from having to create multiple front ends yourself, as long as the user makes sure to use the right form for their information.

Let me know if you have any other questions. In the mean time you might check out the following site for an introduction into split database design.

Split DB Design

Hope all this helps.

- Minion -

thanks, so this process would be able to create 30 front end databases to input the data and will be linked to the Backend for final analysis.

[Supermansteel]

Essentially yes. The backend would store the tables themselves that all the information is stored in. Then the users would have seperate (or share) front ends where all the queries and forms would reside calling upon linked tables verses local tables. Then for yourself you could create a personalized front end that would allow you to acces and generate all the necessary reports without the other users having access to that feature.

If the sharing of information or forms is not an issue just make one back end on a mapped (or unmapped if you want to set the paths for each front end individually) location and a one front end. Then each user can go out to the location and copy the front end to their local machine. As long as links were created using a static path that is identical between machines (ie a mapped drive) the front end can reside anywhere on the individual machines. This will save you from having to create multiple front ends yourself, as long as the user makes sure to use the right form for their information.

Let me know if you have any other questions. In the mean time you might check out the following site for an introduction into split database design.

Split DB Design

Hope all this helps.

- Minion -

wow.....that helps alot thank you very much

[MMcCarthy]

wow.....that helps alot thank you very much

In theory with only 30 users you could also use just the one front end on the network and set the database to shared (tools - options - advanced). However, as Minion says it would be more efficient to have multiple frontend copies.