By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,510 Members | 1,441 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,510 IT Pros & Developers. It's quick & easy.

compacting question

P: n/a
I do a routine compact and repair on a back end MS Access 2002 database.
This time I had something peculiar occur. The compact started as normal,
than the following error message popped up (I shortened the path for this
post):

Microsoft Access can't delete G:\......\MW-Estimate_be.mdb after compacting
it. The compacted database has been named G:\......\db1.mdb.

It then goes on to explain that the original database wasn't deleted because
it was read-only. I did check and there was no .ldb file prior to compacting,
which let me to believe no users were accessing the database, and it started
compacting because it displayed the Access progress bar in the lower left of
the screen.

I have since been able to successfully compact it and have confirmed through
the Linked Table Manager that the front end is linked to the proper back end.
Was this just a fluke timing thing where someone may have accessed the
database at the same time I was compacting?

Any thoughts are appreciated!

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200709/1

Sep 17 '07 #1
Share this Question
Share on Google+
1 Reply


P: n/a
On Sep 17, 8:35 am, "Slez via AccessMonster.com" <u23064@uwewrote:
I do a routine compact and repair on a back end MS Access 2002 database.
This time I had something peculiar occur. The compact started as normal,
than the following error message popped up (I shortened the path for this
post):

Microsoft Access can't delete G:\......\MW-Estimate_be.mdb after compacting
it. The compacted database has been named G:\......\db1.mdb.

It then goes on to explain that the original database wasn't deleted because
it was read-only. I did check and there was no .ldb file prior to compacting,
which let me to believe no users were accessing the database, and it started
compacting because it displayed the Access progress bar in the lower left of
the screen.

I have since been able to successfully compact it and have confirmed through
the Linked Table Manager that the front end is linked to the proper back end.
Was this just a fluke timing thing where someone may have accessed the
database at the same time I was compacting?

Any thoughts are appreciated!

--
Message posted via AccessMonster.comhttp://www.accessmonster.com/Uwe/Forums.aspx/databases-ms-access/2007...
My vote is for the fluke timing thing - except without the 2nd user.
Sometimes it is difficult for a program to know how long it will take
the operating system to do different tasks. Think cart before the
horse. If the operating system is still trying to close the database,
when it is instructed to delete the database... well, you can guess
the rest.

Sep 17 '07 #2

This discussion thread is closed

Replies have been disabled for this discussion.