Strange corruption problem

[Sam Smith]

I have a 2003 10 user database program with all the latest service packs and
patches for Access and Windows.

Once a week I get a corrupt MDB file with errors in the MSysCompactError
table of 1003 and 1053 saying that it cannot find field 'Description' in the
effected table. The thing is there is no field 'description' in the table.
The table itself ends up with loosing its primary key and one of the records
(always one that one of the users has open at the time) is lost with ###
filling all of the fields and other strange characters. What is going on?

Is this just a generic error message and there is a hodden system field that
users cannot see which is called 'description'?

Has anybody else had this problem and if so - solved it?

TIA

---
Sam

[Salad]

Sam Smith wrote:

I have a 2003 10 user database program with all the latest service packs and
patches for Access and Windows.

Once a week I get a corrupt MDB file with errors in the MSysCompactError
table of 1003 and 1053 saying that it cannot find field 'Description' in the
effected table. The thing is there is no field 'description' in the table.
The table itself ends up with loosing its primary key and one of the records
(always one that one of the users has open at the time) is lost with ###
filling all of the fields and other strange characters. What is going on?
Is it the same table each time or is it random tables?

Maybe you can write a routine that will close open Access windows first
before compacting.

Is this a frontend or backend table? DOes this happen with random users
or the same user?


Is this just a generic error message and there is a hodden system field that
users cannot see which is called 'description'?

Has anybody else had this problem and if so - solved it?
TIA

---
Sam