Corrupting MDB Files

[Tom Gaughan]

We have small Access 2002 database files that are used to temporarily keep orders stored unitl they are processed and sent to SQL Server. Periodically when a user tries to even just access the order table we are getting the following error:

You cannot add or change a record because a related record is required in table 'MSysAccessStorage'

No error number is given on the messagebox.

Typically the most active order table only contains around 200 records before they are purged. Because of the frequency of adding and deleting records, we have a VB application that runs a compact on the database files every night. The compacts do run successfully every night. The first person to access the database raises the error. The only solution we have is overlaying the Access file with a backup from another server.

Database files are located on a Novell server. Users are running Windows 2K, some are on XP. We had used these files for close to 5 years before this problem started occurring.

Thanks in advance,
Tom

 

[Arvin Meyer [MVP]]

Try converting your database to Access 2000 which doesn't have an
MSysAccessStorage table (it uses an MSysAccessObjects table instead) If it
still corrupts, the corruption probably exists due to the VB compaction.
Instead try using the Windows scheduler with an Access form that compacts
the database. Have a look at Tony Toews corruption page for some other
suggestions.

http://www.granite.ab.ca/access/corruptmdbs.htm

--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access
We have small Access 2002 database files that are used to temporarily keep
orders stored unitl they are processed and sent to SQL Server. Periodically
when a user tries to even just access the order table we are getting the
following error:

You cannot add or change a record because a related record is required in
table 'MSysAccessStorage'

No error number is given on the messagebox.

Typically the most active order table only contains around 200 records
before they are purged. Because of the frequency of adding and deleting
records, we have a VB application that runs a compact on the database files
every night. The compacts do run successfully every night. The first
person to access the database raises the error. The only solution we have
is overlaying the Access file with a backup from another server.

Database files are located on a Novell server. Users are running Windows
2K, some are on XP. We had used these files for close to 5 years before
this problem started occurring.

Thanks in advance,
Tom