FRM-41106 You cannot create records without a parent record.

Question

Hello!
Forms 6i.
I have a Parent-Detail-Relationship. At the Detail-Block a "When-create-record" sets some default values on the Detail-Block.
I got error "FRM-41106 You cannot create records without a parent record" when the Parent-Block executes a execute_query.
I debuged the problem an found out, that the error appears in the standard-programunit "Clear_All_Master_Details".
The error appears, when the code is deleting the detail-block "code: Clear_Block(NO_VALIDATE)".
This is strange: The error appears only when I uses the "When-create-record"-trigger on the detail-block.
If a comment out the trigger, no error appears.
Why Is a "When-create-record"-trigger initiated when deleting the detail-block?
Default-Code of "Clear_All_Master_Details":
-- Clear all the detail blocks for this master without
-- any further asking to commit.
currel := Get_Block_Property(trigblk, FIRST_MASTER_RELATION);
WHILE currel IS NOT NULL LOOP
curdtl := Get_Relation_Property(currel, DETAIL_NAME);
IF Get_Block_Property(curdtl, STATUS) <> 'NEW' THEN
Go_Block(curdtl);
Check_Package_Failure;
Error appear here----> Clear_Block(NO_VALIDATE);
IF :System.Block_Status <> 'NEW' THEN
RAISE Form_Trigger_Failure;
END IF;
END IF;
currel := Get_Relation_Property(currel, NEXT_MASTER_RELATION);
END LOOP;
Thx in advance,
Wolfgang

Answer 1

Wolfgang,
To be honest, I've always done this kind of thing in the Pre-Inse rt or Pre-Upda te triggers. Why is it so important for the user to see the value of these field BEFORE the IN SERT or UPDAT E? Once the record is commited, they will see these values in your form. In my experience - users are typically satisfied with this approach. If your users are not OK with this approach, perhaps you could us a When-Validate-Record trigger instead of the When-Create-Record trigger.
I think the When-Create-Record option would still work, but your code will need a little tweak. Give the following a try:
   IF ( NVL(:termin.best_nr,'MSTR') = NVL(:pos.best_nr,'DTL')
        AND NVL(:termin.best_jj,'MSTR') = NVL(:pos.best_jj,'DTL')
        AND NVL(:termin.best_pos,'MSTR') = NVL(:pos.best_pos,'DTL') ) THEN
       <<...set_values..>>
   END IF;Remember, NULL values do not always get evaluated correctly so it is always best to use the NVL function to ensure fields are evaluated correctly.
BTW, you indicated that you ran DEBUG on your trigger, when your IF statement was evaluated did the "set_Values" section of your code run? If it didn't - do you have other code in your WCR trigger that is setting values outside of your IF statement?
Craig...