max.wanadoo at gmail.com
max.wanadoo at gmail.com
Fri Sep 28 14:29:54 CDT 2007
Clicked directly, but hey! Just tried again and now it works! (are you sure you didn't give MS a quick csll and tell them to put it up there again!) Thanks Jim Max -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman Sent: Friday, September 28, 2007 8:09 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] A2K - Locking Problem Works here. Did you cut & paste or click on it directly? Jim. -----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 11:33 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] A2K - Locking Problem Jim, The link doesn't seem to work. Max -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman Sent: Friday, September 28, 2007 3:54 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] A2K - Locking Problem Reuben, That can be caused by a few things, but the first thing is to check and make sure that there are no open locks and kill them if there are. This can be done by rebooting the server or: 1. Get all the users out. 2. On the server, right click on My Computer, select manage. Go to Shared Folders, then open files. See if any references exist to the MDB file. If so right click on the correct file and then select close. Now see if you can delete the .LDB file. 3. If nothing shows, then the network session that had the lock may already be closed, but the lock may still be there. Use the utility here: http://www.microsoft.com/technet/sysinternals/utilities/handle.mspx to check for open handles against the MDB and close them if they exist. You now can delete the .LDB file. Jim. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Reuben Cummings Sent: Friday, September 28, 2007 10:21 AM 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 -- 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