1 of 1 people found this helpful
The simplest might be to just mark the parent record as "deleted" by changing the value of a field defined for that purpose and design your user interface to "hide" the deleted records from the user's view.
Otherwise, you are looking at replicating your entire data model--possibly with some simplifications or you may be able to "flatten" your data, and importing multiple sets of records into that copy of your system prior to deleting the actual records from your main system.
The two options are not mutually exclusive. You can initially "mark" the records and then, late at night, a server scheduled script can archive and delete all records marked that day or all records more than X days old.
This worked great, Phil. Once you mentioned it, I remembered seeing it used before. Thanks!