All FRM messages are suppressed after buissness rules validation

Question

hello,
i've just discovered this really odd and annoying problem and I need some help. After validating business rules all forms messages are suppressed. If I re-enter the form, messages appear again, but are "visible" only till next business rules validation.
this is the scenario:
1. When I enter the form, I disable all business rules
2. I insert some data and commit. Message FRM-40400 appears.
3. I validate business rules by pressing button "Validate" (I call procedure which enables all business rules, calls procedure capi.validate_all_static_br, disables business rules and displays errors with Qms$errors.RaiseQMSFailure)
4. if i change some data and commit, message FRM-40400 does not appear.
I've done some debugging and discovered problem in qmslib65.pll package qms$forms_errors procedure push
PROCEDURE Push
( p_msg IN VARCHAR2
, p_error IN VARCHAR2 DEFAULT 'I'
, p_msg_type IN VARCHAR2 DEFAULT ''
, p_msgid IN NUMBER DEFAULT 0
, p_loc IN VARCHAR2 DEFAULT '') IS
-- Purpose Show message to the end-user, standard procedure for the Oracle Forms
-- Generator of Designer/2000 to pass the display and handling of a message
-- to a user created procedure.
-- Usage Called by the Oracle Forms Generator code
-- Parameters : msg Text message
-- error ERRor or WARNing
-- msg_type ORA, API or user TLA
-- msg_id Id of message
-- loc Location where error occured
-- Remarks
v_msg VARCHAR2(2000) := p_msg;
v_error VARCHAR2(2000) := p_error;
v_servermsg VARCHAR2(2000) := DBMS_ERROR_TEXT;
l_empty_errorrec hil_Message.message_rectype;
BEGIN
IF p_msgid != 0
THEN
g_errorrec.severity := p_error;
ELSIF ((SUBSTR (v_msg, 1, 11) = 'API Error: ')) OR
((INSTR (v_servermsg, 'ORA-20999') <> 0) AND (v_msg IS NULL)) OR
(INSTR (v_msg, 'ORA-20999') <> 0)
THEN
-- error returned from the API, just display no further action required ?
HandleServerAPIError (p_msg);
-- M. Kappel
/* 11-apr-2001
- Allow check of v_servermsg even if v_msg contains data.
- With new-style cdm ruleframe, v_msg contains 'ORA-20998'.
We never looked at v_servermsg because v_msg was not null.
- With old-style database trigger business logic, v_msg contains only text.
If we still never look at v_servermsg, we don't identify that the error is
a 20998 and therefore we raise an alert 'Transaction Failed' instead of
showing the 'Errors in this Transaction' window.
-- ELSIF ((INSTR (v_servermsg, 'ORA-20998') <> 0) AND (v_msg IS NULL)) OR
-- (INSTR (v_msg, 'ORA-20998') <> 0)
-- THEN
ELSIF (INSTR (v_servermsg, 'ORA-20998') <> 0) OR
(INSTR (v_msg, 'ORA-20998') <> 0)
THEN
HandleServerApplError (p_msg);
-- error returned from the API, just display no further action required ?
ELSIF ((INSTR (v_servermsg, 'ORA-20000') <> 0) AND (v_msg IS NULL)) OR
(INSTR (v_msg, 'ORA-20000') <> 0)
THEN
-- error was raised by old Headstart code with raise_application_error
-- strip ora-20000 : , check if code (get message) or message
HandleOldHeadstart (v_servermsg);
ELSIF (SUBSTR (v_msg, 1, 3) IN ('FRM', 'MNU', 'PLS', 'SRW', 'ORA', 'REP'))
THEN
HandleOracleError (v_msg, v_error);
ELSE
     HandleApplError(v_msg, v_error);
END IF;
Display_Error (g_errorrec);
g_errorrec := l_empty_errorrec;
END Push;
IMO, this part of code
ELSIF (INSTR (v_servermsg, 'ORA-20998') <> 0) OR
(INSTR (v_msg, 'ORA-20998') <> 0)
is either obsolete or incomplete. It should be something like this:
ELSIF (INSTR (v_servermsg, 'ORA-20998') <> 0 AND(v_msg IS NULL)) OR (INSTR (v_msg, 'ORA-20998') <> 0)
i would like to know if anyone have simmilar problem and if there are any other solutions then above mentioned.
Kind regards,
Damjan

Answer 1

I'm having the same problem, i'm using 6.5.22 with the C/S-kit
Is there already a solution for this problem?
Regards,
Richard Teunissen