compact/repair does not make db smaller

[Guest]

my database has run around 40 mb for a couple of years (Access 2000) and now
it has swollen to 166 mb and when I run compact & repair, it stays the exact
same size every time. It also makes a new database named db1, db2, etc every
time I run compact & repair...and that db is also 166 mb!

Can anybody tell me what I'm doing wrong?? I go to Tools - Database
Utilities to run compact/repair. The database has security and opens from a
shortcut using a special mdw file. However, it has always been this way, and
a few weeks ago is the first time we've ever had this problem.

Thanks for any help!!
Susan

 

[John Vinson]

my database has run around 40 mb for a couple of years (Access 2000) and now
it has swollen to 166 mb and when I run compact & repair, it stays the exact
same size every time. It also makes a new database named db1, db2, etc every
time I run compact & repair...and that db is also 166 mb!

Compact works by copying the current database contents to a new
database; by default it's named db1, but the 1 will increment if there
is already such a database in existance. It then checks to see if the
new database is intact, and if so deletes the old one and renames the
new one. I'm not certain of the exact sequence of these operations
but... if you have a db1 (db2, db3) left around then the compact is
NOT working correctly!

Can anybody tell me what I'm doing wrong?? I go to Tools - Database
Utilities to run compact/repair. The database has security and opens from a
shortcut using a special mdw file. However, it has always been this way, and
a few weeks ago is the first time we've ever had this problem.

There may be some corruption that Access cannot handle, or possibly
you don't have Windows create/read/write/delete privileges on the
folder containing the database. Check the privileges for the account
you're using; if they are ok, then I'd suggest using Access user
interface to create a *completely new* database. Use File... Get
External Data... Import to import everything from your current
database. Check that the table reltions are correct, and you may need
to reset the security.


John W. Vinson[MVP]

 

[Guest]

Thanks! I tried to make a new database and import these objects, but it
won't let me import from that database because of security. It doesn't ask
for a password, just says I don't have permission. Is there a way around
this? Can I remove the security to do this, then add it back to the new
database?

Thanks!

 

[John Vinson]

Thanks! I tried to make a new database and import these objects, but it
won't let me import from that database because of security. It doesn't ask
for a password, just says I don't have permission. Is there a way around
this? Can I remove the security to do this, then add it back to the new
database?

I think what you'll need to do is use Tools... Security... Workgroup
Manager to Join the workgroup used for the damaged database; then
create the new database, logging in as an Admins user. You should then
be able to do the import.

John W. Vinson[MVP]