Re: Forms 6i and Oracle 8i
Date: Wed, 10 Jan 2001 11:07:47 -0500
Message-ID: <mH076.172$G32.778145976_at_radon.golden.net>
I use this all the time and it works, here is what you do
- block query data source is your view name
- block the dml target is your actual table
- mark all the items in the block that are not part of the target table as query only YES
No override triggers required as Forms will build the proper SQL this way
"Andy Collins" <andy.collins_at_clara.co.uk> wrote in message
news:oe566.19515$0d.1202011_at_nnrp4.clara.net...
> Hi,
>
> I've created a view on the database and based a block upon it. In order to
> update the data I use an On-Update trigger to maintain the data on the
base
> tables. Running against DB 7.3.4 it works correctly but we are in the
> process of upgrading to 8.1.6 and testing against this platform message
> 'FRM-40654: Record has been updated by another user. Re-query to see
change'
> appears when any data is updated. Note, this is when data is changed on
the
> form and not when commited to the database.
>
> Removing the On-Update trigger gives message 'FRM-40602: Cannot insert
into
> or update data in a view' which is as expected.
>
> My resolution has been to create an 'INSTEAD OF' trigger on the view which
> only contains 'NULL;' within the body thus allowing the original code to
> work.
>
> Have I missed a property on the block or is this how Forms works against
> Oracle 8i?
>
> Forms version 6.0.8.10.3 - 6i with patch set 1.
>
> Thanks for your help.
>
> Andy.
>
>
Received on Wed Jan 10 2001 - 17:07:47 CET