Error during "compact on close"::

Hi,

I always set the 'Compact on Close' option for my new db's, but I am starting to wonder if this is such a good idea.

I have a collection of 20 or so single-table, very simple db's (there's a reason, moot for this question), where data is only being added to records that already exist in the table. No records (or very few) are being added and/or deleted.

I have suddenly started to receive an error on compact on close, something to the effect of "... Access can not delete [tablename] after compacting.... saving to new name db1.mdb [etc]... try removing read-only ...."
Sorry I don't have the exact message, will get it if it happens again, but thought this was enough to go on, if it's happened to anyone else.
btw, Access2002/WinXP/P4 yadda .. Db's were copied from my local hard drive to a network drive on a server. The user accesses the db's there. Could it have anything to do with that? The db files have full perms for everyone, and are not 'read-only'. could it be at the folder level?

Have posted this in a couple other places to no avail. Guess this isn't as common as I'd thought it may be!

TIA!!
Ling663

If you are only adding a deleting record every now-and-then, why waste processing time on compacting DB. Compacting is truly valuable in DB during development, and when Adding and Deleting large volumes of data. Plus in a multi user enviroment a user could be in the DB when someone else exists and that will be a problem too.

I would remove the feature of compacting when closing and just make it so that you as the administrator compact it once a month, or when truly needed, when you know no one is in it.

As far as the actual problem we would need the actual error msg, but I have heard of this one before

S-

Thank you 'sbaxter'! I have removed the option from all the db's and obviously it will save time on closing and remove the chance of errors. Just a matter of habit to have that option set, even tho most of what I do is pretty small, and for single users.

Sometimes I find out that the quirks of Access that I can't understand are simply well-known and matter-of-course, so asking about them in forums such as this gives me some insight in language a bit easier to understand than the MS knowlege base!

thx again!
ling663

I wonder if you might be able to solve my big problem. I have a small front end, backend database that continually crashes on closing, but only, so far as I can tell when "Compact on close is set" or when you ask it to compact amnd repair. It seems to happen on some machines and not others, although the build state of NT and Office 2000 appears to be the same. It also does it on WinXP and Office XP machines. It is driving me crazy, I have contacted MS helpline but to date they have been unable to help - any ideas would be gratefully accepted.
Regards
Barney

Are there other users in the DB when the compacting is to take place?

S-

No, it happens when I have the dB open exclusively

R
Barney