Re: Forms 3.0.16 - Commit in a form called from another form

In article <3v600g$b9t_at_pheidippides.axion.bt.co.uk>, Anna Hedington says...
>
>Any ideas how I can commit changes in a called form before returning
>to the calling form, which needs sight of the changes for a Pro*C user
>exit??

Anything POSTed to the database before your user exit is called should be visible to that user exit, since it shares the same Oracle session.

>
>The calling form calls the new form and the user exit in a PRE-UPDATE
>trigger. The new form is an enhancement to a well established form.
>
>COMMIT in the called form produces 'FRM-40403: A calling form has unposted
>changes. Commit not allowed'. Changing KEY-COMMIT to 'POST' and KEY-EXIT
>to 'EXIT_FORM(NO_ROLLBACK)' in the called form produces encouraging
>messages, ie 'n records posted' etc, but the changes appear to be lost
>on return to the calling form.

Try including a POST in the _calling_ form, just before the call statement. The second form should then not need any special treatment: it shouldn't care whether it's running stand-alone, or called from another form (as in this case). You may see a slight difference in the messages, but that's all.

-- 
 _________________________   __________________________________________
/  Tommy Wareing          \ /  I've been looking for an original sin,  \
|  p0070621_at_brookes.ac.uk  X   One with a twist and a bit of a spin    |
\  0865-483389            / \     -- Pandora's Box, Jim Steinman       /
 ~~~~~~~~~~~~~~~~~~~~~~~~~   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~