Re: FRM-40401

From: Steve Johnson <robertoc_at_fyiowa.infi.net>
Date: 1997/08/04
Message-ID: <33E60E11.1E72_at_fyiowa.infi.net>#1/1

There's one of two things you can do.

1. FRM-40401 is an error at Level of 5. If you set your :System.message_level to 10 you won't see this message. Then when you're done you can reset the level to whatever it use to be.

    DECLARE
      hold_lvl VARCHAR2(5) := :SYSTEM.message_level;     BEGIN

      :SYSTEM.message_level := '10'
      commit;
      :SYSTEM.message_level := hold_lvl;

    END; 2) This is probably the best solution. Issue FORMS_DDL('commit');

Hope this helps.

Steve J.

Pat Doran wrote:
>
> I have a problem,
>
> I have a form which is based on a view that I DO NOT want to modify. I
> would like to have the user be able to navigate throughout this view via
> the form and apply updates (via a button that executes some PL/SQL) to a
> different table based on what they currently have in the form. Whenever I
> attach a trigger to the update button 1 of 2 things happens.
>
> 1. If I include a commit at the end of the update statement in the PL/SQL
> the update occurs but I get the error message FRM-40401 No changes to
> apply, even though the update happens!!! How get I stop this message? I do
> not want to update the form or it base view, I only want to execute the
> PL/SQL attached with the button trigger...it appears that the commit in
> PL/SQL is being interpreted as a Forms do_key(commit_form)
>
> 2. If I do not include a commit or a do_key(commit_form) then the changes
> are rolled back once I exit the form. But I don't get an error message....
>
> Any help would be greatly appreciated, this is driving me nuts
> pdoran_at_lucent.com
Received on Mon Aug 04 1997 - 00:00:00 CEST