Re: Unwanted FORMS 3 message
Date: 1995/04/28
Message-ID: <3nr8kq$ik5_at_mother.usf.edu>#1/1
In article <139_at_along.dialix.oz.au>, paladin_at_along.dialix.oz.au (Alex Long) says:
>
>
>In article <1995Apr12.181516.4511_at_bilpin.co.uk>, Tony Desborough (tony_at_bilpin.co.uk) writes:
>>
>>Hi,
>>
>>Can anyone tell me how to get rid of the following SQL*FORMS 3 message,
>>which has has habit of appearing just when you don't want any
>>operator input :-
>>
>>"Please acknowledge message. (OK)"
>>
>>Thanks in advance.
>>Tony
>>--
>>----------------------------------------------------------------------------
>>Tony Desborough SRL Data Ltd
>>Software Programmer 1, Perren St
>>Email: tony_at_bilpin.co.uk LONDON, NW5 3ED
>Hi Tony,
>
>I don't have my manuals at home, so I am using a faulty memory, but
>here goes.
>
>The message is system generated, and the severity of the message
>is graded from 5 to 25 (Gentle reminder to 'I hope you a have a
>backup'). You can set the form to ignore error messages below a
>certain level with a KEY-STARTUP trigger. The exact syntax esacpes
>me.
>
>Another way, is with a ON-ERROR/ON-MESSAGE type of trigger, where
>you inetrcept a message by the FRM-xxxx number, and then either
>ignore it, or cause something to happen.
>
>I hope that helps.
>Regards,
>Alex Long
>
The syntax is: :SYSTEM.MESSAGE_LEVEL := 10; (level 0 is normal all messages level). I would stongly suggest not just setting the level to the highest level and leaving it there. You may mask error messages that you really should get.
Are you getting this message because you issued a MESSAGE command and subsequent MESSAGE is attempting to write to the message line but waiting for the user to acknowledge the previous message? For example:
MESSAGE('Starting processing');
... some processing occurs ...
MESSAGE('Done processing');
The second MESSAGE will prompt the user to acknowledge the first MESSAGE.
If this is the case, you may be able to place a non-database field on a pop-up page, assign your message string to the field and then pop it up over the message line. This allows you to do:
:POP_UP_BLOCK.MESSAGE_FIELD := 'Starting processing';
go_block('POP_UP_BLOCK.MESSAGE_FIELD');
... some processing occurs ...
:POP_UP_BLOCK.MESSAGE_FIELD := 'Done processing';
If you are not issuing a series of MESSAGE commands, I would investigate under what situations the message appears. It may indicate that there may be a problem in the code that setting the message level would only mask the problem. If possible I would step through the code with debugger and determine what command is causing the message to appear. Received on Fri Apr 28 1995 - 00:00:00 CEST