Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Multiuser / Networking / March 2004

Tip: Looking for answers? Try searching our database.

Locked Out and Open for Suggestions

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Bernard Johns - 29 Mar 2004 02:51 GMT
I have a mulituser database where up to 10 users may access a .mdb at the same time, but usually on 2-4 are using it at any given time.  The .mdb is split with the forms, queries, reports, etc. on the user's desktop and the back end on a local server running Microsoft Server 2000.  The users all have full permissions to the folder where the back end .mdb is located.  There is no security on the .mdb itself other than Shift-Bypass.   The default open mode is shared.  The default record locking is set to  No Locks.  Open Databases with Record-Level Locking is enabled. The deskstops are running Windows 2000 and are using Office 2000 Professional.  The .mdb was created in Access 2000

I am expereincing a problem  that several times a day, users will become locked out by other users.  The lock out sometimes occur when the user locking the others out opens the .mdb and sometimes after the .mdb is open for a period of time.  One computer does seem to lock out others more often than other computers, but the problem is not limited to that computer exclusively. The problem occurs whether two computers are accessing the .mdb or 10 computers are accessing the .mdb.
Tony Toews - 29 Mar 2004 22:04 GMT
>I am expereincing a problem  that several times a day, users will become locked out by other users.  The lock out sometimes occur when the user locking the others out opens the .mdb and sometimes after the .mdb is open for a period of time.  One computer does seem to lock out others more often than other computers, but the problem is not limited to that computer exclusively. The problem occurs whether two computers are accessing the .mdb or 10 computers are accessing the .mdb.

When you say locked out what's the exact message?   Unknown format?

See if any of the messages at the Corruptions Symptoms pages at my
website match.   http://www.granite.ab.ca/access/corruptmdbs.htm

Tony
--
Tony Toews, Microsoft Access MVP
  Please respond only in the newsgroups so that others can
read the entire thread of messages.
  Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
DIJ - 30 Mar 2004 13:56 GMT
> I have a mulituser database where up to 10 users may access a .mdb at the same time, but usually on 2-4 are using it at any given time.  The .mdb is
split with the forms, queries, reports, etc. on the user's desktop and the
back end on a local server running Microsoft Server 2000.  The users all
have full permissions to the folder where the back end .mdb is located.
There is no security on the .mdb itself other than Shift-Bypass.   The
default open mode is shared.  The default record locking is set to  No
Locks.  Open Databases with Record-Level Locking is enabled. The deskstops
are running Windows 2000 and are using Office 2000 Professional.  The .mdb
was created in Access 2000.

> I am expereincing a problem  that several times a day, users will become locked out by other users.  The lock out sometimes occur when the user
locking the others out opens the .mdb and sometimes after the .mdb is open
for a period of time.  One computer does seem to lock out others more often
than other computers, but the problem is not limited to that computer
exclusively. The problem occurs whether two computers are accessing the .mdb
or 10 computers are accessing the .mdb.

I've been getting that problem as well.
I've found that the back end .mdb has become corrupt and the only way to
repair it to unshare the folder where the back end is and repair.
Then I have to reshare the folder again.
I don't know if this is the same error but any help would be appreciated.

DIJ
www.emu-x.com
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.