2 out of 17 users lock database using runtime

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

Guest

I have an application that opens a form when Access opens. I have 17 users.
Several use runtime 9.0. I have 2 users (using runtime) that lock the
database and others can not open it if one of these 2 users opens it first.
When these 2 users open it first they get a message stating that any changes
they make may not be saved. When they click OK, they can continue and can
make changes that are saved. (Doesn't make sense to get the message)

If another user opens the database first, the 2 problem users can open it,
they don't get the message and they can use the database. All users can
also open the database while these individuals have it open as long as the 2
problem users didn't open it first.

It appears that the settings on these 2 computers are the same as other
users that don't lock the database. All users go to the same form when the
database opens. The 2 problem users (and other users) are using Windows XP
pro.

This has become very frustrating. Please help.

Thanks
 
I just confirmed that all users have create, read, write and delete
permissions for the folder the database resides in.

Everyone accesses the database through the same front-end on the server.

An ldb file is created in the database folder whenever the database is
opened regardless of who opens it.

The 2 users have runtime (like most other users) and open the same form as
all other users.

Please help.
 
We have been using the current application and setup (1 front-end) for about
4 years. Why would this now become a problem?

Rick
 
In other words, OP, split the db into a so-called "front end/back end"
structure. The FE contains all of the forms, reports, macros & modules,
but no actual tables; it just has /links/ to the actual tables in the
BE. The BE contains just the tables. There is a single BE, on the
server. Each user has their own copy of the FE, on their own PC.

HTH,
TC
 
We have been using the current application and setup (1 front-end) for
about
4 years. Why would this now become a problem?
Click to expand...

I don't know that I could answer that for you, since I don't have enough
information about your network and/or user setup. What you've been doing for
4 years is ill advised and I would change it, even if it's not the source of
your problem. Having all users open a single frontend on a server can lead
to corruption and that may be why you are seeing this problem now.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Big List: www.ltcomputerdesigns.com/JCReferences.html
 
We have the FE and BE in the same directory on the server.

If the FE is moved to everyone's local PC, how does one insure the links to
the tables don't get broken?
 
RW said:
We have the FE and BE in the same directory on the server.

If the FE is moved to everyone's local PC, how does one insure the
links to the tables don't get broken?
Click to expand...

Create the links using a UNC path like...

\\ServerName\ShareName

Then the link works from anywhere on the network.

To do this refresh the links specifying a new location and then navigate to
the back via "Network Neighborhood - Entire Network" rather than going
through a mapped drive letter.
 
RW said:
We have the FE and BE in the same directory on the server.

If the FE is moved to everyone's local PC, how does one insure the links
to
the tables don't get broken?
Click to expand...


Why would they? That information is in the FE and travels with it.

You should use UNC pathnames for the linked table, and then you won't have
to worry about mapped drives being consistent. In the Linked Table Manager,
put a check at the bottom of the dialog, and locate the backend via network
neighborhood.
 
Thanks for the assistance.


Joan Wild said:
Why would they? That information is in the FE and travels with it.

You should use UNC pathnames for the linked table, and then you won't have
to worry about mapped drives being consistent. In the Linked Table Manager,
put a check at the bottom of the dialog, and locate the backend via network
neighborhood.
Click to expand...
 
Back
Top