Compact and Repair

[Guest]

Is the copy that the utility makes only for its compacting purpose and then
is deleted after the utility is completed? Or, does one have to physically
delete the old larger copy?

 

['69 Camaro]

Hi.

Is the copy that the utility makes only for its compacting purpose and
then
is deleted after the utility is completed?

Not quite. It creates a db1.mdb file to place copies of the tables and
objects into while it gathers the records from the original file. Once it's
finished, the original file is automatically deleted, and the db1.mdb file
is renamed with the original file name. However, if db1.mdb already exists
in that directory, the compacted file will first be named db2.mdb, unless
that name already exists, in which case Jet will find the next highest
sequential number that doesn't already exist in that directory and use that
in naming the new file. The file after the compaction isn't the same file
as the original and may even have different Windows security permissions
from the original.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blog: http://DataDevilDog.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

 

[Cgman]

Is this normal that Access does not delete the old file and rename the new
one correctly?

If any other person is signed into the PC and performs a compact/repair,
Access works properly. When our database person is signed in it fails to
delete the old file and rename the new file. This occurs over the network and
he has to copy everything locally to have access work as it should.

Any ideas why this would only fail with one person? We deleted his local
profile, and its only when he is logged into the PC when this happens.

Thank You!

 

[Tony Toews [MVP]]

Is this normal that Access does not delete the old file and rename the new
one correctly?

If any other person is signed into the PC and performs a compact/repair,
Access works properly. When our database person is signed in it fails to
delete the old file and rename the new file. This occurs over the network and
he has to copy everything locally to have access work as it should.

Any ideas why this would only fail with one person? We deleted his local
profile, and its only when he is logged into the PC when this happens.

That person likely doesn't have delete permission in that folder. Or
something similarly wield.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Cgman]

Thank you very much for your help, Tony.

We were able to find our resolution in the knowledge base hidden under a rock.
Knowledge base # 945674 fixed our problem without a hitch.

Thanks again.