I should have been more explicit. The first thing I checked (before I
initially posted) was the permissions - the folder has full access
(R/W)
permissions when the compacting starts.
When the compacting starts
- The original DB is in its own folder (nothing else in folder)
- The folder is marked R/W
When the compacting ends, I have the following:
- Database1.accdb
- original db
I am able to compact in-place with no problems. I am able to copy files
into
the folder and remove them with no problems.
A few observations
1) MS/Access does not issue any messages during or after the compact
2) It would have been nice if the manual compact operation generated a
brief summary of its actions and any issues encountered. At least so I
can
tell that it worked.
3) Windows Explorer does not show any Read-Only permissions on the
folder -
either before or after the manual compaction.
4) Anomaly: I have an explorer-like tool (Power Desk 7) which shows a
bit
more information about folders. It shows that before the compact
operation
the folder is R/W (absence of RO flag). But *after* the compacting, it
shows
the Read-Only checkbox of the folder's attributes as being partially
filled-in. I'm not sure what to make of it. Usually, a partially filled
checkbox means that only some of the selected items to which the
checkbox
applies have the attribute. But in this case it doesn't make sense I'm
selecting a single item (the folder). The folder is not being used by
any
other process. I created it just for this test of the compacting
process.
Weird.
-Regards
David
:
Perhaps you don't have the correct permissions on the folder where the
accdb
file exists.
Compacting creates a new file (Database1.accdb, Database2.accdb,
etc.).
Once
the compact is complete, Access deletes the existing file and renames
the
new one.
Check to ensure that you have Delete permission on the folder.
--
Doug Steele, Microsoft Access MVP
(no private e-mails, please)
I am experiencing the same issue. It creates Database1.accdb and
leaves
the
original alone.
[I'm running Win/XP with the latest updates. I am the admin for the
system]
I even tried compacting Database1 which was a clean copy of the
original
db.
It creates Database2 and leaves Database1 alone.
My DB is very simple - 3 tables with no relationships among them.
Two
of
the
tables are empty, the third just has a bit of data.
-David
Running Access 2007.
:
On Thu, 27 Sep 2007 11:16:02 -0700, Connie
<
[email protected]>
wrote:
When we use the compact and repair function in Access 2007, on a
database
created in Access 2000, it creates a new database file named
Database.
Subsequent compactions create additional databases named Database
1,
Database
2, etc. This is on a network drive, and it is a replicated
database.
Is the new file that is created the new version of the compacted
original
and should it therefore be renamed and the original be deleted?
The
orginal
database size doesn't change, the new one that is created is
considerably
smaller. Also, should the replicated copies be individually
compacted
and
repaired or does repairing the main database automatically compact
the
others?
Any advice is much appreciated! Thank you.
The way compaction works is that Access creates a new database
(Database
1, 2,
3... etc. depending on what is already there); copies all objects
from
the
current database into it; moves control to the new database,
renames
it,
and
deletes the old one.
I suspect that you don't have full read, write, create and delete
privileges
on the folder containing the database. You need all of these to
complete
the
compaction operation! Check your Windows privilege on the folder.
John W. Vinson [MVP]
