Compact not replacing original database

[Paul Hammond]

When I compact and repair my database it goes through the motions, but does
not replace the original database. It creates a new database called db1.mdb
which is the compacted version. I have watched this process many times and
worked up until recently. I am using Office 2003. Could this be a network
security problem. I know how to grab the new database and start using it,
but I thought someone might have a better idea.

Thanks,

Paul

 

[Klatuu]

It most likely is a permissions issue. You have to have delete rights to
the directory where the mdb is.

In fact, if you have a multi user Access application, read, write, create,
and delete permissions are required for the directory where the back end mdb
resides.

 

[Paul Hammond]

Thanks, You seem to be correct. Though I can delete, save, create or do
virtually anything I want on the network, I bump into little security blips
all the time now. I found I can do the complete compact and repair on my C:
drive without any problems.

Paul

 

[ormazd]

I just encountered this situation and thought I'd share the solution we
found. A network user identified this issue while compacting databases in
his networked home directory. We checked his Security settings under
Properties for the folder, and he had Full Control permissions.
We next accessed his folder directly from the server, which provided an
additional tab for 'Sharing.' When we checked Full Control permissions in
Sharing, he was able to perform the compact action properly.