[AccessD] A2K - Locking Problem

Robin robin at musicalmemories.co.uk
Fri Sep 28 09:12:17 CDT 2007


Hi Reuben,
I've had this caused by a corrupt record - especially when I used to use
memofields.
Check the underlying table to see if there are any field containing
#error
Rgds
Robin Lawrence


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Reuben
Cummings
Sent: 28 September 2007 15:21
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] A2K - Locking Problem


The IT department refuses to reboot the server the mdb resides on.  They
want to complain about a problem, but won't do one thing I've asked them
to do.

Reuben Cummings
GFC, LLC
812.523.1017


> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of 
> max.wanadoo at gmail.com
> Sent: Friday, September 28, 2007 10:02 AM
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] A2K - Locking Problem
>
>
> Hi Reuben,
> When I get this, it is because my system thinks (or actually has) two 
> versions of the same mdb open running simultaneously, matching each of

> my keystrokes. It might be a memory leak or similar.  If I reboot the 
> PC the problem disappears.  Sometimes looking at the Task Manager give

> a clue.
>
> Max
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Reuben 
> Cummings
> Sent: Friday, September 28, 2007 2:54 PM
> To: AccessD
> Subject: [AccessD] A2K - Locking Problem
>
> I have a client that is receiving messages stating "The Microsoft Jet 
> Database engine stopped the process because you..."  Basically trying 
> to say that the record has been edited by someone else.
>
> This has happened several times lately.  There is always a .ldb hangin

> around after closing the app (by all users - there are 4 users).  This

> is occurring even if only one person is using the app.  And even then 
> the ldb is still not deleted.
>
> Any ideas?
>
> Reuben Cummings
> GFC, LLC
> 812.523.1017
>
>
>
> --
> 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