Moving Access from single PC to networked multi-user

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

RC - 08 Oct 2004 16:36 GMT

I am creating an Access 2002 database that I want to run from a single
PC until I get everything working ok. I would like to get all the
tweaks worked out and add or delete any features that users notice
after they start using the database. Then the database will need to
move to a network so that the one main table in the database can be
edited and have information added to the table by about 10 different
users. I plan to split the front-end/back-end, and put the back-end
on the network server and then either have each user run the front-end
from the network or put the front-end on each users PC.
Anyone have any suggestions, things to consider? Do I have to be
careful using RecordsetClone instead of Recordset? Do I need to set
any settings regarding locking records or anything?

Reply to this Message

Van T. Dinh - 09 Oct 2004 01:07 GMT

* Each user should have a copy of the Front-End on his/her PC. Tony Toews
has "AutoFE" that can automate the Front-End updating process. See:

http://www.granite.ab.ca/access/autofe.htm

* You may want to compile the Front-End into MDE format.

* If you use Seek on your Recordset, you will need to change the code
slightly (since Seek doesn't work on linked Tables) or use FindFirst
instead.

I am sure others will have more ideas ...

Signature

HTH
Van T. Dinh
MVP (Access)

> I am creating an Access 2002 database that I want to run from a single
> PC until I get everything working ok. I would like to get all the
[quoted text clipped - 8 lines]
> careful using RecordsetClone instead of Recordset? Do I need to set
> any settings regarding locking records or anything?

Reply to this Message

Larry Linson - 11 Oct 2004 02:53 GMT

> ... I plan to split the front-end/back-end,
> and put the back-end on the network server
> and then either have each user run the front-end
> from the network or put the front-end on each users PC.

Put the front end on each user's PC... the only exception is if you are
using WTS or Citrix, in which case a copy of the front-end should be in a
separate folder for each user, so there still will not be multiple users
logged in to the same copy.

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. And, for goodness sake, follow Van's
advice: 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

Reply to this Message