orphan data

[sneddens]

I have created two quite polished database applications and there is one problem remaining for me...

On a data entry form that uses a master file and a related file, sometimes a person may want to change the data in the key field and have it change in all the related records at the same time. Instead what happens is that the related information disappears because the key field has been changed in the master. It's still there but inaccessible except to manually go in and change the key field of the related file. Other users wouldn't know this. How can I design around this?

[spragueg]

You should use an auto enter unique serial number or unique calculation in your master file as the basis for your key. Keep that key hidden from the user. That way the relationship is not broken when the data changes.

[sneddens]

Thanks. Can't believe I got this far without really understanding why to do that.