J
J
I'm using Task Scheduler to run a number of compacting tasks on MS
Access databases:
Here's an example command line:
"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE"
"\\ATGSVR3\Corp\Inventory.mdb" /compact
I do this for 6 databases and 4 are compacting w/o issues while 2 error
out with the following error:
===================
Microsoft Office Access can't delete \\ATGSVR3\Corp\Inventory.mdb after
compacting it. The compacted database has been named
\\ATGSVR3\Corp\db1.mdb
If you compact a database using the same name, Microsoft Office Access
creates a new compacted database and deletes the original. In this
case, however, the original database wasn't deleted because it is
read-only.
If you can, remove the read-only status, delete the original database
and then rename the new database using the original name. If you can't
remove the read-only status, inform your workgroup administrator.
====================
Even for the 2 databases that error out, they error out sproadically
(although it is more common for the command to error out rather than
complete successfully.
Any thoughts? I have checked for read-only status and all files are
read/write.
Access databases:
Here's an example command line:
"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE"
"\\ATGSVR3\Corp\Inventory.mdb" /compact
I do this for 6 databases and 4 are compacting w/o issues while 2 error
out with the following error:
===================
Microsoft Office Access can't delete \\ATGSVR3\Corp\Inventory.mdb after
compacting it. The compacted database has been named
\\ATGSVR3\Corp\db1.mdb
If you compact a database using the same name, Microsoft Office Access
creates a new compacted database and deletes the original. In this
case, however, the original database wasn't deleted because it is
read-only.
If you can, remove the read-only status, delete the original database
and then rename the new database using the original name. If you can't
remove the read-only status, inform your workgroup administrator.
====================
Even for the 2 databases that error out, they error out sproadically
(although it is more common for the command to error out rather than
complete successfully.
Any thoughts? I have checked for read-only status and all files are
read/write.