compact and repair issue

[dpimental]

All, I have databases on a network drive.

I am using Access 2002 and the datbases have linked tables, some to other access dbs and some to oracle db.

When I try to compact and repair, it creates a db1.mdb, but never compacts and repairs the actual database. It appears that the db1.mdb is the compacted db.

Also, if I copy the file to my c drive, it works without a problem.

David Pimental
(US, Oh)

 

[genomon]

We have never been able to compact modest to large mdb's on a server. The db1 is what is left over when the compact fails (look at the size). Our network people offer no solution other than there may not be enough memory on the server; maybe could be a bandwidth issue from having the app open on the client, but not sure about that. Best way for us is to compact it locally, then copy back to the network. Nice to hear we aren't the only ones...

Beir bua agus beannacht!

 

[mcelligott]

Hello,

If I may add my 2 cents.

I have been compacting and repairing both my front-end and back-end portions of my databases on a monthly basis for several years now (the back-end resides on the server, front-end on the local machine plus a copy of the front-end on the server which I use for programming purposes). I have never had an issue. I have to do it monthly because the database gets very large (approx 1.5 gb uncompacted to 450 mb compacted).

I have set aside two icons (one for the front-end and one for the back-end on the server) that I use only to do programming or compacting and repairing. These icons connect me directly to each (the regular user connects indirectly so they can only change what I authorize them to change - its an additional security thing for me). I kick everyone out of the database (which can be difficult being a 24 hour operation) and do the compact and repair. Usually takes about 5-10 minutes.

I'm sure that is clear as mud. My description of the process isn't the best but it does work.

Bob

 

[dpimental]

Thank you both. I know it's possible. I believe the issue is not related to access. I think that the server's disk is almost full. Thanks again!

David Pimental
(US, Oh)