John Colby
jwcolby at ColbyConsulting.com
Fri Oct 14 12:44:38 CDT 2005
If no one else is in, and there is no LDB file, if the Administrator logs in, is an LDB created? If so, then the Administrator user IS opening a link to the data container somehow. Jet doesn't know anything about anything. Jet is asked to open connections to data and does so. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jennifer Gross Sent: Friday, October 14, 2005 1:21 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Terminal Server - mdb locked by Administrator Thanks for this John. The weird thing about it is that the Administrator has no open connection to the data file whatsoever. There is nothing that he is running that is connecting to the data file at all. I don't know which user created the .ldb and seems to have left it an orphan, but I can't delete it until the Administrator is logged off. Strange. Jennifer -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Colby Sent: Friday, October 14, 2005 9:48 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Terminal Server - mdb locked by Administrator In that case, the act of logging in to Terminal server is causing him to "open" the database. The LDB file is created whenever any user in any way "opens" the database that the LDB file is for. The LDB file appearing and disappearing when the Administrator logs in / out of terminal server means that JET thinks the user is "opening" the database. "Opening" the database does NOT necessarily mean opening the container itself. It can also be an active connection (ADO or DAO) to a table in the database. If you have asked JET for permission to load / alter DATA in a container, Jet creates the LDB. When the last user closes their ACTIVE connection to the BE, the LDB goes away (theoretically). Thus a FE can be open have tables linked to the BE but there may not be an LDB because they haven't actually opened a form, query or report (or a recordset in code). As soon as you do any of those things, THEN Jet creates the LDB file. Thus the Administrator may have a VB6 application (for example) that runs when he logs in to terminal server. That VB6 application opens some recordset and the LDB file gets created. Something like that. YOU cannot delete the LDB as long as ANY user has a LIVE link to the container. The only time you CAN delete an LDB file is when Jet fails to delete it (which does happen) but there is really no live link to the data container and Jet knows this. At that point the LDB is just an "orphaned" file and can be deleted. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jennifer Gross Sent: Friday, October 14, 2005 12:29 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Terminal Server - mdb locked by Administrator Hi Jim, I have delete permissions to the folder and I am not able to delete the .ldb file. When I check the LDB Viewer it tells me Administrator is logged into the data file. As soon as the Administrator logs out of Terminal Server, the .ldb file is deleted - even though Administrator was not logged in to any Access databases. I will ask the admin guy to make sure I have full delete permissions to that folder. Thanks, Jennifer -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence Sent: Thursday, October 13, 2005 10:38 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Terminal Server - mdb locked by Administrator Hi Jennifer: It is the old problem with permissions to the .ldb file. Every user must have full rights to the directory where the .ldb file is stored or problems happen. I would attempt to delete the ldb file before running anything. If you can not then you will have to get a person in the admin group to delete the file. HTH Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jennifer Gross Sent: Thursday, October 13, 2005 8:37 PM To: AccessD List Subject: [AccessD] Terminal Server - mdb locked by Administrator Hi All, I have an A2K FE/BE on Terminal Server. Every so often I want to go in and compact the BE. Consistently when the Administrator is logged on to Terminal Server but NOT running ANY Access applications Dev Ashish's LDB Viewer shows that the BE is locked by Administrator and I cannot get exclusive use of the BE to compact. Does anyone know what is going on here. TIA, 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 -- 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