L
Ling
Hi,
I always set the 'Compact on Close' option for my new db's, but I a
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'
a reason, moot for this question), where data is only being added t
records that already exist in the table. No records (or very few) ar
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] afte
compacting.... saving to new name db1.mdb [etc]... try removin
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 har
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 perm
for everyone, and are not 'read-only'. could it be at the folde
level?
TIA!!
Ling66
I always set the 'Compact on Close' option for my new db's, but I a
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'
a reason, moot for this question), where data is only being added t
records that already exist in the table. No records (or very few) ar
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] afte
compacting.... saving to new name db1.mdb [etc]... try removin
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 har
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 perm
for everyone, and are not 'read-only'. could it be at the folde
level?
TIA!!
Ling66