I have an application running on a network with 5-10 simultaneous users. Main tables are "Orders" and "OrderDetails" in a one to many relationship with integrity set. For some reason (possibly network problems) a few "OrderDetails" got created without corresponding "Orders" in spite of the fact that the input form mandates creating the "Orders" first.
What this did, however, was eliminate the entire relationship between the two tables with no warning. The symptom was in the input form when the subform with the "OrderDetails" no longer was visible--or probably not even there on the form. The subdatasheets no longer worked as well.
I could re-establish the relationship after deleting the orphan records but users were totally confused when the system stopped working for them with no warning.
My question: How can I prevent this from happening (enforcing relational integrity didn't stop the behavior on the whole process) or how can I get some type of warning that the errors are taking place?
What this did, however, was eliminate the entire relationship between the two tables with no warning. The symptom was in the input form when the subform with the "OrderDetails" no longer was visible--or probably not even there on the form. The subdatasheets no longer worked as well.
I could re-establish the relationship after deleting the orphan records but users were totally confused when the system stopped working for them with no warning.
My question: How can I prevent this from happening (enforcing relational integrity didn't stop the behavior on the whole process) or how can I get some type of warning that the errors are taking place?
