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 / June 2006

Tip: Looking for answers? Try searching our database.

Table locked

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Leoleu - 27 Mar 2006 12:48 GMT
Coul i determine which user or computer locked a table?

L.
Tony Toews - 30 Mar 2006 03:56 GMT
>Coul i determine which user or computer locked a table?

No.   You can determine which users have an MDB locked though.

Tony
Signature

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

Leoleu - 10 Apr 2006 12:54 GMT
Hmm, I have this situation: around 10 users use the same table, I use
record-level locking.
But sometimes happen, that the table is lock (all records). Do you have any
idea,
what is cause of this?

Sorry if my english is understable :-)

Thank You

 L.

>>Coul i determine which user or computer locked a table?
>
> No.   You can determine which users have an MDB locked though.
>
> Tony
david epsom dot com dot au - 11 Apr 2006 05:46 GMT
What message do you get when the table is locked?

(david)

> Hmm, I have this situation: around 10 users use the same table, I use
> record-level locking.
[quoted text clipped - 13 lines]
>>
>> Tony
Leoleu - 18 Apr 2006 10:36 GMT
Error 3218, "Nelze aktualizovat. Je aktualne uzamceno" (Can't update.
Currently locked)

> What message do you get when the table is locked?
>
[quoted text clipped - 17 lines]
>>>
>>> Tony
david@epsomdotcomdotau - 19 Apr 2006 00:34 GMT
This is a Windows locking error, not a database locking error.

The database can't lock because Windows can't lock.

You can get this error even when there is only one user, doing
one thing, because it is not a lock on a record or table, it is just
Windows not locking.

You need to check file permissions on the database file and on
the folder where the database is.

If it is a split database, you need to check in both places.

Sometimes database corruption or bad ldb files can cause the
same problem, but you need to check permissions first.

Sometimes Novel Networks caused this problem because they
ran out of locks, but you need to check permission's first.

(david)

> Error 3218, "Nelze aktualizovat. Je aktualne uzamceno" (Can't update.
> Currently locked)
[quoted text clipped - 20 lines]
> >>>
> >>> Tony
Leoleu - 20 Apr 2006 06:29 GMT
Hmm, I look, that the permissions for the database (and directory) are
R/W/E.
All users can change all data in all tables. But sometimes the one table is
locked.
I can change data in other tables in the same database in this time.
When all users close the client part of application, the table is unlocked.
I don't know, what is cause of locking the table.

L.

> This is a Windows locking error, not a database locking error.
>
[quoted text clipped - 42 lines]
>> >>>
>> >>> Tony
david epsom dot com dot au - 20 Apr 2006 07:14 GMT
The error message indicates that Windows won't
let Access set locks. What kind of Network do
you have?

(david)

> Hmm, I look, that the permissions for the database (and directory) are
> R/W/E.
[quoted text clipped - 53 lines]
>>> >>>
>>> >>> Tony
Leoleu - 26 Apr 2006 14:56 GMT
We have Microsoft Network with Windows 2003 server as primary domain
controller
and Microsoft ISA 2000 server as firewall.
I am on 100Mb LAN but 90% users is on 10Mb.

> The error message indicates that Windows won't
> let Access set locks. What kind of Network do
[quoted text clipped - 60 lines]
>>>> >>>
>>>> >>> Tony
david epsom dot com dot au - 27 Apr 2006 06:29 GMT
Next I suggest turning OFF record level locking at all clients.

Hopefully, fewer locks, so Windows can manage the locks better.

(david)

> We have Microsoft Network with Windows 2003 server as primary domain
> controller
[quoted text clipped - 65 lines]
>>>>> >>>
>>>>> >>> Tony
Leoleu - 02 May 2006 11:03 GMT
I tested it, but the problem still remains.

> Next I suggest turning OFF record level locking at all clients.
>
[quoted text clipped - 71 lines]
>>>>>> >>>
>>>>>> >>> Tony
david epsom dot com dot au - 03 May 2006 03:28 GMT
If you get a simple table lock conflict, you get a message

Table <name> is exclusively locked by user <name> on machine <name>. (Error
3189)

If the problem was just that the table was locked by another user, that is
the message you would get.

Because you did not get that message, it means there is not a person who
just has the table locked.

Sometimes another user has locked something else in the same area, but if
that was true, the locks would go away when that person finished.

You say that only one table is locked, that the locks stay until everyone
leaves, that the file is on a Windows Server. This is unusual. Perhaps
Windows in not unlocking correctly?

I suggest that you check again all patches on Windows workstations, and
Office, and Windows Server.

Search to see if you can find some part of your application which causes
this problem.

Turn off file caching on the server, and network caching, and optimistic
locking.

I am sorry that none of the questions I have asked have helped me find the
problem with your system. I don't know any more questions to ask.

(david)

>I tested it, but the problem still remains.
>
[quoted text clipped - 74 lines]
>>>>>>> >>>
>>>>>>> >>> Tony
david epsom dot com dot au - 04 May 2006 06:55 GMT
When you tested without record level locking, you still got the
same error MESSAGE, not a better message?  Sometimes when you
have record level locking turned off, you get a better error
message, with more information.

A database is either in the record level locking mode or not,
depending on who was first to open it. To turn off record level
locking, you have to disconnect everyone from the database,
and make sure that when you connect everyone connects with
page locking.

Also, check the value in the registry of
HKLM\SOFTWARE\MICROSOFT\JET\4.0\ENGINES\JET 4.0\pageslockedtotablelocked

The value should be zero.

(david)

>I tested it, but the problem still remains.
>
[quoted text clipped - 74 lines]
>>>>>>> >>>
>>>>>>> >>> Tony
Leoleu - 05 May 2006 14:23 GMT
Yes, the message is the same. I will try copy the data to another server
(newer and better)
and I will test it. I forgot inform you, that the data is on server with
Windows NT4.0 SP6.
I will move the data on server with Windows2003 for test.
Thank you for your advices.

> When you tested without record level locking, you still got the
> same error MESSAGE, not a better message?  Sometimes when you
[quoted text clipped - 92 lines]
>>>>>>>> >>>
>>>>>>>> >>> Tony
leoleu - 09 Jun 2006 12:52 GMT
After data move on server Win2003 the problem still remains.
I check registry on all worskations for pageslockedtotablelocked
and all values are zero. I forgot inform you, that
few worskations have installed MS Access 2000
and other worskations have only runtime. I will check
for all update and test it.

> When you tested without record level locking, you still got the
> same error MESSAGE, not a better message?  Sometimes when you
[quoted text clipped - 92 lines]
>>>>>>>> >>>
>>>>>>>> >>> Tony
 
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.