John said:
I have a shared Access file on a network with 3 potential users -
call them User A, User B and User C. When User A opens the file, no
one else can access it and there is no Access Lock file that appears
on the network. Users B and C can coexist in the file simulaneously
(and an Access lock file appears) but User A cannot get in the file
whenever either B or C are in it.
Is there something wrong with the Office 2000 setup on User A's PC?
Or is there a problem at the file itself? Any suggestions?
When Access opens a file, it can open it in a shared mode or an
exclusive mode. Exclusive mode keeps others out so changes to design can
take place.
When opening Access:
Do one of the following:
Double-click the database.
To open the database for shared access in a multiuser environment, so you
and other users can read and write to the database, click Open.
To open the database for read-only access so that you can view it but cannot
edit it, click the arrow next to the Open button, and then click Open
Read-Only.
To open the database with exclusive access, click the arrow next to the Open
button, and then click Open Exclusive.
To open the database for read-only access and also prevent other users from
opening it, click the arrow next to the Open button, and then click Open
Exclusive Read-Only.
It is possible to set open exclusive as the default. It sounds like
your problem user has unknowingly done that.
Since you now have data on different machines and I am going to guess
that the data is not the same on each of those machines, you will need to
combine most, if not all of that data onto one copy of Access. This will be
complicated if the tables and data are not formatted exactly the same, For
example 123 in one data base may be text and it may be a number is a
different machine. One may use Three fields for a name FirstName, IM and
LastName and another may put it all in one field.
I suggest you start by deciding exactly how you want the final product
configured and then how you are going to get all that data into that one
database in the same format. Your final design may not be the same as any
of the existing designs.
Next you need to decide the split. What parts of the database will be
on the "server" and will be called the Back end database from now on and
which parts will be on each user's machine and will be called the front
ends. The back end should hold all data that is shared and may be changed
by the users. It should also contain all or most data that more than one
user will need access to and may be changed by you from time to time. Most
other data that does not change or that will only be used by that particular
user should be on the Back end databases on the users machines.
For example you may have all the sales made by a unit on the back end
along with the price list. The sales may been to be shared by everyone so
they all know what has been done or pending. The price list may not be a
field they will change, but you may need to change to assure everyone has
the same current price available.
Each individual machine may have something about your company like
addresses that does not change or even product descriptions etc. You may
want each user to be able to store personal information about customers like
their kids names or shared information about sports teams or you may want to
put this on the server so everyone will have this information.
This is an art form and a science to get this part of the planning
designed and will be an ongoing job and should include the users in the
planning.
Access works best if it does not need to move a lot of information over
the LAN which means static data is best kept on the front end databases.
Also kept on the front end machines will be most forms, reports queries etc.
This will allow the whole system to work faster and in some cases allow for
customization of some forms reports etc.
This may seem like a lot of work and off the point of the question you
were asking, but it is very important that this part of the job be done
first and right.
Next is the mechanics of setting up the back end on the server, dumping
in the data and putting the front end copies on each user's machines and
assuring that the links work. Access has a built in database splitter that
may make this part of the job (moving from a single database with all the
data and forms etc. to two databases a front end and a back end.) easier.
Look under the Tools menu for it.
Splitting a database can be a big job, but done right everyone will
thank you and wonder how they did their jobs without it.
Note: back ups become more important here. If you LAN does not support
automatic backups you should provide a method of backing up the data, even
if that means you do it manually.
