Errors in QMS$FORMS_ERRORS (headstart 5.0.3)

Hi everybody,
I have 2 questions about the procedure ErrorMessageAlert of the QMS$FORMS_ERRORS package in qmslib50.pll of Headstart 5.0.3.
1.
In the procedure a alert is shown depending on the severity ('E', 'F', 'W', 'Q' and 'I')of the error.
However, at a customer when I open 2 certain forms the mentioned procedure is called with the severity '1'. This one is unknown and I get an alert showing that the alert_id in SET_ALERT_PROPERTY is null.
2.
At the same combination of opened Forms I get an error with severity 'E' and msg-code = '-0' and the message-text is ' ' (i.e. space). In this case an alert is shown which is empty except for '-0:'
Does anyone know about these things? Are these bugs of some sort?
Further info: all the used errors are shown by using qms$show_message('<messagecode>', 'severity', <boolean>);
I already checked if this procedure is called with severity '1' or messagecode '-0'
Hope anyone can help!

Marc,
Question 1. I'm not aware of any known bugs in this area. I can only think that there is code somewhere in these forms (or attached libraries) which is calling qms$show_message incorrectly. I suppose it is also possible that a message was recorded incorrectly in the qms_message_properties table, although in order to do this you would have had to drop the allowable values constraint on Severity. When you call qms$show_message, do you include the severity parameter? If so, try letting it default to the value in the message dictionary.
Question 2. Does this error happen when you open the form? Or when performing some action?
Lauri

Similar Messages

Error-message (qms$trans_error)

We use headstart 6.5.1
In case a Business Rule fails we get the (expected) error-window
showing what is wrong.
In one form we just get the blank error-window, without showing
the error-messages. The only thing we can do is to close the
form (and losing all the changes).
The BR's (and FK and PK constraints) for the same records work
fine in other forms (this means the capi and tapi are OK).
What can be the problem.

Roel,
This is a "bug" in Headstart. I changed the code so that when an error needs to be shown on an invalid item, the error is shown through a popup, and not the error-screen.
Greetings,
Kristof

ORA-0600 from hil_message.get_oracle_messages

I'm not entirely sure whether this is a Headstart problem or not, but it manifests itself on a call to Headstart code.
I have forms generated using Headstart, Des2000 V6.0.3.6.0, Oracle 8.0.4, on NT. They run fine in normal mode, but as soon as I try to run them in debug mode, it drops out with FRM-40735: PRE-FORM trigger raised unhandled exception ORA-00600. When I follow the code through in debug, the path is -
qms$event_form (pre-form, before); qms$errors.show_debug_info; qms$forms_errors.get_debug_flag; qms$forms_errors.init_suppress_message; qms$forms_errors.init_oracle_message. The line at which it actually falls over is the call from init_oracle_message to hil_message.get_oracle_messages (which calls qms_message.get_oracle_messages).
I've checked hil_message & qms_message packages on the db, both are there & valid. I'm running the forms against the user which owns the packages.
Any ideas what might be causing this?
null

Cheryl,
I believe you have run into a known Headstart limitation.
See the Template Package Users Guide, User Interface Generation, Menus, Form attachment Method.
Headstart provides a procedure qms$application.set_start_menu which allows you to call the same form from multiple menus. However, this procedure uses the replace_menu built-in which does not work with the forms debugger.
A call to this procedure is included in your application library, in the init_application procedure.
You have two options:
- comment out that line of code while you are running under debug
- use the Headstart debugger
Regards,
Lauri

No commit-message (FRM-40400) == Bug in Headstart

