compact on close makes new db

[Richard Choate]

When I use the "compact on close" setting with AccessXP on my PC, all works
fine. When my client uses that setting on his PC with AccessXP, it
automatically creates a new copy of the database with names like db1.mdb,
db2.mdb, etc. Why the hell is it doing this? His PC is very similar to mine
and his software is essentially identical.
Richard Choate

 

[John Vinson]

When I use the "compact on close" setting with AccessXP on my PC, all works
fine. When my client uses that setting on his PC with AccessXP, it
automatically creates a new copy of the database with names like db1.mdb,
db2.mdb, etc. Why the hell is it doing this? His PC is very similar to mine
and his software is essentially identical.
Richard Choate

Check the users' Windows security permissions on the folder in which
the database resides. They must have *full* read, write, create,
rename and delete permission on the folder - and it would appear that
either they don't. The way Compaction works is that Access creates a
new database named dbX.mdb (starting with db1.mdb), copies the current
database objects into it, and then deletes the old database and
renames db1.mdb to the current database name. One of these latter two
steps isn't being permitted.

 

[jfp]

John --
re this, i remember several months ago reading a posting that explained
that when Access makes a new database, it loads default values for
certain settings / options. Apparently, the compact operation does NOT
overwrite some of these with those from the database being compacted.
Thus, after compaction, certain settings have quietly been set back to
the default values. I think this affected some stuff in security. Does
this sound correct? If so, please elucidate. Thanks !