[AccessD] Laccdb - Lock File Issues - Problem Solved

Brad Marks BradM at blackforestltd.com
Thu Aug 5 09:56:06 CDT 2010


We are fairly locked into using Linked Tables (no pun intended).

It sounds like if we stay with Linked Tables, Access will always use a Lock file, even though we never update any of the Linked Tables.  Is this correct?


-----Original Message-----
From: accessd-bounces at databaseadvisors.com on behalf of Charlotte Foust
Sent: Thu 8/5/2010 9:50 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Laccdb - Lock File Issues - Problem Solved
I assume you're using linked tables.  If you want to avoid the lock
file, you'd need to do it differently.  You could use ADO to read data
from the SQL Server table without a link or used a stored procedure to
return the data.


On Thu, Aug 5, 2010 at 7:34 AM, Brad Marks <BradM at blackforestltd.com> wrote:
> 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

AccessD mailing list
AccessD at databaseadvisors.com
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