Multiple Users

H

Help IN

Hi, I have a contact database set up on a shared drive. There are three of
us that use the program to enter information. I can enter new info but am
unable to save it when the others have the program open. Is there a way to
solve this where we can all have full access at the same time?
 
D

Douglas J. Steele

All users require Change access (Read, Write, eXecute and Delete) on the
folder where the MDB file is located.

Hopefully you've split your application into a front-end (containing the
queries, forms, reports, macros and modules), linked to a back-end
(containing the tables and relationships), with only the back-end being on
the server. (Each user should have his/her own copy of the front-end,
ideally on his/her hard drive)
 
H

Help IN

I haven't split my database because my bosses really dont mess with anything
other than entering information into a form. And I have already created
everything. Would splitting it now cause problems with the database? Is
there anyway for us to all 3 have access and save information other than
splitting it?
 
P

Pat Hartman \(MVP\)

In a shared database, all users can add/change/delete data per the abilities
of the application. If you try to modify objects such as
forms/reports/queries, you will lock others out of the database. Only one
user can have the database open if objects are being modified.

Do you have code that is modifying objects? Are you doing it manually? If
that is the case, you MUST split your application. The back end which
contains the shared data tables will remain on the shared network drive.
Each of the three users will need a copy of the front end database stored
locally. That will allow people to change their own copy of the front end
without impacting other users. IMHO, this is really poor practice. NO ONE
should EVER be allowed to make object changes to a shared database. Only
the developer should make changes. They should be made off line and tested.
When they are ready to be distributed, the developer can replace the front
end on the server with the changed front end.
 
H

Help IN

The information in the forms is being entered manually. Would it cause
problems by splitting the database after it has been created? The others do
not mess with any design, they only enter contact info and notes on a form,
so is splitting it necessary?
 
P

Pat Hartman \(MVP\)

Splitting the database is always a good idea when sharing among multiple
users. It minimizes the risk of corruption. As to the save issue, are you
sure you are trying to save the data and not save an object. The way to
save a record in code is:

DoCmd.RunCommand acCmdSaveRecord

If you are just doing acCmdSave or any other method that doesn't
specifically mention record, you are attempting to save an object rather
than data.

Access forms natively save records when the current record pointer is used
so forms to need to specifically contain a "save" button unless it makes
your users more comfortable.
 
H

Help IN

Thank you Pat, that is exactly what I was doing saving the object. It all
makes since now. You think that I should split my database to prevent
corruption? There is a wizard for this am I correct? Splitting the database
after it is created won't be a problem. Thanks again for your help!
 
P

Pat Hartman \(MVP\)

Splitting the database has advantages such as easier front end maintenance
(you can just plop in a new database and not have to worry about
transferring data) and more stability (less prone to corruption).
 
Top