Hello,
On committing on or more business rules are violated the 'message-window' appear.
After correcting the errors and committing the changes i'm not getting the usual
'commit-message' (FRM-40400). This only happens after on or more business rules are violated.
This is caused by a bug in the procedure 'QMS$FORMS_ERRORS.PUSH'. Below the solution i have implemented (the complete procedure is displayed). I'm using version 6.5.4.0 of the library 'qmslib65.pll.
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
On committing on or more business rules are violated the 'message-window' appear.
After correcting the errors and committing the changes i'm not getting the usual
'commit-message' (FRM-40400). This only happens after on or more business rules are violated.
When one or more business rules are violated application error ORA-20998 is raised. To
detect this DBMS_ERROR_TEXT is used ==> DBMS_ERROR_TEXT contains ALWAYS the text of the
LAST (dbms-)error (the text contains 'ORA-20998').
Even when no business rules are violated it's possible that DBMS_ERROR_TEXT contains 'ORA-20998'.
In that case no FRM-, MNU-, PLS-, SRW-, ORA- or REP-messages are displayed, because the error is
treated as a voilation of one or more business rules. To avoid this 'v_error = E' is added to the IF-clause:
when one or more business rule are violated this procedure is called to display an error (p_error ==> E);
for displaying the FRM-, MNU-, PLS-, SRW-, ORA- and REP-messages this procedure is called to display an
information (p_error ==> I).
When Designer generates code to validate p.e. check-constraints it will call this procedure too. See the example
below:
IF (:FUNCTIES.MIN_LEEFTIJD < :FUNCTIES.MAX_LEEFTIJD) THEN
NULL;
ELSE
qms$forms_errors.push('CBB-00219', 'E', 'OFG', 0);
qms$forms_errors.raise_failure;
END IF;
In this case the procedure is called to display an error. To avoid that the error is incorecctly treated as a
violation of one or more business rules '(p_msg_type != 'OFG' or p_msg_type is null)' is added to the IF-clause.
ELSIF v_error = 'E'
AND (p_msg_type != 'OFG' or p_msg_type is null)
AND ( 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;

you can create a KEY-COMMIT form level trigger with the following :
declare
msglvl varchar2(3) := :system.message_level ;
begin
:system.message_level := 5 ;
commit_form ;
:system.message_level := msglvl ;
end ;
or put instruction : clear_message; before the commit_form ;

Qmslib50 errors compilation

Hi,
I use designer 6i r43 with headstart 2.1.2 patchs 13 database oracle 9i 9.0.1
when iwant to compile qmslib50 ihave get this message :
in the package corps (QMS$FORMS_ERRORS) procedure (INIT_SUPPRESS_MESSAGE)
at line : SET_GROUP_CHAR_CELL (g_suppress_error_colid, v_rowindex, v_suppmesg(i_rowindex));
the message errors is :
'''' les diclarations tables PL/SQL doivent utilisi des index binaires''''
in english:
''''the table PL/SQL declarations must use the binary index''''.
any help.

Hi,
I use designer 6i r43 with headstart 2.1.2 patchs 13 database oracle 9i 9.0.1
when iwant to compile qmslib50 ihave get this message :
in the package corps (QMS$FORMS_ERRORS) procedure (INIT_SUPPRESS_MESSAGE)
at line : SET_GROUP_CHAR_CELL (g_suppress_error_colid, v_rowindex, v_suppmesg(i_rowindex));
the message errors is :
'''' les diclarations tables PL/SQL doivent utilisi des index binaires''''
in english:
''''the table PL/SQL declarations must use the binary index''''.
any help.

Closing Application - Headstart bug?

This mail was originally posted on the ODTUG maillist.
I am using Headstart Qms 5.0 and we are having problems with closing the
application window using the Windows Close button[x]. Detailed description
follows:
When window is closed by pressing the 'x' found at the right topmost part of
the screen, a message appears confirming whether to commit, not commit or
cancel changes. Once cancel button is pressed, it creates infinite loop or
sometimes shows the same message several times.
The temporary workaround was to comment out the before code added by QMS in
the key-exit trigger: qms$event_form('KEY-EXIT');
/* CGAP$TES_SEQUENCE_BEFORE */
/*begin
qms$event_form('KEY-EXIT');
end; */
/* CGNV$CLOSE_ALL_WINDOWS */
BEGIN
CGNV$.nav_enter_query := FALSE;
IF (:SYSTEM.MODE = 'ENTER-QUERY') THEN
exit_form;
ELSE
CGNV$.CLOSE_ALL_WINDOWS;
END IF;
END;
/* CGAP$TES_SEQUENCE_AFTER */
begin
qms$event_form('KEY-EXIT','AFTER');
end;
Although this solves the problem of infinite loop, this needs to be further
investigated because the code is actually handling the case where system
mode is 'ENTER-QUERY':
procedure close_current is
-- Purpose: Exit form, regardless of form mode
begin
-- Cancel query mode when running in query mode, and then
-- perform do_key('exit_form') as OFG generates code in KEY-EXIT trigger
to close
-- child forms when preference NAVCCF is set to Yes
do_key('cancel_query');
if name_in('system.mode') = 'ENTER-QUERY'
then
copy('10','system.message_level');
exit_form;
copy('0','system.message_level');
end if;
g_closing_current := true;
do_key('exit_form');
exception
when form_trigger_failure then raise;
when others then
qms$errors.unhandled_exception('qms$form.close_current');
end close_current;
Looks like a Qms bug to me. Is anyone familiar with this? All help highly
appreciated.
Rgds,
Siggi

This reply was originally posted on the ODTUG maillist.
I ran into this problem. It was a Forms 5.x bug. It was definitely fixed
in 6.0. I can't remember the patch set in 5.0 that fixed it. It was not a
Headstart problem, but rather a Forms bug.
Mari Cobb
Oracle Certified Professional
Independent Consultant
Sacramento, California www.ms-mari.com
null

When window closed shows qms$trans_errors window

Hello,
I want to report the following problem, regarding qmslib65.pll, revision 6.5.1.12.
To show the problem, I do the following actions:
1. In my form I delete a record (which has details record, that are not shown in the form)
2. I try to close the window and I see an popup window, asking me if I want to save the changes
3. I answer Yes and due to the restricted relation between this record and its details I see a popup window, telling me that this delete action is not allowed.
4. The next thing that happens is that the form is showing me the qms$trans_errors window with no information at all.
My guess is that this is due to the qms$window.when_window_closed procedure, present in the qmslib65.pll, especially the follwing code:
if l_last_window
then
if qms$errors.show_message('QMS-00158')
then
commit_form;
if name_in('system.form_status') <> 'QUERY'
then
go_block('QMS$TRANS_ERRORS');
raise form_trigger_failure;
end if;
else
exit_form(no_validate,full_rollback);
end if; -- show message
end if; -- last window
Notice the go_block('QMS$TRANS_ERRORS') line. In my opinion the violation of the FK restricted constraint is not handled by any business rule (qms$transaction) and therefore the go_block('QMS$TRANS_ERRORS'); statement is obsolete in this case.
What I want to do know is create a workaround to avoid showing the qms$trans_errors window if no business rule is violated, when closing the window. Any ideas?
With regards,
William de Ronde

This is known bug #2283122. It was fixed in Headstart patch 6.5.2.2, which is available via the supplement option.
Basically, we added a bit of code to check the number of messages on the cg$errors message stack just before going to the QMS$TRANS_ERRORS block. We now only go to the block if the number of messages is > 0.
Regards,
Lauri

I: Headstart 2.1.2, Obsolete Webforms workarounds

Resolved issues in webforms
Headstart for Designer 6.0 and Developer Server 6.0 (patch 5 or higher)
In developer server 6 some issues are resolved where headstart had workarounds for. This document describes the changes that you can apply to
the headstart libraries to remove these workarounds.
1. Show tooltips on the web
In previous developer server versions (before developer 6.0 patch 5), tooltips on the web did not work. As a workaround, tooltips where shown
in the MDI console at the when-new-form-instance. To remove this workaround:
qmsevh50.pll, procedure qms$event_item
Remove the following lines of code:
if qms$help.tooltips_enabled
and qms$application.get_user_interface = 'WEB'
then
qms$item.show_hint;
end if;
qmslib50.pll, package qms$block, procedure init_tooltip
Remove the following lines of code:
if qms$application.get_user_interface = 'WEB'
then
return;
end if;
2. Multiselect SHIFT- and CTRL-click
The problem with multiselect functionality on the web concerned the system variable :system.mouse_button_shift_state. This variable did not
give the right status on the web. The problem can be solved by looking at the variable :system.mouse_button_modifiers. To apply the change,
replace the following procedure in pakage QMS$MSEL:
procedure change_selection
is
l_select_key varchar2(50) := upper(name_in('system.mouse_button_shift_state'));
begin
If (l_select_key = 'SHIFT+'
or g_selection_scope = 'RANGE_SELECT'
and get_range_select_start > 0
Then
SelectRange;
Else
If l_select_key = 'CTRL+'
or g_selection_scope = 'INCREMENTAL_SELECT'
Then
ToggleCurrent;
Else --no interpretable modifier key
If IsSelected
then
unselect_all(name_in('system.cursor_block'));
else
unselect_all(name_in('system.cursor_block'));
SelectCurrent;
end if;
End if;
End if;
exception
when form_trigger_failure then raise;
when others then qms$errors.unhandled_exception('qms$msel.change_selection');
end change_selection;
with this code:
procedure change_selection
is
-- l_select_key varchar2(50) := upper(name_in('system.mouse_button_shift_state'));
-- mva, 05-10-2000 workaround for bug 756682: use mouse_button_modifiers!
l_select_key varchar2(50) := upper(name_in('system.mouse_button_modifiers'));
begin
If (l_select_key = 'SHIFT+'
or g_selection_scope = 'RANGE_SELECT'
and get_range_select_start > 0
Then
SelectRange;
Else
-- If l_select_key = 'CTRL+'
If l_select_key = 'CONTROL+'
or g_selection_scope = 'INCREMENTAL_SELECT'
Then
ToggleCurrent;
Else --no interpretable modifier key
If IsSelected
then
unselect_all(name_in('system.cursor_block'));
else
unselect_all(name_in('system.cursor_block'));
SelectCurrent;
end if;
End if;
End if;
exception
when form_trigger_failure then raise;
when others then qms$errors.unhandled_exception('qms$msel.change_selection');
end change_selection;
null

You mentioned 'the problem with multiselect functionality' but what exactly was the problem? I tried finding the bug 756682 (mentioned in the code) on Metalink but couldn't find it.
Regards,
Edward

All FRM messages are suppressed after buissness rules validation

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

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

FRM-41045 when returning to calling form

I'm using Designer 1.3.2 with Headstart 3.4.3 and Forms 4.5.
The situation is as follows:
I'm using the call_form functionality to call another form when using a form. This goes well. When I leave the called form to return into the calling form I get the error message 'FRM-41045 Cannot find item: Invalid ID'. The functionality of the form stays in tact, so my question is how can I solve this error or how can I suppress this message?

Linda,
My suggestion would be to try to drill down on the cause of the problem in form builder. What causes the FRM message?
If you cannot track down to the cause and want to suppress this message, you could try to capture the event in the on-error trigger and continue without an error when this error occurs (maybe encapsuled by a helping global variable construction so that the message is not always suppressed)
In designer/forms 6.0 or 6i you could suppress the message in two ways:
1. By adding it to the suppress message stack (see hsdapp65.pll for an example).
2. Add the message to the qms_message_properties table and set the suppr_always_ind to Y.
The headstart 3.4 qms_messages table does not yet contain this column, but you might take a look at the headstart 2.1.2 procedure qms$forms_errors.add_suppress_message(<message number>); to code your own solution for it in headstart 3.4.
Regards, Marc

Manipulating message queues

Hi,
I found the following command/line to manipulate message queue settings to display messages either in status bar or as alerts. But I am not sure how n where to use this.
"qms$forms_errors.set_oracle_message_target"
Can any one share more details about this?
Any help would be greatly appreciated.
Thanks,

Hi Herbert,
Can we achieve the same (displaying all messages either in status bar or as alerts) in Forms 10g without using Headstart packages/libraries?
Please do not suggest to modify ON-ERROR or ON-MESSAGE triggers to do that. Is there any single statement/procedure to do that at application level.
~Gouri Sankar

Images in webforms from jar file

In a headstart generated forms (designer 6 headstart 5.0.3) i have a lot of image items
(unbound items with the hint <IM>my_image.gif</IM>
It's a WebForms application.
I use jar archive file for images. But i see no any image in runtime.
The problem is: in qms$block.init_image_item (qmslib50.pll) is call to read_image_file whit 3 parameters
image_name => 'my_image.gif'
image_type => 'GIF' = substr(l_image_file,instr(l_image_file,'.')+1);
item_name => 'block.my_image_item'
It works on the web too but only if images are in the file system.
If images are in the jar file it don't works.
image_type for the web have to be 'URL' and
image_name my_image (without gif)
What i have to do?
How can i generate form with image_name (without extension) and image_type='URL'?
If it's impossible may be do you have a version of qms$block.init_image_item (for web :-) )
or do i have to change this procedure myself?
Kind regards,
Roman Farber
null

procedure init_image_item
is
-- purpose: If the hint text contains the name of an image file,
-- enclosed between <IM> and </IM> tags, the image file is
-- is applied to the next item (which is the image item).
-- Procedure is customized for web.
-- Procedure will first looking for an image in archive jar file.
-- If image is not found in jar file we are going to looking for
-- an image in the file syatem.
l_image_file varchar2(50);
l_image_item varchar2(100);
l_image_type varchar2(10);
l_path varchar2(300);
l_path_specified boolean := false;
-- Only for web
l_image_name varchar2(50);
begin
l_image_file := qms$item.get_tagged_hint_info(l_cur_item,'<IM>','</IM>');
if l_image_file is null
then
return;
end if;
-- image file may be stored in forms parameter or global.
-- In both cases the image file should start with a colon
if instr(l_image_file,':') = 1
then
l_image_file := name_in(substr(l_image_file,2));
end if;
l_image_item := l_cur_block| |'.'| |get_item_property(l_cur_item_id,nextitem);
-- check if the next item is really an image item
if get_item_property(l_image_item,item_type) <> 'IMAGE'
then
return;
end if;
-----====================================================
-- For Web Forms, Looking for the image in jar archive file
-- if file is not found (or it's not the application archive jar file )
-- then go to the file system.
SYNCHRONIZE;
-- Name of image without extension.
l_image_name := substr(l_image_file,1,instr(l_image_file,'.')-1);
-- message('l_image_name = '| |l_image_name);pause;
-- Suppress error FRM-47109, cannot locate image file
-- We need to suppress this message because the image files
-- might be located in one of the FORMS50_PATH directories
qms$forms_errors.add_suppress_message('FRM-47109');
read_image_file(l_image_name,'URL',l_image_item);
SYNCHRONIZE;
if not form_success
then
-- message('form not succes');pause;
qms$errors.show_debug_info('Image '| |l_image_file| |
': not found in jar archive file now looking for in file system' );
qms$forms_errors.delete_suppress_message('FRM-47109');
else
-- message('form wel succes');pause;
qms$forms_errors.delete_suppress_message('FRM-47109');
return;
end if;
-- End of looking for the image in jar archive file
-----====================================================
-- file system
l_image_type := substr(l_image_file,instr(l_image_file,'.')+1);
Tool_env.getvar('HEADSTART\IMAGEFILE_PATH', l_path);
if l_path is not null
then
if get_application_property(operating_system) like 'MSWINDOWS%'
or get_application_property(operating_system) = 'WIN32COMMON'
then
if l_path not like ('%\')
then
l_path := l_path| |'\';
end if;
end if;
-- Suppress error FRM-47109, cannot locate image file
-- We need to suppress this message because the image files
-- might be located in one of the FORMS50_PATH directories
qms$forms_errors.add_suppress_message('FRM-47109');
read_image_file(l_path| |l_image_file,l_image_type,l_image_item);
if not form_success
then
qms$errors.show_debug_info('Image '| |l_image_file| |': not found on path '| |l_path
| |', now looking in FORM50_PATH directories' );
qms$forms_errors.delete_suppress_message('FRM-47109');
-- Try to read the image file again, without the path name
-- Forms will automatically search through all directories in the FORMS50_PATH
read_image_file(l_image_file,l_image_type,l_image_item);
qms$errors.show_debug_info('Item '| |l_image_item| |': read image '| |l_image_file);
else
qms$forms_errors.delete_suppress_message('FRM-47109');
qms$errors.show_debug_info('Item '| |l_image_item| |': read image '| |l_path| |l_image_file);
end if;
else
read_image_file(l_image_file,l_image_type,l imageitem);
qms$errors.show_debug_info('Item '| |l_image_item| |': read image '| |l_image_file);
end if;
exception
when form_trigger_failure then raise;
when others then qms$errors.unhandled_exception('qms$block.init_image_item');
end init_image_item;

Releasenotes, bugfixes and enhancements

Hello,
I'm currently using Headstart version 6.5.1(.0). Can anyone send me the releasenotes, bugfixes or enhancements of all patches since then till version 6.5.3., or can anyone give me a good reason of upgrading.
All can be send to [email protected]
Thank you very much.

Kristof,
The release notes of all patches.
Headstart Oracle Designer PATCH 6.5.3.0 FOR 9i
==============================================
This patch is ready for use with Designer 9i, Forms 9i and Reports 9i.
Also it addresses the following bugs and enhancement requests
(mostly the same that are addressed in PATCH 6.5.3.0 FOR 6i):
Bug No. Description
====== =======================================================================
2309129 - ERROR IN UNLD_RPTS.SQL SCRIPT
2309202 - NAVIGATOR FORMS DO NOT HAVE CG$STARTUP_MODE, CAUSES ERROR
2441289 - SAVE BUTTON STAYING DISABLED WHEN IT SHOULD BE ENABLED
2482013 - LOGGING INTO 9I SERVER AS SYS MUST BE DONE AS SYSDBA
2483045 - CHANGE OBJECT LIBRARY USAGE STANDARD IN HEADSTART USER GUIDE
2497339 - CALENDAR-LOV WITH TIME HAS EXTRA BUTTONS, PROBLEM WHEN NULL VALUE
2499198 - USE CALENDAR LOV, GET FRM-40102: "RECORD MUST BE ENTERED OR DELETED
FIRST"
2504387 - SET QMSOLB65.OLB DISPLAY ONLY ITEMS (CGSO$%_DO) TO ENABLED=YES
2520101 - OFGTEL65.PLL CANNOT BE COMPILED AGAINST HST65 TEMPLATE PACKAGE OWNER
2520119 - GENERATION OF HEADSTART DEMO FORM HSD0034F GIVES CDG-01117 INVALID
DISPLAY TYPE
2520191 - MESSAGE QMS-00125 DOES NOT EXIST IN QMS_MESSAGE_PROPERTIES, USED IN
QMSLIB65
2521218 - HEADSTART 6I DOES NOT COMPILE WITH FORMS 9I
2529003 - CAPI SHOULD NOT INCLUDE COLUMNS WITH COMPLETE = NO
2570562 - 'SAVE OLD DATA' NOT GENERATED WHEN CAPI UTILITY PARAM
'TAPI TRIGGERS' IS NO
2600939 - IF SUBTYPE ATTRIBUTE MAPPED TO MULTIPLE TABLES, UTILITY CAN TAKE THE
WRONG ONE
2605551 - STILL HAVE CODE FOR '_CASDEL' IN QMSLIB65.PLL QMS$FORMS_ERRORS
2635597 - HEADSTART 6.5 UTILITIES THAT CALL BLTEXT.DELETE_TAGGED_BLOCK FAIL
2635613 - CALL TO QMS$BLOCK.GO('<BLOCK NAME>') IN QMSLIB65 IS CASE SENSITIVE!!
2635789 - CAPI VALIDATED BUSINESS RULE AGAINST WRONG ROW FROM INTERNAL ROW
STACK
2651107 - CHANGE_CONNECTION DOES NOT UPDATE ENTIRE INFO ABOUT APPLICATION
Headstart Oracle Designer PATCH 6.5.3.0 FOR 6i
==============================================
This patch addresses the following bugs and enhancement requests:
Bug No. Description
======= ======================================================================
2309129 - ERROR IN UNLD_RPTS.SQL SCRIPT
2309202 - NAVIGATOR FORMS DO NOT HAVE CG$STARTUP_MODE, CAUSES ERROR
2482013 - LOGGING INTO 9I SERVER AS SYS MUST BE DONE AS SYSDBA
2441289 - SAVE BUTTON STAYING DISABLED WHEN IT SHOULD BE ENABLED
2483045 - CHANGE OBJECT LIBRARY USAGE STANDARD IN HEADSTART USER GUIDE
2497339 - CALENDAR-LOV WITH TIME HAS EXTRA BUTTONS, PROBLEM WHEN NULL VALUE
2499198 - USE CALENDAR LOV, GET FRM-40102: "RECORD MUST BE ENTERED OR DELETED
FIRST"
2504387 - SET QMSOLB65.OLB DISPLAY ONLY ITEMS (CGSO$%_DO) TO ENABLED=YES
2520101 - OFGTEL65.PLL CANNOT BE COMPILED AGAINST HST65 TEMPLATE PACKAGE
OWNER
2520119 - GENERATION OF HEADSTART DEMO FORM HSD0034F GIVES CDG-01117 INVALID
DISPLAY TYPE
2520191 - MESSAGE QMS-00125 DOES NOT EXIST IN QMS_MESSAGE_PROPERTIES,
USED IN QMSLIB65
2529003 - CAPI SHOULD NOT INCLUDE COLUMNS WITH COMPLETE = NO
2570562 - 'SAVE OLD DATA' NOT GENERATED WHEN CAPI UTILITY PARAM
'TAPI TRIGGERS' IS NO
2600939 - IF SUBTYPE ATTRIBUTE MAPPED TO MULTIPLE TABLES, UTILITY CAN TAKE
THE WRONG ONE
2605551 - STILL HAVE CODE FOR '_CASDEL' IN QMSLIB65.PLL QMS$FORMS_ERRORS
2635597 - HEADSTART 6.5 UTILITIES THAT CALL BLTEXT.DELETE_TAGGED_BLOCK FAIL
2635613 - CALL TO QMS$BLOCK.GO('<BLOCK NAME>') IN QMSLIB65 IS CASE SENSITIVE!
2635789 - CAPI VALIDATED BUSINESS RULE AGAINST WRONG ROW FROM INTERNAL
ROW STACK
2651107 - CHANGE_CONNECTION DOES NOT UPDATE ENTIRE INFO ABOUT APPLICATION
Headstart Oracle Designer 6i PATCH 6.5.2.3
CDM RuleFrame Performance Improvement
==========================================
The main purpose of this patch is to improve the performance of the
CDM RuleFrame engine when large transactions are involved.
The functionality of CDM RuleFrame is only slightly changed by this patch:
- The utility 'Create CAPI Custom Service' makes it possible to include
a CAPI Custom Service (i.e. your own package or function) in more
than one CAPI (see "BUG 2419371" below)
- The utility 'Create VAPI Definition' can now also create VAPI's for
subtypes (controlled by new utility parameter)
This patch addresses the following bugs and enhancement requests:
Bug No. Description
======= ======================================================================
2070417 - PERFORMANCE ENHANCEMENT SUGGESTION FOR DISABLING CDM
RULEFRAME IN BATCH MODE
2204246 - USE NATIVE DYNAMIC SQL FOR RULEFRAME RUNTIME
SOFTWARE
2220682 - IMPROVE RULEFRAME RUNTIME PERFORMANCE WITH NOCOPY
IN TRANSACTION MANAGEMENT
2220697 - RULEFRAME STACK: USE TEMPORARY DATABASE TABLES INSTEAD
OF PL/SQL TABLES
2220707 - STORE ROWS IN RULEFRAME ROW STACK ON AN INDEX CALCULATED BY
A HASH FUNCTION
2220908 - ELIMINATE ROW STACK FROM CAPI AND MAKE OLD ROW STACK SMALLER
2227746 - ENHANCE RULEFRAME PERFORMANCE BY MINIMIZING CAPI USE OF
FIND_ON_STACK
2249250 - WHEN CREATING CAPI FOR TABLE WITH MANY COLUMNS: ORA-06502 VALUE
ERROR
2259418 - IMPROVE RULEFRAME PERFORMANCE BY ENFORCING CERTAIN RULES
IMMEDIATELY
2394119 - RUNNING UTILITIES ERR.SQL GIVES ORA-20000: ORU-10028: LINE
LENGTH OVERFLOW
2394166 - WHEN BUSINESS RULE ALREADY EXISTS, UTILITY STILL TRIES TO
INSERT TRIGGER
2396132 - UTILITY JOURNALLING BUSINESS RULES ORA-01401: INSERTED VALUE
TOO LARGE IN BLTEXT
2419371 - POSSIBILTY TO USE SAME CUSTOM SERVICE IN MORE THAN ONE CAPI
PACKAGE
2441447 - REMOVE WORKAROUND FOR BUG 1347738 IN CAPI GENERATOR (HSU_CAPF)
2481957 - DEFAULT IN SPECIFICATION OF HSU_BRTR.RUN AT WRONG PARAMETER
2485658 - CDA-01305 COLUMN UID - WHEN SAVING RESULTS OF REFRESHING JOURNAL
TABLE UTILITY
Headstart Oracle Designer 6i PATCH 6.5.2.2
==========================================
This patch addresses the following bugs and enhancement requests:
Bug No. Description
======= ======================================================================
2283093 - RUNNING REPORTS USING DESTYPE=CACHE FROM REPORT LAUNCH FORM
2283122 - ERROR WHEN CLOSING WINDOW AFTER DUPLICATE RECORD KEY
2285936 - PROBLEMS WITH REPORT LAUNCH FORM IN 6.5.2.1 SUPPLEMENT OPTION
2303927 - QMS0012 REPORT LAUNCH FORM NO DEFAULT VALUES IN PARAMETERLIST AFTER
STARTUP
Headstart Oracle Designer 6i PATCH 6.5.2.1
==========================================
This patch addresses the following bugs and enhancement requests:
Bug No. Description
======= ======================================================================
1696475 - ONLINE HELP FOR REPORTS HAS STRANGE URL
1702857 - ORA-00600 WHEN TRYING TO RUN HEADSTART FORM USING FORMS DEBUGGER
1727439 - POOR PERFORMANCE IN UTILITY 'CREATE CAPI DEFINITION'
1727886 - ERRORS IN 'CREATE CAPI DEFINITION' UTILITY ARE IGNORED
1747626 - RULEFRAME 6I BUS. RULE VIOLATION ON DELETED RECORD GIVES ORA-01403
OR QMS-00100
1754565 - PROCEDURE QMS$ABOUT_THIS_APPLICATION IS MISSING IN YOUR APPLICATION
LIBRARY...
1754740 - SETUP PART OF USER GUIDE SHOULD MENTION ACCESS TO HEADSTART DATABASE
OBJECTS
1754906 - CREATE FIND WINDOW(S) - SAVING CHANGES FAILED WITH CDA-01151
1764270 - CHAPTER 17 REFERS TO SCRIPT HSU_USER.GRT, WHICH IS NOT AVAILABLE
1769077 - SERVER SIDE INSTALLER SAYS USER ALREADY INSTALLED WHEN MANUAL IMPORT
UTILITIES
1769234 - LONG BLOCK.ITEM NAME RESULTS IN QMS-00100: ORA-06502:
PL/SQL: NUMERIC/VALUE ERR.
1769321 - VALUE ERROR IN HTML ONLINE HELP GENERATOR WHEN ITEMS HAVE LONG HINT
TEXTS
1781424 - CDM RULEFRAME: TRIGGER ALREADY EXISTS ERROR EVEN IF TRIGGER IS IN
OTHER FOLDER
1781454 - CREATE DOMAINS FOR DISCRIMINATOR COLUMNS TRIES TO UPDATE DOMAIN IN
WRONG FOLDER
1802399 - WHEN VIEWING LOG: UNHANDLED EXCEPTION IN VIEW_LOG_MESSAGES:ORA-06502
1832171 - DROP THE PK ON QMS_TRANSACTIONS FOR PERFORMANCE REASONS
1869480 - REPORTS MODULES NOT SHOWN IN MULTI SELECT LIST OF UTIL SET
IMPLEMENTATION NAME
1877521 - ORA-06502 WHEN MAINTAIN BUSINESS RULE DESIGN DEFINITIONS FOR STATIC
DOMAINS
1885204 - BUSINESS RULE TRANSFORMER: TRIGGERING EVENT <X> IS INVALID.
IT HAS NO ENTITY...
1890011 - UNABLE TO GENERATE DEFAULT NULL PARAMETER IN CAPI CUSTOM SERVICE
1890029 - HSD 65 USER GUIDE MENTIONS STFFMB PREF.INST. OF PREF.
SET QMS65_LOV_MODULE
1890035 - SMALL OMISSIONS AND TYPOS IN HEADSTART 65 USER GUIDE
1891637 - REDIRECT HEADSTART REFERENCED OBJECTS: INVALID VALUE FOR OLD QMS
APP VERSION
1978916 - WITH OLD DB TRIGGER, SEE 'ORA-20998'IN FORM INSTEAD IF THE ACTUAL
MESSAGES
1979278 - F9 DOES NOT WORK FOR LIST OF VALUES ON MODAL DIALOG FORM
(ALSO UP/DOWN)
1985903 - APPLICATION CLOSES WHEN USING MULTI-SELECT FEATURES IN MODAL DIALOG
WINDOW
1987743 - ORA-06508: PL/SQL: COULD NOT FIND PROGRAM UNIT.. <TAPI PACKAGE>.INS
2093405 - WHEN INSTALLING HEADSTART IN A 9I DATABASE, CG$ERRORS WON'T COMPILE
ANYMORE
2101690 - ONLINE HELP FOR REPORTS (QMS0012F) DOESN'T WORK
2148764 - CG$ERRORS WON'T COMPILE ON 9I DATABASE
2148774 - ENABLED PROPERTY SET YES ON CGSO$..._DO OBJECTS IN OBJECT LIBRARY
2176331 - ERROR WITH ORDER BY CURRENT FIELD
2176348 - GET ERROR IF LAST REPORT PARAMETER IS TYPE DATE
2176364 - CREATE VIEW DEFINITION DOESN'T UPDATE WHERE CLAUSE OF DOMAIN KEY
CONSTRAINT
2185321 - COMPILATION ERRORS ORACLE 9I: DIFFERENCES PARAMETER DEFAULTS PACKAGE
SPEC/BODY
Regards,
Marcel

Frm-47023 no such parameter named cg$startup_mode exists in form.

This messages occurs when the form is run.
We've renamed our OFG library's to lowercase, for UNIX.
Then this message occured when generating a new form.
SO we copied the uppercase OFG libaries backin. Compiled then all and also the app65.pll, the qmsevh65.pll and the qmslib65.pll. The error will not disappear for new forms.
If we regenerate an existing form this message does not show.
Can anybody help us with this?

I got this error once when I generated a ReadOnly form. This was a result of the fact that the CG$STARTUP_MODE parameter is not generated: this is a Designer bug.
A workaround for this bug is supressing the 47023 error message with qms$forms_errors.add_suppress_message.
regards,
Harm van Zoest

Commit delay when using alerts

I know that using Headstart it is possible to have the standard FRM messages displaying either in an alert box or in the status bar at the bottom of the screen. I have been involved with two applications that are 100% generated using Headstart and we have chosen to display the messages in an alert box. I have recently discovered that in certain circumstances there is a potentially serious problem with this.
If the user commits a record, an alert box is displayed with the message FRM-40400: Transaction complete. x records applied and
saved. I had always believed that at this stage, the records were safely written to the database but this is not the case. If the user leaves the alert box displayed on screen the records have not been saved. If the database goes down at this point the changes are rolled back and not saved to the database.
I still want to display the majority of the FRM messages in alert boxes. What I want to know is, can I display FRM-40400 in the status bar but every other FRM message in an alert box?

This is news to me too!!!
You can make a small customization to your qmslib50 library to always put FRM-40400 on the message line.
In package qms$forms_errors, procedure ErrorMessageAlert:
/* customization */
if p_errorrec.msg_code = 'FRM-40400'
then
p_errorrec.severity := 'M';
end if;
/* end customization */
Put this code just before the lines...
/* Show message */
IF p_errorrec.severity <> 'M'
THEN
Regards,
Lauri

Errors in QMS$FORMS_ERRORS (headstart 5.0.3)

Similar Messages

Maybe you are looking for