runtime version locking problem

[Miranda Lynn]

I created a database for our office which is kept on a server for multiple
people to access. The database is split to protect the tables. All the
locking is set to record-level and the database is shared to allow for the
multiple users. The problem is that we have a combination of full versions
of Access and runtime versions that use the database. Multiple people can
get in it some of the time (from what I can tell this is when a full version
opens it first), and the rest of the time it totally locks when one person is
in it (I think this happens when a RT version gets into it first). What I
would like to know is if there's something about the RT version that might
lock down the database that I haven't been able to find or how I can make it
quit doing this because it makes getting things done difficult when there's
so much waiting? Thanks

 

['69 Camaro]

Hi, Miranda.

Multiple people can
get in it some of the time (from what I can tell this is when a full version
opens it first), and the rest of the time it totally locks when one person is
in it (I think this happens when a RT version gets into it first).

When the subsequent user attempts to open the database file, is the error
message either "Could not lock file" or "Could not use <Full
path\DBName.mdb>; File already in use"? If so, then some of the users don't
have "Full Control" Windows security permissions on the directory where the
database file is located. For more information on methods to avoid this
problem, please see the following Web page for a link to the article,
"Multiuser Databases":

http://www.Access.QBuilt.com/html/articles.html

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.)