Sharing Problem

  • Thread starter Thread starter Charlie
  • Start date Start date
C

Charlie

I have an Access 2000 database on a Windows98 computer that is being accessed
by 3 XPpro computers via mapped network drive. The setup works fine except
for one glitch that is driving me crazy:

Let's call the three XP boxes Lloyd, Mae, and Charlie. If Mae has the
database open, Charlie can't open it. Lloyd and Mae can both have it open,
and Lloyd and Charlie can both have it open. If Charlie opens it first, Mae
can open it. But if Mae opens it first, Charlie cannot open it. Charlie can
navigate to the file on the mapped network drive, but clicking on it produces
no result at all if Mae has it open. All 3 can have it open as long as
Charlie opens it before Mae does. Something about Mae having the database
open prevents Charlie from opening it.

I realize this sounds like a bad logic puzzle, but it really has me stumped.
Any suggestions of a not-too-terribly-technical nature would be appreciated.
 
I have an Access 2000 database on a Windows98 computer that is being accessed
by 3 XPpro computers via mapped network drive. The setup works fine except
for one glitch that is driving me crazy:

Let's call the three XP boxes Lloyd, Mae, and Charlie. If Mae has the
database open, Charlie can't open it. Lloyd and Mae can both have it open,
and Lloyd and Charlie can both have it open. If Charlie opens it first, Mae
can open it. But if Mae opens it first, Charlie cannot open it. Charlie can
navigate to the file on the mapped network drive, but clicking on it produces
no result at all if Mae has it open. All 3 can have it open as long as
Charlie opens it before Mae does. Something about Mae having the database
open prevents Charlie from opening it.

I realize this sounds like a bad logic puzzle, but it really has me stumped.
Any suggestions of a not-too-terribly-technical nature would be appreciated.
Click to expand...

simple solution. Split the database and distribute the front ends to
each user. Put the back end on one of the XP boxes.
 
Mae may be opening the database exclusively. Watch how Mae opens the database
and see if she's using any shortcuts that might have the right command line
for exclusive OR maybe she's opening up Access first then the database. It's
possible to open exclusive by accident there to.

What's the settings under Tools, Options, Advanced tab say about Default
open mode and Default record locking.

Do all users have read, write, create, delete, or modify permissions to both
the database file and the entire folders where it resides? I bet someone
doesn't and that's the problem.
 
Hi Charlie,

This really sounds to me like Mae is opening the database in exclusive mode,
as Jerry suggested. Lloyd, Mae, and Charlie all need to have RWCD privileges
for the shared folder. If Mae is the first one in, and is unable to create
the locking database file, then it will be opened in exclusive mode. Here is
a KB article that discusses this in more detail:

Introduction to .ldb Files
http://support.microsoft.com/?id=299373

Also, verify that Mae's setting, under Tools | Options... ---> Advanced Tab
has "Shared" set as the Default open mode.

Here is an article that I have written which provides many helpful tips:

Implementing a Successful Multiuser Access/JET Application
http://www.accessmvp.com/TWickerath/articles/multiuser.htm

Each user should be opening their own copy of the "front-end" (FE)
application, which is installed on their local hard drive. Only the
"back-end" (BE) file is shared. This is commonly known as a split database.


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________
 
Default open mode is "shared"
Default record locking is "No locks"
"Open database using record-level locking" is checked (I tried unchecking,
but this had no effect.)

As I said, the database resides on a Windows98 box, and all three users are
mapping directly to the C: drive at logon, and opening the database via
desktop shortcut.
 
Splitting the database seems to solve the problem, so I guess that is the way
to go.

Thanks
 
Back
Top