Re: FORMS 5. Call_FORM help

Joe

[Quoted] Are you sure about that. It would be wonder to me that a commit in the form didn't commit ever change in the users session !!

Richard Platt

Joe Brown wrote in message <715usr$l4f$1_at_apache.dtcc.edu>...
>When using dml in procedures/triggers in forms use
>
>forms_ddl('commit');
>
>to issue a commit. Forms_commit built-in only commits blocks of the
>form, not implicit cursors in procedures/triggers.
>
>
>In article <3635F3F0.3903249B_at_earthlink.net>,
>Ashok Upadhyay <aupadhya_at_earthlink.net> wrote:
>>Is call form necessary there? If that runs procedures only without any
user
>>inputs, that can be changed to forms/stored procedures and could be called
from
>>calling form itself.
>>
>>Commit_Form or Commit /rollback in procedures should release the LOCK. Is
commit
>>present in procedures? Or use COMMIT_FORM in called form to release the
lock.
>>
>>Thanks
>>
>>mdesouza_at_YAHOO.COM wrote:
>>
>>> Hi
>>>
>>> I have a main form which calls another forms that runs a few procedures
to
>>> perform update deletes and inserts on a table
>>>
>>> when the procedure completes, the locks on the table have not been
released,
>>> the only way the locks are released on that table is when I exit all the
forms
>>>
>>> Can someone explain why , or is there way round this so that when the
>>> procedures complete the locks are released
>>>
>>> regards
>>>
>>> michael dsouza
>>>
>>> -----------== Posted via Deja News, The Discussion Network ==----------
>>> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
>>
>
>
>--
>(: Joe Brown :) joe_at_apache.dtcc.edu
>I believe Wine is going to be great if it ever gets finished. . .
>I believe Linux _is_ great even though it's not finished! ! !
>I believe you have my address. :-)
Received on Thu Oct 29 1998 - 00:59:34 CET