FRM-99999 Error 408 Occurred [message #117987] |
Mon, 02 May 2005 08:05 ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
lavallee_g
Messages: 22 Registered: May 2005 Location: Quebec
|
Junior Member |
|
|
Hi,
Is there an easy way to get rid of error (FRM-99999 Error 408) , in Forms 6.0.8.22.1, DB 9.2.0.4.0. ????
The problem is caused by a constrain DEFERRABLE
ex:
ALTER TABLE FISTON ADD
CONSTRAINT FIST_PAPA_FK
FOREIGN KEY
(
PAPA_ID
)
REFERENCES PAPA
(
PAPA_ID
)
DEFERRABLE
INITIALLY DEFERRED
/
When you delete a child AND a parent then commit, forms only send the deletion of the parent instead of the child THEN the parent.
Looks like forms get lost in is logic who usualy commit the parent before the child.
What can I do?
Thanks
[Updated on: Mon, 02 May 2005 10:59] Report message to a moderator
|
|
|
|
Re: FRM-99999 Error 408 Occurred [message #118165 is a reply to message #117987] |
Tue, 03 May 2005 07:33 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
lavallee_g
Messages: 22 Registered: May 2005 Location: Quebec
|
Junior Member |
|
|
Hi,
It may help but my problem is only with the delete. Instead of a deferred foreign key, a cascade delete may be used. The only problem with cascade delete is that is too powerfull. If not used with caution, it can delete A LOT of data.
Thanks for the hints, I'm already trapping my constraints message in a on-error, I can adjust it to supress FRM-99999.
Genevieve
[Updated on: Tue, 03 May 2005 07:35] Report message to a moderator
|
|
|
|
|
|
|
Re: FRM-99999 Error 408 Occurred [message #118568 is a reply to message #117987] |
Thu, 05 May 2005 20:52 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) |
![](/forum/images/custom_avatars/67467.jpg) |
djmartin
Messages: 10181 Registered: March 2005 Location: Surges Bay TAS Australia
|
Senior Member Account Moderator |
|
|
My apologies. I just reread the doco and the cascade only works for the detail blocks that have been defined in the form. Therefore, you would have to define a detail block and relationship to ALL of the subordinate tables to get the delete of the parent to automatically delete the children.
Suggestion: Create a pre-delete trigger for your parent table that contains a 'delete from child_a where parent = :par_blk.id' for each of the child tables. This should probably be a procedure in your database so that it can be maintained independantly from the form.
David
|
|
|