Quote:I wish there was a way to 'search and destroy' any subrecords that had corrup natural linking.
I just found a stray subform record in one of my apps.
This is the process I used:
1) Make a temporary backup copy of your app.
2) Open that temporary copy.
3) Retreive all of the main form (parent) records.
4) After double checking that you are looking at the temporary copy, perform a Mass Delete of all the parent records.
5) Open the subform as standalone in Search/Update mode, and press F10 to see if there are any subform records. If there are, they are orphans, because they should have been removed when the parent records were deleted.
Now, this brings up an issue. How did my app get an orphan subrecord? I am using Natural linking. (I understand how it could happen with Relational linking if my programming failed to fill the key field or some such problem.)
I wonder if this would happen if I created a subrecord, but failed to save the main record?
Ray, it seems that I remember you, or someone at Lantica, explaining something similar to this. Am I correct here?