Odd Compact Behavior

[JohnC]

For years, I have been able to have an Access .mdb file open, and be able to
run the Compact/Repair routine. This would compact the file I had open at
the time.

For some reason, now Access (2003) is not compacting the current open
database but it is making a new database with the db#.mdb naming scheme. It
is an exact copy of my database in a compacted state. Nothing is done to
the one I have open. I am doing this on a shared LAN file. Never had this
problem before.

Ideas? I'm sure it is something simple.

John

 

[Rick Brandt]

For years, I have been able to have an Access .mdb file open, and be
able to run the Compact/Repair routine. This would compact the file
I had open at the time.

For some reason, now Access (2003) is not compacting the current open
database but it is making a new database with the db#.mdb naming
scheme. It is an exact copy of my database in a compacted state. Nothing is
done to the one I have open. I am doing this on a shared
LAN file. Never had this problem before.

Ideas? I'm sure it is something simple.

John

Do you have delete permissions to the share? The compact process makes a new
file, deletes your original, and then renames the new file. Without delete
perms you get stuck after step 1.

 

[Bob Quintal]

Do you have delete permissions to the share? The compact process
makes a new file, deletes your original, and then renames the new
file. Without delete perms you get stuck after step 1.

I noticed the same problem, for the first time yesterday, on a local
drive. I suspect it's another "feature" of Office Service Pack 3.

 

[JohnC]

Yes, I have delete permissions to the share. I am able to delete files in
the shared folder.
John

 

[Guest]

I noticed the same problem, for the first time yesterday, on a local
drive. I suspect it's another "feature" of Office Service Pack 3.

I have noticed the exact same thing and it seems as though it started
happening in the last month or so...