Multi User MS Access - Urgent

[kiransalu]

I am not an Access Programmer. I am a programmer in Visual basic and oracle. I've used Access only for Database.....

I am coming to the problem......I have been asked to develop an access application. This application should have 5 screens(forms) and access tables. 10 users will be using the application concurrently. What is the approach for access development? My assumptions in Access. Access is a desktop applition, so if i develop database and front end forms, how the users will be using the application? Do i need to install in all the users desktop. Then each user will enter in his own access application(database). What is the best way of developing access for multiple users?

Please help me.....

 

[PHV]

First, try to avoid terms like "Urgent" ...
Then do a keyword in the Access fora for be fe.

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ222-2244

 

[kiransalu]

OOPS. I apologize for that....

 

[BSman]

Put the Access back end (data, i.e. tables) and the front end on the server. Link to the tables, if possible, through a standard mapping drive letter (i.e., all users have the same drive letter mapped to the same network location), since that will run a bit faster than linking through UNC (\\servername\volumne\directory\subdirectory\...)

Access is already a multi user application. The only thing that every user must have on his workstation is a copy of the same version of Access that the application is written in.

Users can use the same form at the same time, so you don't need a separate form for each user. In fact, if the users are entering the same type of data, but, for example, different company groups, then you could have it all go in one table and include in the table a column that identifies the group. (As opposed to having a separate table for each group to capture basically the same data.)

 

[kiransalu]

That sounds great.

Can i separate Access FE and BE. I have an idea to develop forms/reports in a Access application. And the database(only tables) reside in the server,preferable a network server, where all the users are mapped to it...

I will link all the tables (from the server) to the Access FE. I will install FE in the user's machine.

Am i right here???

 

[KenReay]

Hi

Yes, sounds right

If you are using aversion of Access after A97, you can use row level locking, see tools\options for setting

Also see in help Optimistic/Pessimistic locking, based on your applications characteristics you need to make a choice on this

Regards

Ken Reay
Freelance Solutions Developer
Boldon Information Systems Ltd
Website needs upgrading, but for now -

http://www.kenneth.reay.btinternet.co.uk

UK

 

[BSman]

Actually, both the FE and the BE should be on the server. This makes updating and control of the application (FE) much easier and more effective, since everyone will definitely be using the same version of the application.

If you happen to have users with different versions of Access that will be running the same application (meaning you need a separate version for each Access version), then just put each version on the server and link each user to the appropriate version. (I've been doing this for some time now with Access 97 and Access 2000.)

Also, be sure to only put the MDE version of the application on the server for the users to use, not the MDB version. This will limit their ability to attempt to make changes (not that they would ever try....!).

The advantages to this approach are:

1. You can easily develop updates to the application, test them, and when ready just overwrite the FE application (when all users are disconnected).

2. For the occasional times you may need to make changes/additions to the BE (tables), you can sometimes make them while users are using the database (for example, when adding a new table or even modifying a table that isn't used yet). Of course, you need to plan to sometimes compact the back end and the front end to eliminate bloat.

 

[MichaelRed]

While [COLOR=blue[/color]'s suggestion re the single FE can seem to be attractive from the maintenance perspectivem it is not appreciated by the LAN Admin types, as the net traffic will increase quite a bit.

Further, the maintenance issue is not as simplistic as having the single point for updates / changes. Particularly when the app is introduced, frequent, and occassionally large, changes are expected. If there is only the single FE, you cannot effectively do the changes whil others are in the app. There are several to numerous posts detailing some efforts toward avoiuding these issues.





MichaelRed
mlred@verizon.net

 

[kiransalu]

Wow, Excellent answers by BSMAN, Kenneth and Michael. Please keep up the good work.

I have started working on Access DB with your blessings...