multiuser access?

  • Thread starter Thread starter pnp
  • Start date Start date
P

pnp

Could i use access as a database for 2 or more users to concurrently access
it? Or is it only used as a single-user database?
 
Access has been designed for use by more than one user since its earliest
versions, so the answer is 'Yes'.

Generally, the steps and "best practices" are as follows:

1. If you have not already done so, split the application into a Front-End
and a Back-End. 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.

The number of users that can effectively and efficiently use your database
will be determined by a number of factors: the design of the database, what
the users will be doing (reading and reporting only vs. adding, editing and
deleting records), network infrastructure and setup, and the like.

Those are pretty much the high points. Post back if you need more.
 
Thank you for your detailed help.
One more question: If I use the database from an app that I've developed
will I have any problems with record locking, updates etc?
 
You're welcome.
One more question: If I use the database from an app that I've developed
will I have any problems with record locking, updates etc?

Access generally takes care of this rather well. You might also want to
open Access Help and in the "Answer Wizard" enter the words "record locking"
as the search criteria. You will see a number of additional topics that you
can review for further information.
 
I have read the response below.. I have a similar
situation, and have split the database. However now non
of my queries work as they state that the table that they
are accessing are not marked for reading. I have checked
the tables and they are marked with all privileges so I am
not sure why I am getting this error on all of my
queries? Any Ideas?
 
I am not familiar with the message you indicate you are receiving nor do I
see anything which appears relevant after searching the MS KB. Can you
post the exact error message?

Also, are you using Access Security with your database? If so, you may want
to post your question to that news group.
 
I just noticed that you posted this same question in a separate post in this
news group - and that you have received an answer from John Vinson. His
suggestion is also most appropriate.
 
Back
Top