Drew Wutka
DWUTKA at Marlow.com
Tue May 20 17:44:12 CDT 2008
To find out who is locking a record is pretty tricky. Basically, you need to find out where in the 'virtual' .ldb space the table records are located. Then to test if they are locked, you have to try to lock those bits/bytes yourself, if they are locked, you can determine who is locking them by another set of bits....pretty complex, and I don't think the white papers give exact details on how to do it. To throw in a slight tangent to this, you may want to look into why a record is being locked. I'd say that in 99% of the systems that I have built, the end users are never able to lock a record more then the split second that it is required to add a record, or change a record. Of course, this leads into the bound/unbound debate.... Drew -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jennifer Gross Sent: Tuesday, May 20, 2008 6:07 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Who is locking the record? Hi Steven, LDBView and UserRoster give me who is logged in, but not who is locking a particular record. So far, parsing the error description for 3260 seems to be the only viable option. This error does not seem to be raised with two sessions on the same machine or on a Windows peer to peer network. With Windows Server record locking is raising error 3260, as long as the record is not locked by the same session. At least with my basic testing it seems that is what is going on. Jennifer -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Steve Erbach Sent: Tuesday, May 20, 2008 1:44 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Who is locking the record? John, Could LDBView or UserRoster be of use at all? http://www.mvps.org/access/modules/mdl0055.htm http://support.microsoft.com/kb/285822#1 http://www.granite.ab.ca/access/corruption/workstation.htm Steve Erbach Neenah, WI http://www.TheTownCrank.com On Tue, May 20, 2008 at 1:41 PM, jwcolby <jwcolby at colbyconsulting.com> wrote: > To my knowledge it is not possible. > > John W. Colby > www.ColbyConsulting.com > > > Jennifer Gross wrote: >> No takers on this? Sometimes the Access message is generic and just >> lets you know the record is locked. Other times when a record is >> locked Access will display their own message letting the user know >> who is locking the record. So it seems that information is >> available, must be in the LDB file >> - does anyone know how to get at it? >> >> 3218 is a record locking error, perhaps 3188 as well. I can trap the >> error, but I don't know how to identify who is locking the record. >> >> Jennifer -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com The information contained in this transmission is intended only for the person or entity to which it is addressed and may contain II-VI Proprietary and/or II-VI Business Sensitive material. If you are not the intended recipient, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. You are notified that any review, retransmission, copying, disclosure, dissemination, or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited.