Jim Dettman
jimdettman at earthlink.net
Wed Aug 18 13:27:22 CDT 2004
JB, This needs to be fix. It means that the program is terminating abnormally either from the user, by a problem with the PC or network, or because of a programming problem. What ever the cause, it needs to be investigated. Simply deleting the locks is not really a cure. Sooner or later, your going to end up with a corrupt MDB. It's not a rights issue because even if the LDB file gets left behind (which may cause a performance problem when logging in under certain circumstances), the locks still should be getting cleared. I'd hound the "developer" till s/he does something about it. In the meantime, if this is a NT/W2K/WinXP server, try turning off OPLOCKS (Opportunistic Locking). More info is available in the MSKB on Microsoft's web site. I'd also make sure the MDB/LDB is not being virus scanned. Jim Dettman (315) 699-3443 jimdettman at earthlink.net -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of John Bartow Sent: Wednesday, August 18, 2004 1:14 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Clear Locks Via OS (was: A table that can't beduplicated) This is what I am trying to do from the workstation. (I recently asked about this on DBA-Tech). I have a customer site where their 3rd party app is constantly leaving an mdb & ldb file open on the server every time they use the apps. (I can't touch the apps - VB using A97 mdb BE). I am looking for a way to do this from the workstation because as simple as it sounds, the client is afraid of logging onto the server to do this and the developer is non-responsive to the problem. (Your message below is what I have them doing now plus closing the hung mdb & ldb files for the user that is no longer using the app.) Any idea of whether I can do this from the workstation? Maybe wrap the apps startup in a batch file that calls the app and when done calls a script to clean it up? JB -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of DWUTKA at marlow.com Sent: Wednesday, August 18, 2004 11:07 AM To: accessd at databaseadvisors.com Subject: RE: [AccessD] Clear Locks Via OS (was: A table that can't be duplicated) Depends on the OS. You can't in Windows 9x machines, but in NT based machines, it's a matter of finding the files in use. For Windows 2000, one way to get there, is to right click on my computer, and select 'Manage'. This brings up the Computer Management screen. Expand the 'System Tools' node, then the 'Shared Folders' node, then open the 'Open Files' node. That will display all of the 'file locks' coming in from other machines. Well, sort of. It's displaying files in use, you're not going to see the individual locks that one particular user has in place. Drew -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Dan Waters Sent: Tuesday, August 17, 2004 6:32 PM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Clear Locks Via OS (was: A table that can't be duplicated) Jim, How do you, ". . . clear the locks being held on the database file via the OS." ??? Thanks, Dan -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman Sent: Tuesday, August 17, 2004 11:20 AM To: Access Developers discussion and problem solving Subject: RE: [AccessD] A table that can't be duplicated Paul, Delete the .LDB file if it exists, then try again. If still the same problem reboot the machine where the database resides or clear the locks being held on the database file via the OS. Jim (315) 699-3443 jimdettman at earthlink.net -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Paul Rodgers Sent: Tuesday, August 17, 2004 11:47 AM To: 'Access Developers discussion and problem solving' Subject: [AccessD] A table that can't be duplicated The main table in a database won't be copied. Access says another user is busy with the table. But this is not so. I can't copy the table and rename the table, I can't import it into another database, I can't use a MakeTable query to do it that way. I can copy the whole database, but that same table in the copied database refuses to be copied - or to be renamed. I can steal it with Excel - but then I lose all the lookups and the like. Anyone had this problem before please, anyone found an answer, please? Cheers paul -- _______________________________________________ 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