[AccessD] Who is locking the record?

Jennifer Gross jengross at gte.net
Wed May 21 12:54:15 CDT 2008


I don't think it is an older version of Jet.  They have MDAC 2.8 installed,
running Jet 4.0.  From Drew's explanation it seems to be related to the OS
and it's file locking????

Jennifer 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Wednesday, May 21, 2008 8:20 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Who is locking the record?

If I had to guess I would say that on your client's system they are running
an older version of Access / Jet which raises the original error, and that
the later versions of Jet do not raise that error any more?
John W. Colby
www.ColbyConsulting.com


Jennifer Gross wrote:
> I don't know why, but on my client's Windows Server 2000 system it 
> raises error 3260, but everywhere else I am testing it raising 3218, 
> which does not show the user or machine.
> 
> You are right, when error 3260 is raised I can just display the error 
> description since it gives me the user.  No need to parse it, since it 
> is giving me what I need.  Where my original request stems from is 
> that the error I raise in testing on my system is 3218, which doesn't 
> give the user - so I wanted to know how to get at the user.  I test 
> the same code on my client's system and it raises 3260.  Strange days
indeed . . .
> 
> Jennifer
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: Wednesday, May 21, 2008 5:13 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Who is locking the record?
> 
> I just tested again and I am not getting your results.
> 
> 1) I logged in to my client's system.
> 2) I opened an application with the saved code under discussion.
> 3) I vnc'd to another machine, opened the table under test and started 
> an edit
> 4) I ran the code.
> 
> I received an error 3218, not error 3260.  3218 does not return the 
> user name / machine.
> 
> so at this point I am completely unable to get an error 3260 at all in 
> any method I have used for testing.  the client is not using 
> workgroups so that isn't the issue.
> 
> I don't know what is up but it isn't working for me at all.
> 
> John W. Colby
> www.ColbyConsulting.com
> 
> 
> Jennifer Gross wrote:
>> 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
> 
> 
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com





More information about the AccessD mailing list