Exclusive access to database

L

Larry G.

I know that when there is more than one person in the database at a time, one
can't make new objects and expect save them. I have a person in the database
doing data verification but I need to be creating the Macros and switchboard
while she is doing that. Can I do all of that in a copy of the database that
I made this morning and then merge them back together this afternoon without
loosing any data correction she makes and not loosing the work that I do?
 
6

'69 Camaro

Hi, Larry.

One of the reasons for splitting a mulituser database is ease of
maintenance. The most important reason, of course, is that it reduces the
likelihood of corruption. These are two very good reasons for you not to
allow users and developers to share the same database file on the networked
server. For more information, please see the tip on split databases on the
following Web page:

http://www.Access.QBuilt.com/html/gem_tips.html#SplitDB

And one can automate the distribution of the new front end with Tony Toews's
autofe utility. Please see the following Web page for more information:

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

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address so that a message will
be forwarded to me.)
- - -
If my answer has helped you, please sign in and answer yes to the question
"Did this post answer your question?" at the bottom of the message, which
adds your question and the answers to the database of answers. Remember that
questions answered the quickest are often from those who have a history of
rewarding the contributors who have taken the time to answer questions
correctly.
 
T

Tom Wickerath

Hi Larry,

You can very easily do this, as long as you are not making design changes to
the tables, if you first split your database into two .mdb files: a front-end
(FE) and back-end (BE). The BE .mdb file contains only the tables with the
shared data, and is placed on the file server. The FE .mdb file contains
everything else: queries, forms, reports, macros, modules and any local
(non-shared) tables. A copy of the FE .mdb is installed on each user's local
hard drive. There is a database splitter wizard that will assist you: Tools >
Database Utilities > Database Splitter.

Other steps that you should take to help insure success of a multi-user
application include disabling Name Autocorrect, setting subdatasheets to
[None] and opening a single connection to the BE database (for starters).

BUG: Slow performance on linked tables in Access 2002 and Office Access 2003
http://support.microsoft.com/?id=275085

Slow performance when user opens an object with Name AutoCorrect enabled in
Microsoft Access
http://support.microsoft.com/?id=290181

Keep a persistent connection open
http://www.granite.ab.ca/access/performanceldblocking.htm
http://support.microsoft.com/?id=303528#15
http://www.fmsinc.com/free/newtips/Access/accesstip36.asp


Tom

http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

:

I know that when there is more than one person in the database at a time, one
can't make new objects and expect save them. I have a person in the database
doing data verification but I need to be creating the Macros and switchboard
while she is doing that. Can I do all of that in a copy of the database that
I made this morning and then merge them back together this afternoon without
loosing any data correction she makes and not loosing the work that I do?
 
J

John Vinson

I know that when there is more than one person in the database at a time, one
can't make new objects and expect save them. I have a person in the database
doing data verification but I need to be creating the Macros and switchboard
while she is doing that. Can I do all of that in a copy of the database that
I made this morning and then merge them back together this afternoon without
loosing any data correction she makes and not loosing the work that I do?
Click to expand...

No.

Instead, use Tools... Database Utilities... Database Splitter Wizard
to split the database into a "backend" containing the tables, and a
Frontend containing the macros, switchboard, forms, and other code.
Each of you should have a copy of the frontend, linked to the tables
in the shared backend.

When you have the new spiffy frontend working, you can simply delete
her frontend database and replace it with the new one - the data is
safely in the backend.

John W. Vinson[MVP]
 
Top