I would like to save some values on a table when creating a new record (DataDictionary). These values would be obtained from a parent table. However I want to implement it in the DD class, not in the view where the DD is used. This has a potential point of failure: What happens if this DD is used on other view and the parent is removed from the structure? I would like to prevent this.

This is my view code:

Code:
Object oPARENT_DD is a cPARENTDataDictionary
End_Object

Object oCHILD_DD is a cCHILDDataDictionary
    Set DDO_Server to oPARENT_DD
    Set Constrain_file to PARENT.File_number
End_Object

///// cCHILDDataDictionary class
// More code here...
Procedure Creating
    Forward Send Creating
    
    Move CHILD.COLUMN1 to PARENT.VALUE_WHEN_CREATED1
    Move CHILD.COLUMN2 to PARENT.VALUE_WHEN_CREATED2
    Move CHILD.COLUMN3 to PARENT.VALUE_WHEN_CREATED3
End_Procedure
This structure should be keep in every view. But I want to avoid potential issues: if Remove_Server_File is used in a new view and the PARENT table is removed, the DD class won't work correctly as it will move whatever value the buffer had to the new record. The alternative is to move this Creating event to every single view where the DataDictionary is used.

What would you do in this case?