Professional Documents
Culture Documents
Oracle Forms is part of Oracle's Internet Developer Suite (iDS). Previous versions of it
was called SQL*Forms.
PS: You also need to regenerate the FMB files after upgrading to a new Forms version.
FORMS API Master -- This will help us to compare two Fmbs. in Tools Developer
Compare option will be there you can compare two fmbs.
OriPos := TO_NUMBER(:System.Trigger_Record);
First_Record;
LOOP
-- do processing
IF (:System.Last_Record = 'TRUE') THEN
Go_Record(OriPos);
EXIT;
ELSE
Next_Record;
END IF;
END LOOP
-- ON-LOGON Trigger
declare
uname varchar2(10);
pass varchar2(10);
begin
uname := 'username';
pass := 'password';
logon(uname, pass || '@connect_database');
end;
[my_cfg]
userid=username/password@connect_database
form=MY_FORM.fmx
http://<<ip_address:port>>/forms/frmservlet?config=my_cfg
NEW_FORM: terminate the current form and replace it with the indicated new form.
The old form's resources (like cursors and locks) will be released. parent form will be
closed.
OPEN_FORM: Opens the indicated new form without suspending or replacing the
parent form.user can navigate between parent and child forms.
MESSAGE_LEVEL:
Set to 0, 5, 10, 15, 20, 25 to suppress all messages with severity below this level. The
default level is 0. Messages with a level higher than 25 cannot be suppressed. See the
"Forms Error Messages Manual" for more details about the various
MESSAGE_LEVEL's:
• 0 - Default value. All types of messages from the other levels of severity.
• 5 - Reaffirms an obvious condition.
• 10 - Indicates that the operator has made a procedural mistake.
• 15 - Declares that the operator is attempting to perform a function for which the
form is not designed.
• 20 - Indicates a condition where the operator cannot continue an intended action
due to a problem with a trigger or another outstanding condition.
• 25 - Indicates a condition that could result in the form performing incorrectly.
• >25 - Indicates a message severity level that you cannot suppress via the
SYSTEM.MESSAGE_LEVEL system variable.
Examples:
:SYSTEM.MESSAGE_LEVEL := '25';
COMMIT;
:SYSTEM.MESSAGE_LEVEL := '0';
/* For suppressing FRM-40100: At first record. */
:SYSTEM.MESSAGE_LEVEL := '5';
FIRST_RECORD;
:SYSTEM.MESSAGE_LEVEL := '0';
/* For suppressing FRM-40350: Query caused no records to be retrieved.
*/
:SYSTEM.MESSAGE_LEVEL := '5';
EXECUTE_QUERY;
:SYSTEM.MESSAGE_LEVEL := '0';
However, you can use the FORMS_DDL built-in to execute DDL statements. Eg:
FORMS_DDL can also be used to create dynamic SQL statements at runtime. The
FORMS_SUCCESS built-in can be used to determine if the last executed built-in was
successful.
Just note that FORMS_DDL will force an implicit COMMIT and may de-synchronize the
Oracle Forms COMMIT mechanism.
1. Create a TIMER at the point where you want the navigation to occur. Eg.
create_timer('TIMER_X', 5, NO_REPEAT);
2. Code a WHEN-TIMER-EXPIRED trigger to handle the navigation
DECLARE
tm_name VARCHAR2(20);
BEGIN
tm_name := Get_Application_Property(TIMER_NAME);
IF tm_name = 'TIMER_X' THEN
Go_Item('ITEM_X');
END IF;
END;
SET_APPLICATION_PROPERTY(CURSOR_STYLE, BUSY);
message('...'); synchronize;
This can also be used to execute a query while the user is looking at the results of a
previous query.
• Enabled: True
• Navigable: False
• Mouse Navigate: False
Now set the "Canvas Type" in the canvas property palette to "Horizontal Toolbar" and
the "Form Horizontal Toolbar Canvas" in the module property palette to your canvas
name (C_TOOLBAR in our case).
Note: Designer/2000 includes a Help Generator that can generate source files for the
Help Compiler.
DECLARE
file1 TEXT_IO.FILE_TYPE;
file2 TEXT_IO.FILE_TYPE;
str VARCHAR2(80);
BEGIN
file1 := TEXT_IO.FOPEN( 'input.txt','r' );
file2 := TEXT_IO.FOPEN( 'output.txt', 'w' );
TEXT_IO.GET_LINE( file1, str );
TEXT_IO.PUT_LINE( file2, str );
TEXT_IO.FCLOSE( file1 );
TEXT_IO.FCLOSE( file2 );
END;
@echo.
@echo Done!!! Remember to move the FMX files into your runtime
directory.
@echo.
:END
If you want to generate a Library file, replace FORM with LIBRARY. Use f45genm to
generate your form in a Motif environment.
Use the "f45run" command to run your form. Forms 6i uses commands f60gen, f60run,
etc.