Multiple users, potential problems?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We have an Access database on a server with two desktops connecting to the
database simultaneously on occasion. Should we set the db to exclusive use to
avoid problem or can we leave it as shared. What problems could we encounter
if we use it simultaneously? The fe/be configuration sounds like it might be
too complicated.

buckeye one
 
buckeye1 said:
We have an Access database on a server with two desktops connecting to the
database simultaneously on occasion. Should we set the db to exclusive use
to
avoid problem or can we leave it as shared. What problems could we
encounter
if we use it simultaneously? The fe/be configuration sounds like it might
be
too complicated.

buckeye one
Click to expand...

You should split the database and provide each user with their own copy of
the front end. It's not complicated at all. Search the help for "split
database". There's also an excellent article here:

http://www.granite.ab.ca/access/splitapp/index.htm

HTH - Keith.
www.keithwilby.com
 
Keith Wilby said:
You should split the database and provide each user with their own copy of
the front end. It's not complicated at all. Search the help for "split
database". There's also an excellent article here:

http://www.granite.ab.ca/access/splitapp/index.htm

HTH - Keith.
www.keithwilby.com

Thanks for responding. I should split the db on the secretary's computer and manually connect the objects on her c:/ drive to the tables on the server to preserve security? When I work on the database, I just go to the shared network drive directly. If I split my connection as well, would that hurt my ability to change table structure on the shared network drive?
Click to expand...

buckeye one- David Henkle
 
David,

The "classic" setup is to have your app split with the BE on a server
available to all users and to have a development copy of your FE in your
private area. You can either then send copies of your updated FE to your
users when necessary or (and this is what I do) have a copy of your FE in a
read-only "public" folder and have your users' shortcut point to a batch
file which copes the FE from the public folder to the C drive, then opens
it.

You will still need to have a method of removing all users if you need to
update the BE. The way I do it is to have a "shutdown" table, which code in
my main form's timer event checks every 10 seconds. If the code finds a
certain entry in the table then an action is performed (eg DoDmcd.Quit).
This table is also checked on startup of the app and prevents users logging
in if a certain entry is found. You could even have the shutdown table in a
separate BE just to be sure they don't create the ldb for your main BE when
attempting to log on.

HTH - Keith.
www.keithwilby.com
 
Back
Top