FRM-40007 TO FRM-40041
FRM-40007: Invalid user identifier or password. Re-enter.
Cause: You entered
an incorrect ORACLE username or password.
Action: Retype your
username and password properly.
Level: 99
Trigger: ON-ERROR
FRM-40010: Cannot read form %s.
Cause: One of the
following:
1. You entered a nonexistent form
name.
2. You typed an incomplete path.
3. You do not have the proper
privileges to run the form.
4. You do not have a compiled copy of
the form.
Action: Retype the
form name correctly, provide the proper path name, contact your system
administrator, or compile the form.
Level: 5
Trigger: ON-ERROR
FRM-40011: Form was created by an old version of Oracle Forms.
Cause: The .FMB file
was created with an old and incompatible version of the Form Compiler.
Action: Recompile the
form or relink Generate.
Level: 99
Trigger: ON-ERROR
FRM-40012: Form was created by a new version of Oracle Forms.
Cause: The .FMB file
was created by a new and incompatible version of the Form Compiler.
Action: Recompile the
form.
Level: 99
Trigger: ON-ERROR
FRM-40013: Program Error: error occurred while reading form.
Cause: An internal
error occurred while Oracle Forms was trying to read the .FMB file.
Action: Recompile the
form.
Level: 99
Trigger: None
FRM-40014: Not enough memory to load the form.
Cause: Internal
error. Your computer does not have enough memory to run the form.
Action: The designer
might be able to modify the form so that it will run. If that is not feasible,
your installation must make more memory available, either by modifying the
operating system parameters or by adding more memory to the computer.
Level: 99
Trigger: ON-ERROR
FRM-40015: Unexpected end of file reading form.
Cause: The form was
fragmented or incomplete.
Action: Recompile the
form.
Level: 99
Trigger: None
FRM-40019: Unknown screen number to display.
Cause: An internal
error occurred.
Action: If the problem
persists, contact Oracle Support Services.
Level: 99
Trigger: None
FRM-40020: Page %d too small for this form.
Cause: Application
design error. An item is positioned off the page.
Action: Ensure that
all items that are associated with the given page fit completely on that page.
You can reposition the items or resize the page.
Level: 99
Trigger: None
FRM-40021: Item in form file is too large.
Cause: An internal
error occurred while Oracle Forms was reading the form.
Action: If the
problem persists, contact Oracle Support Services.
Level: 99
Trigger: None
FRM-40023: Error creating record manager context.
Cause: Oracle Forms
could not initialize its internal record manager.
Action: If the
problem persists, contact Oracle Support Services.
Level: 99
Trigger: ON-ERROR
FRM-40024: Out of memory.
Cause: Internal
error. Your computer does not have enough memory to run the form.
Action: The designer
might be able to modify the form so that it will run. If that is not feasible,
your installation must make more memory available, either by modifying the
operating system parameters or by adding more memory to the computer.
Level: 99
Trigger: ON-ERROR
FRM-40025: Cannot suppress screen output without file input.
Cause: You tried to
run a form on the command line using incompatible preferences. The output_file
preference works only in conjunction with the keyin preference.
Action: Retype the
command to include both the output_file and keyin preferences.
Level: 99
Trigger: None
FRM-40026: Error opening key script file.
Cause: Oracle Forms
cannot open the file you specified with the keyin preference.
Action: Make sure the
file exists and the file protections are set properly. Or create a file with
the keyin preference.
Level: 99
Trigger: None
FRM-40027: Error opening display spool file.
Cause: Operating
system error. Oracle Forms cannot open a file specified with the output_file
preference because there is insufficient disk space or because you have
specified an incorrect filename.
Action: Contact your
system administrator.
Level: 99
Trigger: None
FRM-40028: Error opening message file %s%s%s.MSB.
Cause: Oracle Forms
cannot find the message file.
Action: Make sure the
message file exists and the appropriate path is set.
Level: 99
Trigger: None
FRM-40029: Already logged on. Must logout before changing
connections.
Cause: The Login()
Built-in was issued while already logged on.
Action: Use the
Logout() Built-in first.
Level: 25
Trigger: ON-ERROR
FRM-40030: File %s is not a Forms file.
Cause: The file
specified on the command line was not a valid Oracle Forms file.
Action: Re-enter
Forms Runtime startup command with the name of a valid file.
Level: 99
Trigger: ON-ERROR
FRM-40031: File %s is not a Forms Runtime file.
Cause: The file
specified on the command line is not a Forms Runtime (.FMX) file.
Action: Re-enter a
valid Forms Runtime (.FMX) file.
Level: 99
Trigger: ON-ERROR
FRM-40032: Internal Error: file %s contains an improper chunk
size.
Cause: Internal
error. File was compiled incorrectly or is corrupted.
Action: Recompile
your file.
Level: 99
Trigger: ON-ERROR
FRM-40033: Internal Error: file %s contains a bad chunk table.
Cause: Internal
error. File was compiled incorrectly or is corrupted.
Action: Recompile
your file.
Level: 99
Trigger: ON-ERROR
FRM-40034: Cannot attach the library file.
Cause: Oracle Forms
was unable to find the specified library file.
Action: Exit Forms
Runtime and try again.
Level: 99
Trigger: ON-ERROR
FRM-40036: Library was created by a new version of Oracle Forms.
Cause: Oracle Forms
unable to use library.
Action: Recompile the
library with current version of Oracle Forms.
Level: 99
Trigger: ON-ERROR
FRM-40037: Library was created by an old version of Oracle
Forms.
Cause: Oracle Forms
unable to use library.
Action: Recompile the
library with current version of Oracle Forms.
Level: 99
Trigger: ON-ERROR
FRM-40039: Cannot attach library %s while opening form %s.
Cause: The given
library is attached to the form but cannot be located in the search path for
PL/SQL libraries.
Action: Make sure
that the given library can be found and that it has read permissions set.
Level: 99
Trigger: ON-ERROR
FRM-40040: Cannot perform proxy connection.
Cause: Database
privileges for proxying user may not be configured on the database side or
database account for SSO user not created.
Action: Make sure
database is appropriately configured for making proxy connection.
Level: 99
Trigger: ON-ERROR
FRM-40041: Form %s requires a UTF8 character set.
Cause: An attempt
was made to execute the specified form, but it contained one or more items
whose datatype was NCHAR, and the NLS_LANG environment variable did not specify
the UTF8 or AL32UTF8 character set.
Action: Set the
NLS_LANG environment variable to a value which specifies the UTF8 or AL32UTF8
character set, and restart the application.
Level: 25
Trigger: ON-ERROR
1 comment:
FRM-40041: Form %s requires a UTF8 character set.
need detail solution about above FRM code
Post a Comment