G
Guest
Lately, whenever a small Microsoft Access 2000 database at a hospital
undergoes a stress due to computer (or Access) crash , a nonesense record
with some values is inserted in one of the tables, where the ID# is left
blank/null, even though in the design it is a primary key and so should be
unique and not NULL.
This record automatically generated by Access software cannot be removed by
compacting and repairing. Often I've to create a new table and copy all the
records into it, except the nonesense record. This is cumbersome, some when
there are thousands of records. Sometimes I find that a table link
(one-to-many) is broken during one of the crashes, and I've to manually find
and match keys on "many" side with the one on "one" side, including deleting
records on the "many" side.
Is there any design improvement or VBA program one can add to the database
to prevent crash errors resulting in a record being corrupted or new one
inserted?
Thank you.
David
undergoes a stress due to computer (or Access) crash , a nonesense record
with some values is inserted in one of the tables, where the ID# is left
blank/null, even though in the design it is a primary key and so should be
unique and not NULL.
This record automatically generated by Access software cannot be removed by
compacting and repairing. Often I've to create a new table and copy all the
records into it, except the nonesense record. This is cumbersome, some when
there are thousands of records. Sometimes I find that a table link
(one-to-many) is broken during one of the crashes, and I've to manually find
and match keys on "many" side with the one on "one" side, including deleting
records on the "many" side.
Is there any design improvement or VBA program one can add to the database
to prevent crash errors resulting in a record being corrupted or new one
inserted?
Thank you.
David