O
Ogg
After doing a /COMPACT (via batch file), I was unable to access the .mdb
share. I received an error something like "the file is locked or is set to
exclusive access by another user". Locally, the compacted frontend and
backend worked fine. We've never had this problem when we did the "Compact
and Repair" from within Access. But, this is the first time I was looking
to do compacting via a batch file to automate the process. I am wondering
what I might be missing when I launch the compact via the /COMPACT switch
that seems to block access once the compact has completed.
Eventually, we solved the problem by simply copying the "locked" file to
another location, and copying it back to the work directory. Then access
was back to normal! For example, tblMAIN.mdb was locked or inaccessible.
We copied it to another location. Then we renamed the bad one to
xxx-tblMAIN. Then we copied the "copy" back to the working directory. THEN
tblMAN.mdb was accessible just fine.
Is this a known issue when doing a /COMPACT via command-line mode?
share. I received an error something like "the file is locked or is set to
exclusive access by another user". Locally, the compacted frontend and
backend worked fine. We've never had this problem when we did the "Compact
and Repair" from within Access. But, this is the first time I was looking
to do compacting via a batch file to automate the process. I am wondering
what I might be missing when I launch the compact via the /COMPACT switch
that seems to block access once the compact has completed.
Eventually, we solved the problem by simply copying the "locked" file to
another location, and copying it back to the work directory. Then access
was back to normal! For example, tblMAIN.mdb was locked or inaccessible.
We copied it to another location. Then we renamed the bad one to
xxx-tblMAIN. Then we copied the "copy" back to the working directory. THEN
tblMAN.mdb was accessible just fine.
Is this a known issue when doing a /COMPACT via command-line mode?