BradM at blackforestltd.com
Thu Aug 5 09:34:27 CDT 2010
Charlotte, Thanks for the help. As it turns out, we had a "hung" Access task. We used the Windows Task Manager to nuke it. This did not delete the Laccdb file, but the next time we initiated the Access application and then got out of it the Laccdb file went away. I still would like to know if there is a way to avoid the Laccdb file completely. The application in question is only reading data from SQL-Server. It is deployed as an accdr file. It seems like there is no need for any type of locking. Thanks again, Brad -----Original Message----- From: accessd-bounces at databaseadvisors.com on behalf of Charlotte Foust Sent: Wed 8/4/2010 10:24 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Laccdb - Lock File Issues Lock files are associated with mdb and accdb file formats. If you have one that doesn't get deleted when the connection or database is closed, it usually means that the last person out of the database did not have delete permissions on the folder where the lock file lives. Charlotte Foust On Wed, Aug 4, 2010 at 12:56 PM, Brad Marks <brad.marks1 at gmail.com> wrote: > All, > > We have never paid a lot of attention to the Access 2007 Laccdb lock file in > the past. > > Recently we have run into some issues and I am trying to get up to speed > with this file and how it works. > > We are using a Windows Terminal Services environment. We have a small > number of scheduled jobs that automatically run Access Reports and then > Email them at night. No user is logged on when this happens. > > At appears that one of our scheduled jobs did not run properly and now we > have an Laccdb file that we cannot delete. > > If we open with Laccdb file work notepad, we see this info > > > TS Admin TS Admin > > > > How can we delete this file? > > It appears that our automated jobs will still run, even with this lock file. > > We have done some experimenting and we can see how the lock file prevents us > from making any changes to a form or report. It appears that such things as > Append Queries will still run, however. Is this true? > > Is there a way to force Access to not write a lock file. The end-users are > all using an accdR version of the system. They are therefore not able to > make any changes to the application, they can only use the application. It > seems like we really don't need any lock protection for this application. > Is there a way to turn it off so that we don't have to deal with this > problem in the future. > > Thanks in advance for your help. > > Brad > -- > 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 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
More information about the AccessD mailing list