Re: Queries & table locking

Dale,

Thanks for the reply. Have you found that option 3 has consistently worked,
or is it still hit & miss, just a little less so? We're not using workgroup
security, as users do not use the database; it simply serves as a source for
populating combo boxes in another app.

Thanks,

Tony


"Dale Fye" <dale.fye@xxxxxxxxxx> wrote in message
news:eZePWdp5JHA.4936@xxxxxxxxxxxxxxxxxxxxxxx
Generally, when I have received a similar error, there is no one else in
the database.

As I recall, unless you are running with workgroup security, Access always
interprets the current user as admin.

I generally go with Option #3.

HTH
Dale

"Tony" <|toxendine@xxxxxxxxxxxxxx|> wrote in message
news:uDZUOkh5JHA.6136@xxxxxxxxxxxxxxxxxxxxxxx
Hi all,

I've got a database that, via a script called by a Windows scheduled
task, gets data from a Progress database on a nightly basis. In a
nutshell, the script opens the database, runs queries to repopulate
tables, then cleans up & closes. The process usually runs without any
problems. However, from time to time running one of the queries
generates an error:

// Could not lock 'tblName'; currently in use by 'admin' on machine
'machineName'

When this happens, a lock file is left behind and I have to reboot the
machine to recover. The query is a make-table query, so it's deleting
the table then recreating it. At this point, I can't put my finger on
why the table shows that it's in use. The query usually takes ~ 10
minutes to run and returns ~ 200,000 records from the source database.
So, I have a few questions:

1) Is there any way to get more information as to the table being in use,
such as the time admin accesses the table or the process (backup or
anything else) running as admin that is accessing the table?

2) Check to see if admin is accessing the table before running the query
and forcing admin to let go of it?

3) If instead of running a make-table query, I ran delete * from
tableName then an append query, would I avoid needing to lock the table?

I'm using Access 2003 running on a Windows Server 2003 machine.

TIA





.

Relevant Pages

  • Re: Queries & table locking
    ... so they don't bloat the main application or database ... always interprets the current user as admin. ... a lock file is left behind and I have to reboot the ... The query is a make-table query, ...
    (microsoft.public.access.queries)
  • Re: Queries & table locking
    ... so they don't bloat the main application or database file. ... always interprets the current user as admin. ... a lock file is left behind and I have to reboot the ... The query is a make-table query, ...
    (microsoft.public.access.queries)
  • Sync Select Records From Table
    ... I have a fairly large access database that I need to sync with Pocket ... use criteria in a make-table query, only those records that meet the ... Click the Query menu -> Click the Make-Table Query command. ...
    (microsoft.public.pocketpc.developer)
  • Re: Sync Select Records From Table
    ... > I have a fairly large access database that I need to sync with Pocket ... use criteria in a make-table query, only those records that meet the ... Click the Query menu -> Click the Make-Table Query command. ...
    (microsoft.public.pocketpc.activesync)
  • Queries & table locking
    ... I've got a database that, via a script called by a Windows scheduled task, ... The query is a make-table query, ... such as the time admin accesses the table or the process (backup or anything ...
    (microsoft.public.access.queries)