Re: Forms: master-detail problem (primary/foreign key)

From: Stefan Röhle <roehle_at_mail.uni-mainz.de>
Date: Thu, 26 Jul 2001 19:19:26 +0200
Message-ID: <3B60511E.693BEA42_at_mail.uni-mainz.de>


"Matt B." schrieb:
>
> "Stefan Röhle" <roehle_at_mail.uni-mainz.de> wrote in message
> news:3B5ED3FA.3F90AE53_at_mail.uni-mainz.de...
> > Hi,
> >
> > I am currently developing an application with Form Builder (Version
> > 5.0.6.8.0).
> > On one canvas I use a master table and two detail tables.
> > These tables are connected by an ID, which is the primary key of the
> > master table and a foreign key of both detail tables.
> > When I try to save (commit_form) the data entered into all tree tables I
> > get the error ORA-02291: Primary Key not found (or similar, the original
> > message is in German...)
> > This indicates (I guess) that Forms tries to insert the detail data
> > first and of course then the error is quite normal.
> > How can I change the order in which Forms "saves" (insert or update) the
> > changes?
> > Or perhaps I have missed something else?
>
> Are you using the master-detail relation properties in Forms itself or are you
> managing the blocks manually (w/o using the built-in relation functionality)?
>
> -Matt

I have used the build-in master-detail relation properties (when adding the blocks with the wizard).
When I disable the primary and foreign keys everything works fine. It seems as if the order of the sql statements has to be adjusted - but how? Received on Thu Jul 26 2001 - 19:19:26 CEST

Original text of this message