Locked File Won't Allow Multiple Users

[Guest]

This is a sporadic problem that is becoming very frustrating. We have a
database stored on MS Windows SBS2003 file/AD server. All clients are XP Pro
using Office 2000. When one client opens the DB, sometimes, others cannot
access it. We must close all users out of the program completely and wait
for the .ldb file to disappear. When it disappears, we can then all open
the DB for adding stock. Sometimes, it locks everyone out altogether for 5
or 10 minutes. Then miraculously, it will then open again for everyone with
no changes made to the DB, server or clients. It is a mystery why sometimes
it works, and sometimes it doesn't. If anyone has any suggestions or tips,
I would appreciate them greatly. Thank you in advance.


Also, on a sidenote: Is there a means to password protect only 2 or 3 forms
in a database? I am assuming it would be best to just create a new database
with employee info and store it locally on the boss's pc. If there is a way
to leave our database intact, but require a password to access a select few
forms, this method would be ideal. Again, thanx for any input you may
provide.

 

[Guest]

from Rainbow01 Hong Kong

firstly my English may be not good

from my experience for develop Access application:
-all user action must use forms for user interface, not allow do anything in
tables or query status
-put maindata mdb or mde (only contatin Tables) in Server for backend
-other mdb or mde (contain query, form, report, modules) in each PC for
frontend user interface
then connect to backend mdb or mde through network for multi use
-make Login form by yourself, make 1 table to store user LoginName,
Password, Permission(for Security Level, e.g. some uses only can use some
function, some user can do anything etc....)

P.S. if your situation have many user use at same time, suggest to change
MSSQL server for backend database,
frontend still using Access for user interface

"Brian" 來函：

 

[Guest]

We must close all users out of the program completely and wait

for the .ldb file to disappear ... Sometimes, it locks everyone out
altogether for 5 minutes.

This looks like a network optimisation, but I'm not a network
guru. Normally an LDB file disappears immediately, or after a
few seconds, or 10 - 60 minutes after the user logs out of Windows
and disconnects from the network.

Or sometimes anti-virus/firewall software can do this to you.


The only network problem I'm aware of specifically with SBS is
the "signed packet" problem: this security setting makes files system
databases slow, even when it does not create other problems.

You should turn off packet signing: you may need to change group
policy to do that.

http://www.tangent-systems.com/support/delayedwrite.html

http://groups.google.com.au/group/m...read/thread/7188759b0c85bf5a/8b2530b326ed7070

http://www.smallbizserver.net/SBS20...copytotheSBS2003server/tabid/139/Default.aspx

(david)