how to allow multiple users

  • Thread starter Thread starter Paul
  • Start date Start date
P

Paul

Hello folks,
How can I allow multiple users to use the same Access database? Here's the
scenario. One department always has the input form open but in the current
setup we have to close it when someone else on another computer needs to get
to the data. How can the input forms stay open on one computer but anyone
else on other computers can run reports, etc. at the same time? I'm trying
to figure out how to do this without using any outside tools like VB. Can
anyone help?

thanks
paul
 
How can I allow multiple users to use
the same Access database?
Click to expand...

There's an introductory presentation on Access in a Multiuser Environment
that I did for my user group that you can download from
http://appdevissues.tripod.com. It will identify topics that I thought
worthwhile to discuss, and a bit more. The best collection of detailed
information and links on the subject of Access in the multiuser environment
is at MVP Tony Toews' site, http://www.granite.ab.ca/accsmstr.htm.

Larry Linson
Microsoft Access MVP
 
Paul,

Generally, the steps are as follows:

1. If you have not already done so, split the application into a Front-End
and a Back-End. The Database Splitter utility found at Tools|Database
Utilities|Database Splitter is one way to do this. The Front-End (FE) will
contain all Queries, Forms, Reports, Modules, Macros and local-use tables.
The Back-End (BE) will contain all tables to be shared among users.

2. The BE will reside in a folder on your server, where full permissions
for each user will be granted (Read, Write, Create, Delete, Execute).

3. In the FE, Link to the tables in the BE. To avoid problems with
changing drive mappings, link to the BE tables using the full UNC, starting
with My Network Places and drilling down through folders until the actual
database name of the BE is found.

4. An individual copy of each FE will reside on each user's computer. For
ease of distributing updates to FEs, see:
http://www.granite.ab.ca/access/autofe.htm which describes an AutoUpdater
for front-ends, developed by Access MVP Tony Toews.

5. Additionally, a copy of the most current FE in use by users should be
kept on the server. You will do your maintenance/update programming on your
own copy of the FE on your own computer. When updates are ready to be
distributed, you'll copy your modified FE to replace the one on the server.

Those are pretty much the high points.
hth,
 
Back
Top