[AccessD] A2K - Locking Problem

Hi Robert and Reuben

But wasn't that patch (from April, 2005) included in Win2003 SP2?

<quote>
Service pack information
To resolve this problem, obtain the latest service pack for Windows Server 2003. ..
</quote>

If so, Reuben, this means that the notwork guys didn't update the server. And if so, what do they think SPs are for?

/gustav

>>> robert at servicexp.com 28-09-2007 23:55 >>>
Reuben,
 I struggled for a looooooong time with what sounds like the same error. I
just happened across a MS KB about the problem. Had my users install the
patches and problem solved. 


http://support.microsoft.com/kb/895751 


If you need the patch's (Win 2003 & XP) I believe I still have them..



WBR
Robert

 
-----Original Message-----
From: accessd-bounces at databaseadvisors.com 
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Reuben Cummings
Sent: Friday, September 28, 2007 9:54 AM
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