/ Copyright (c) Oracle Corporation 1989, 2004. All Rights Reserved.
/
/ File		:
/ Created	: 09/01/04
/ By		:
/ Language	: American
/ Character set : US7ASCII
/
/ CONTENTS:
/    Generic Base Messages for :
/  Default DESC: 6.1.0
/
/
/ NOTES:
/
/ MODIFIED:
/ JEWILLIA	  02/09/04 - Message 7017 Updated
/ AMITKUM	  11/25/03 - Message 1364 Updated
/ AMITKUM	  11/24/03 - Message 1495 Deleted
/ AMITKUM	  11/24/03 - Message 1495 Updated
/ AMITKUM	  11/24/03 - Message 1495 Added
/
/ 00001 .. 00199 Generator General Error and Warning Messages
/
00001,1, "Item's Display Type property not set"
// *Cause :  You have not set the item's Display Type property.
//	     Therefore, Form Generator will generate the item
//	     as a text item.
// *Action : If you do not want the item generated as a text item,
//	     set the item's Display
//	     Type to a valid value. To find out which values are
//	     valid for Form Generator,
//	     refer to the help system.
00002,4, "Cannot allocate %u bytes of memory"
// *Cause :  memory has been exhausted. Form Generator is unable to allocate
//	     any more memory.
// *Action : Check the memory available and the memory consumption of other
//	     programs that may be running.
//	     If the problem persists contact your Customer Support
//	     representative.
00003,1, "Cannot find user named editor %s in form or object library"
// *Cause :  Form Generator cannot find the user-named editor specified
//	     for this object in the object library.
// *Action : Make sure the name of the editor specified for the
//	     source object is spelt correctly, and that
//	     the object library contains an editor with this name.
00004,1, "Inclusion Object '%s' is not valid at Form level"
// *Cause :  The object (listed in the module's "Template/
//	     Library Objects" list) is not of a type suitable for
//	     attaching to the Form at Form level.
//	     Not all Forms types can be attached at Form
//	     level, e.g. Items can be attached to Blocks
//	     but not to Forms, Block can be attached to
//	     Forms.
// *Action : Check that the type of the named object is
//	     suitable for attaching to a Form (see the
//	     documentation for a list of valid objects
//	     types)
00005,1, "Ignoring Forms Version 2 style trigger '%s.%s'"
// *Cause :  A Version 2 style trigger is contained in one of the following:
//	     --- a template or object library used during generation
//	     --- a form being captured
//	     Form Generator does not support Version 2 style triggers, and
//	     therefore ignores the trigger.
// *Action : No action required.
//	     If you want to include the code associated
//	     with the Version 2 style trigger, use Form Builder to
//	     convert the trigger to a PL/SQL trigger.
00006,1, "Generatable code group overridden by empty object library code group"
// *Cause :  To override all occurrences of a generatable code group,
//	     an object library object group called
//	     CGOC$CODE_OVERRIDE_SOURCE must contain a code group
//	     with the same name as the generatable code group.
//	     Form Generator has located a suitable code group in the object
//	     library object group. However, the code group is empty.
// *Action : No action required.
00007,1, "No triggers in object group overriding generatable application logic"
// *Cause :  To override all occurrences of generatable code groups,
//	     the object library must contain an object group called
//	     CGOC$CODE_OVERRIDE_SOURCE.
//	     Form Generator has located this object group in the
//	     object library. However, the object group does not contain
//	     any triggers for use as a source of alternative application
//	     logic.
// *Action : No action required.
00008,3, "Unable to find SDD_ELEMENT; EL_ID = %s"
// *Cause :  Form Generator cannot find the Repository element
//	     indicated. The most likely cause is that another user has
//	     deleted the element during this Form Generator session.
// *Action : Rerun the Form Generator. If the problem persists then
//	     the Repository may be corrupted; contact your Customer
//	     support representative.
00009,2, "Valid values are %s or %s to quit"
// *Cause :  You have supplied an invalid response to a question requiring a
//	     "Yes" or "No" response.
// *Action : Enter one of the options in the list given.
00010,4, "cgfree: memory unallocated or previously freed"
// *Cause :  This is an internal error message and should not normally be
//	     issued.
// *Action : Contact your Customer Support representative.
00011,4, "%d bytes allocated and not freed"
// *Cause :  This is an internal error message and should not normally be
//	     issued.
// *Action : Contact your Customer Support representative.
00012,4, "Location %s - invalid argument"
// *Cause :  This is an internal error message and should not normally be
//	     issued.
// *Action : Contact your Customer Support representative.
00013,2, "Valid values are integers in the range %d to %d or %s to quit"
// *Cause :  You have entered a number which is not an integer or which is
//	     outside the range of allowable values.
// *Action : Enter an integer in the range indicated.
00014,2, "Valid values are integers greater than %d or %s to quit"
// *Cause :  You have entered a number which is not an integer or which is
//	     less than the minimum allowed.
// *Action : Enter an integer which is greater than or equal to the
//	     minimum indicated.
00015,2, "Valid values are integers less than %d or %s to quit"
// *Cause :  You have entered a number which is not an integer or which is
//	     greater than the maximum allowed.
// *Action : Enter an integer which is less than or equal to the maximum
//	     indicated.
00016,3, "Unable to open file %s"
// *Cause :  The file shown does not exist, or is not readable.
// *Action : Make sure the file exists and is readable. If the file does not
//	     exist this may be due to lack of write permission in the current
//	     directory.
00017,2, "Comment of object library code group %s does not match its application"
// *Cause :  The specified object library code group overrides all occurrences
//	     of a generatable code group with the same name.
//	     During generation, Form Generator has detected that the comment
//	     inside the object library code group does
//	     not match the name (and use) of the code group itself.
//	     This could cause unexpected behaviour if you capture the
//	     generated form.
// *Action : Change the comment for the object library code group as follows:
//	     --- if you do not want the alternative code captured into
//	     the repository during design capture, either do not include
//	     a comment (recommended) or include the name of the
//	     overridden code group as a comment
//	     --- if you want the alternative code captured into the
//	     repository as user-modified generated application logic,
//	     include as a comment the name of the overridden code
//	     group and add a unique suffix to the code group name
00018,4, "Invalid parameter to %s (%d)"
// *Cause :  This is an internal error message not normally issued.
// *Action : Contact your Customer Support representative.
00019,4, "Code group id %d not found. Function = %s"
// *Cause :  This is an internal error message not normally issued.
// *Action : Contact your Customer Support representative.
00020,4, "%s has failed, please send the following information to your support person"
// *Cause :  An unexpected internal failure has occurred.
// *Action : Please send the trace back information which was output after this
//	     message to your support representative.
00021,1, "Program unit '%s' exists both in form and library. Using version in form."
// *Cause :  Form Generator has detected that the captured form has
//	     been generated from a repository module with the PGULIB
//	     preference set to Yes, and therefore that program units have
//	     been generated to an attached library. Form Generator has
//	     attempted to capture program units added to both the form
//	     and the attached library. However a duplicate program
//	     unit has been found in the form that also exists in the
//	     attached library. For this reason, the program unit in the form
//	     has been captured and the program unit in the library
//	     has been discarded.
// *Action : No action necessary.
00022,1, "Floating scrollbar position adjusted for subcomponents with different sizes"
// *Cause :  The calculated scrollbar positions for two or more
//	     subcomponents sharing a floating scrollbar are
//	     different, so the forms generator has selected
//	     a position suitable for both subcomponents.
// *Action : Accept the scrollbar position selected by the
//	     forms generator, or adjust the layout of one
//	     or more subcomponents to modify each
//	     scrollbar position
00023,0, "Unable to initialize source control api for the following reason\n %s"
// *Cause :  The Source control has not been initialized.
// *Action : Refer to Source control system documentation regarding
//	     the error message issued.
00024,2, "Source control action failed for the following reason\n %s"
// *Cause :  The Source control action has failed.
// *Action : Refer to Source control system documentation regarding
//	     the error message issued.
00025,2, "Creation of forms text file failed.\n"
// *Cause :  Creation of the forms text file has failed prior to it
//	     being put in source control.
// *Action : Check that you have sufficient privileges and space to create
//	     files in the working directory.  Also check to see if the
//	     generated binary file can be loaded into Form Builder
//	     without error.
00026,2, "Creation of binary file failed\n."
// *Cause :  Creation of the forms binary file has failed after
//	     the file has been taken out of source control.
// *Action : Check that you have sufficient privileges and space to create
//	     files in the working directory.  Also make sure that the
//	     archive file is stored in text format.
00027,6, "Checking in file %s.\n"
// *Cause :  File is being checked into source control.
// *Action : None.
00028,6, "Checking out the file %s to %s.\n"
// *Cause :  File is being checked out of source control.
// *Action : None.
00029,2, "An error occurred whilst writing the log file:-\n%s"
// *Cause :  The Generator was unable to write the log file.
// *Action : Check that the path and filename you entered are valid.
00030,2, "Failed to create executable library file '%s'"
// *Cause :  The attempt to create the executable library file failed.
// *Action : Make sure you have appropriate access rights to write
//	     the file.
//	     Check your Form Builder installation is working correctly.
//	     If the problem still persists then contact your support
//	     representative.
00031,1, "Unable to create log file"
// *Cause :  The environment variable DES2_CGENF45_TRACE_FILE is not set in the
//	     oracle.ini file or is set in the wrong group.
//	     It is also possible that the filename specified by the variable is
//	     invalid.
// *Action : Make sure these lines appear in the oracle.ini file, in the
//	     [DESIGNER] group.
//	       DES2_CGENF45_TRACE_FILE=<filename>
//	       DES2_CGENF45_TRACE_LEVEL=<trace level>
//	     where <filename> is the file to write diagnostics output to
//	     and <trace level> is a number between 0 and 5 for the level of
//	     diagnostic output.
//	     Also check the filename specified by the environment variable is
//	     valid
00032,4, "FORMS90_PATH too long or invalid Form Builder installation"
// *Cause :  To read and write Oracle Forms
//	     binary files, Form Generator accesses the Form
//	     Builder component of Oracle Forms. However, Form
//	     Generator was unable to locate the Form Builder
//	     component.
//	     One possible cause might be that Form Builder
//	     has not been installed.
//	     Another possible cause might be the length of
//	     the FORMS90_PATH Registry variable.
// *Action : Try reducing the length of the FORMS90_PATH
//	     Registry variable. Alternatively, reinstall the
//	     Form Builder component of Oracle Forms.
00033,0, "Unable to read configuration file %s for the following reason: %s"
// *Cause :  The generator was unable to read the configuration file
//	     specified.
// *Action : Refer to Source control system documentation regarding
//	     the error message issued.
00034,2, "Duplicate program unit name %s"
// *Cause :  A generated module cannot contain more than one
//	     program unit with the same name.
//	     However, Form Generator has detected
//	     that the generated module will contain multiple program
//	     units with the same name and has therefore halted
//	     generation.
//	     One possible cause might be because you have
//	     defined a program unit as a named routine in the
//	     repository and also included a
//	     program unit with the same name in the template.
// *Action : Change one of the routine names so that they are no longer the same.
00035,2, "Invalid name (%s) for user named routine"
// *Cause :  The name you have specified for a named routine is invalid
//	     for one or both the following reasons:
//	     --- the specified name is greater than 30 characters
//	     --- the specified name conflicts with names reserved for generated
//	     routines (i.e. the name starts with the characters CG, followed by
//	     two characters, followed by a $ sign)
// *Action : Change the name of the named routine either
//	     by reducing the length of the name or by changing the first five
//	     characters.
00036,1, "User modified logic ignored, generatable code not generated"
// *Cause :  The user has modified a generatable piece of event code which
//	     would not have been generated this run.  The user modified code
//	     has been ignored.
// *Action : Select help on the generatable event segment in the Design Editor
//	     to tell you how this piece of logic is generated.
00037,1, "The scrollable window %s does not allow vertical scrollbars"
// *Cause :  The window is defined as scrollable,
//	     (either by the window's Repository definition,
//	     or by the preference WINSCR),
//	     and the property 'Show Vertical Scrollbar' in the
//	     object library is set to 'No'.
//	     Consequently, parts of a canvas may be inaccessible.
// *Action : Set the 'Show Vertical Scrollbar' property to 'Yes' in the
//	      object library for the window, or set the window to be
//	      non-scrollable (either in the Repository or using the
//	      preference WINSCR).
00038,1, "The scrollable window %s does not allow horizontal scrollbars"
// *Cause :  The window is defined as scrollable,
//	     (either by the window's Repository definition,
//	     or by the preference WINSCR),
//	     and the property 'Show Horizontal Scrollbar' in the
//	     object library is set to 'No'.
//	     Consequently, parts of a canvas may be inaccessible.
// *Action : Set the 'Show Horizontal Scrollbar' property to 'Yes' in the
//	      object library for the window, or set the window to be
//	      non-scrollable (either in the Repository or using the
//	      preference WINSCR).
00039,1, "Unsupported item display datatype '%s'"
// *Cause :  The item display datatype that is specified is not supported
//	     by the Form Generator.
//	     A text item will be generated instead.
// *Action : Set the display datatype for the item to one recognized by
//	     the Form Generator.
00040,2, "Many-to-one relationships are not supported by this Generator"
// *Cause :  Two module components in the module are related by a
//	     many-to-one relationship. This is an inverted master detail
//	     relationship.
//	     This Generator does not support inverted master detail
//	     relationships.
// *Action : Re-structure the module to exclude
//	     many-to-one inverted master detail relationships.
00041,2, "%s has no module components and/or table usages"
// *Cause :  The Repository definition of the module
//	     contains no module components.
// *Action : Add at least one module component to the module
//	     in the Design Editor/RON.
00042,2, "Same table relationships are not supported by this Generator"
// *Cause :  Two module components in this module are related by
//	     a link between two usages of the same table, based
//	     on a primary key constraint. This is a
//	     same table relationship.
//	     This Generator does not support same table
//	     relationships.
// *Action : Re-structure the module to exclude
//	     same table relationships.
00043,2, "Constraint %s must have the column references defined"
// *Cause :  The correct column references for this table constraint
//	     have not been defined properly. For example, a foreign
//	     key must have both the 'column' and 'join column' properties
//	     set to valid table columns.
// *Action : Ensure that the table's constraint definitions have the
//	     table reference properties set to valid tables and
//	     the appropriate column properties set to valid table columns.
00044,2, "Shared Data Links are not supported by this generator"
// *Cause :  The Repository definition of a module includes a
//	     module component with a shared data link
//	     defined.
// *Action : Remove the Shared Data Link from the
//	     Module Component.
00045,1, "Unrecognized comment tag for event segment in '%s' template trigger"
// *Cause :  Form Generator is looking for one of the following
//	     comment tags:
//	     --- /*CGAP$TES_SEQUENCE_BEFORE*/
//	     --- /*CGAP$TES_SEQUENCE_AFTER*/
//	     [lastlistitem]
//	     These tags indicate where to place template code
//	     groups in relation to other code for the same trigger
//	     in the generated form.
//	     Form Generator has found a tag beginning with CGAP$TES.
//	     However, the characters that follow do not match either of the
//	     recognized tags.
// *Action : Change the spelling of the comment tag above the event segment
//	     in the template trigger code to one of the following:
//	     --- /*CGAP$TES_SEQUENCE_BEFORE*/
//	     --- /*CGAP$TES_SEQUENCE_AFTER*/
00046,1, "'%s' Action Item set to non-displayed because width is not greater than zero"
// *Cause :  The action item width in the Repository is set to zero/unset
//	     or the AIBBWD preference is set to none and the
//	     action item has not prompt.
// *Action : Set the action item width to greater than zero
//	     in the Repository or change the value of the
//	     preference AIBBWD.
00047,1, "'%s' Action Item set to non-displayed because height isn't greater than zero"
// *Cause :  The action item height in the Repository is set to zero/unset
//	     or the sub-classed action item from the object library has a
//	     height set to zero..
// *Action : Set the action item width to greater than zero
//	     in the Repository or set the height of the sub-
//	     classed action item in the object library to
//	     a value of greater than zero.
00048,2, "Unable to capture the Form Module: '%s' to preserve layout."
// *Cause :  One of the following:
//	     --- the form (fmb) cannot be retrieved because the
//	     user specified form name and location are incorrect
//	     --- the form (fmb) is corrupt
//	     --- the form module bears no relation to the module
//	     being generated.
// *Action : Ensure that the specified form name and
//	     file location are correct and the form
//	     relates to the same module as the module
//	     currently being generated.
00049,2, "Transfer Canvas '%s' contains item(s), so it can not be removed."
// *Cause :  The source FMB file, used in the comparison
//	     process for Generation Preserving Layout,
//	     has an Overflow canvas containing items.
// *Action : Reposition the items onto a normal canvas
//	     in the source FMB file, using Form Builder.
//	     Overflow Canvases are only used as
//	     temporary storage for new items when
//	     Generating in Preserve Layout mode.
00050,2, "Failed to compile library, errors detailed in '%s'"
// *Cause :  The command to compile the .pll file into a .plx file has failed.
//	     A possible cause is a problem in the .pll file that has
//	     resulted in a compilation error.
//	     Alternatively, there might be a problem with your environment
//	     (e.g. you might have the wrong version of Form Builder
//	     installed).
// *Action : If compilation errors occurred during generation, the Generator
//	     creates a log file detailing the problem. For more information
//	     about the compilation error, view the log file from
//	     the Build Action dialog box.
00051,2, "'%s' Action Item name exceeds %d characters in length"
// *Cause :  Name of action item exceeds allowable
//	     length.
// *Action : Set the name property of the
//	     action item to a smaller length
//	     name.
00052,1, "Increase Width property because window too small to fit canvases"
// *Cause :  Form Generator has detected that:
//	     --- the window contains at least one canvas
//	     with a width greater than the window's
//	     Wdith property
//	     --- the window has the Scrollable property set to No
//	     Therefore, Form Generator has increased the window's
//	     Width property during generation.
//	     Form Generator attempts to save (or proposes) this
//	     adjustment to the property to bring the module
//	     definition into line with the generated output.
// *Action : If adjustment saved, no action necessary (Form Generator has
//	     saved the change to the property).
//	     If adjustment proposed, browse/edit the proposed change
//	     before saving/discarding it.
//	     If adjustment failed, no action necessary (Form Generator is
//	     unable to save the change to the property).
//	     Hint: If you do not want to increase the width of the window,
//	     do one of the following:
//	     --- set the window's Scrollable property to Yes
//	     --- reduce the width of the canvases to be displayed in the
//	     window
00053,1, "Increase Height property because window too small to fit canvases"
// *Cause :  Form Generator has detected that:
//	     --- the window contains at least one canvas
//	     with a height greater than the window's
//	     Height property
//	     --- the window has the Scrollable property set to No
//	     Therefore, Form Generator has increased the window's
//	     Height property during generation.
//	     Form Generator attempts to save (or proposes) this
//	     adjustment to the property to bring the module
//	     definition into line with the generated output.
// *Action : If adjustment saved, no action necessary (Form Generator has
//	     saved the change to the property).
//	     If adjustment proposed, browse/edit the proposed change
//	     before saving/discarding it.
//	     If adjustment failed, no action necessary (Form Generator is
//	     unable to save the change to the property).
//	     Hint: If you do not want to increase the height of the window,
//	     do one of the following:
//	     --- set the window's Scrollable property to Yes
//	     --- reduce the height of the canvases to be displayed in the
//	     window
00054,1, "Cannot access registry key '%s'"
// *Cause :  The application tried to access the specified registry key but an
//	     error occurred during the operation. The registry key may not exist.
// *Action : Check the key exists in the registry.
00055,1, "Using Form default Length for %s module argument length"
// *Cause :  The module argument's length property
//	     is unset in the Repository definition or has
//	     been set to zero.
// *Action : Set the module argument length
//	     property to a value greater than
//	     zero in the Repository.
00057,1, "Module Generated In Preserve Layout Mode"
// *Cause :  The Preserve Layout Option has
//	     been chosen in the Generate Form
//	     Dialog Box.
// *Action : To Generate the module normally,
//	     ensure Preserve Layout checkbox
//	     is 'unchecked' in the Generate Form
//	     Dialog Box.
00058,3, "Unable to find Oracle Forms compiler"
// *Cause :  Library Generator uses the Oracle Forms
//	     compiler to convert forms or common library files between text and
//	     binary formats. Library Generator was unable to
//	     locate the Oracle Forms compiler executable.
// *Action : Make sure the EXECUTE_FORMS_GENTIME registry variable
//	     holds the path of the Oracle Forms compiler executable, and
//	     reinstall if necessary.
00059,3, "Unable to find Oracle Reports compiler"
// *Cause :  Library Generator uses the Oracle Reports
//	     compiler to convert Oracle Reports library files between text and
//	     binary formats. Library Generator was unable to
//	     locate the Oracle Reports compiler executable.
// *Action : Make sure the EXECUTE_REPORTS_GENTIME registry variable
//	     holds the path of the Oracle Reports compiler executable, and
//	     reinstall if necessary.
00060,4, "FORMS60_PATH too long or invalid Form Builder installation"
// *Cause :  To read and write Oracle Forms
//	     binary files, Form Generator accesses the Form
//	     Builder component of Oracle Forms. However, Form
//	     Generator was unable to locate the Form Builder
//	     component.
//	     One possible cause might be that Form Builder
//	     has not been installed.
//	     Another possible cause might be the length of
//	     the FORMS60_PATH Registry variable.
// *Action : Try reducing the length of the FORMS60_PATH
//	     Registry variable. Alternatively, reinstall the
//	     Form Builder component of Oracle Forms.
00061,1, "Named routine '%s' with unrecognized generator comment ignored"
// *Cause :  The generator has encountered a named routine which is marked
//	     with a generator comment, but the comment is badly formatted.
// *Action : If this is a user named routine then you will have to change the
//	     comment at the start of the code to something which doesn't
//	     conflict with generated code.  See the help system for details
//	     on the rules for naming user named routines.
//	     If this is a generated routine which you have modified, you
//	     need to check the comment in the named routine code is
//	     properly formatted.  It should be exactly the same as the named
//	     routine name but with some extra characters appended.
//	     For example, you might add _MODIFIED to the named
//	     routine name as follows:
//	      /* CGLY$CANVAS_MANAGEMENT_MODIFIED */
00062,1, "Ignoring unrecognized code group '/* %s */'"
// *Cause :  The generator has found a code group that it does not recognize.
//	     There may be several reasons for this:
//	     --- You are recovering a form generated by a previous version of
//	     the generator and the code group is no long valid.
//	     --- This is a user event segment which has been given a name
//	     which is reserved by the generator.
//	     --- This is a user modified code group but the comment has been
//	     improperly modified.
// *Action : If you are recovering an old form then ignore this warning.
//	     If this is a user event segment then make sure you do not
//	     have a comment in your code which has a generator
//	     reserved name. i.e CGXX$...
//	     If this is a user modified event segment then check you
//	     have only appended text to the comment and have not
//	     altered the name of the code group.
00063,2, "Cannot find end line for procedure '%s'"
// *Cause :  The recovery tool cannot find the end line for the named
//	     procedure.  This is most probably due to a syntax error in
//	     the procedure text.
// *Action : Check the procedure code for syntax errors.
00064,2, "Cannot find end line for function '%s'"
// *Cause :  The recovery tool cannot find the end line for the named
//	     function.	This is most probably due to a syntax error in
//	     the function text.
// *Action : Check the function code for syntax errors.
00065,2, "Cannot find end line for package spec '%s'"
// *Cause :  The recovery tool cannot find the end line for the named
//	     package spec.  This is most probably due to a syntax error in
//	     the package spec text.
// *Action : Check the package spec code for syntax errors.
00066,2, "Cannot find end line for package body '%s'"
// *Cause :  The recovery tool cannot find the end line for the named
//	     package body.  This is most probably due to a syntax error in
//	     the package body text.
// *Action : Check the package body code for syntax errors.
00067,2, "Cannot capture trigger '%s.%s', error parsing trigger code"
// *Cause :  The recovery tool encountered an error whilst parsing the
//	     trigger text.  This is most likely to be a syntax error in the
//	     trigger text.
// *Action : Check the syntax of the trigger text by compiling it in
//	     Form Builder.
00068,2, "Failed to create binary library file '%s'"
// *Cause :  The attempt to create the binary library file failed.
// *Action : Make sure you have appropriate access rights to write
//	     the file.
//	     Check your Form Builder installation is working correctly.
//	     If the problem still persists then contact your support
//	     representative.
00069,4, "Bad or missing Report Builder installation"
// *Cause :  To read and write Oracle Reports
//	     binary files, Report Generator accesses the Report
//	     Builder component of Oracle Reports. However,
//	     Report Generator was unable to locate the Report Builder
//	     component.
// *Action : Reinstall the Report Builder component of Oracle Reports.
00070,2, "Unable to create text file '%s' from binary library file '%s'"
// *Cause :  To capture a library, Library Generator must first convert the
//	     binary library file into a text file. However, Library Generator
//	     is unable to convert the current library into a text file. The
//	     library might have attached libraries that Library Generator
//	     cannot locate, or Library Generator might be unable to write
//	     the text file to the filesystem, or the library file might be
//	     corrupt.
// *Action : If the library has attached libraries, check that
//	     the locations of the attached libraries are included
//	     in the appropriate path environment variables in the
//	     Registry. To check the library binary file is not corrupt,
//	     open it in Form Builder or Report Builder. Make sure that Library
//	     Generator can save the text file to the filesystem by
//	     removing any write-protected files that have the same
//	     name as the file Library Generator will create, or by
//	     making more space available. If the problem persists,
//	     contact your support representative.
00071,4, "Failed to create Forms API context"
// *Cause :  To read and write Oracle Forms
//	     binary files, Form Generator accesses the Form
//	     Builder component of Oracle Forms. However, an error occurred
//	     when Form Generator attempted to initialize the
//	     Form Builder API.
// *Action : Reinstall the Form Builder component of Oracle Forms.
00074,3, "Form Calling Menu Not Permitted"
// *Cause :  An inter-module action item has been created
//	     in the form with a navigate to property set
//	     to a module of type Menu.
// *Action : Remove Action Item or change Action
//	     Item's Navigate To property to reference
//	     a valid module type.
00075,2, "Illegal value entered for preference AIBBWD for action item '%s'"
// *Cause :  The preference AIBBWD value for this action
//	     item contains an illegal series of characters.
// *Action : This preference value must be either a number
//	     of greater value than zero, or one of the valid
//	     string values defined in the on-line help for this
//	     preference.
00076,1, "Module Argument %s has an illegal item usage"
// *Cause :  A module arguments has an item usage to
//	     a lookup item or an item which is not
//	     in the first navigable block.
// *Action : Delete the item usage or reset the
//	     item usage to a base table item
//	     in the first navigable block.
00077,1, "Increasing length of bound module argument %s to match item %s."
// *Cause :  One of the following:
//	     --- The argument has a length specified in the
//	     Repository which is less than the length
//	     of one of the items which uses this argument.
//	     --- An item using the argument is of type date
//	     and consequently the argument length needs
//	     to be increased to accommodate a 'full date'
//	     format.
// *Action : Increase the length of the module
//	     argument in the Repository to the
//	     length of the parameter in the
//	     generated form.
00078,2, "Badly formed named routine '%s'"
// *Cause :  The Repository definition of the specified named
//	     routine does not have a recognizable beginning and
//	     end.
// *Action : Make sure that the code follows the correct syntax for
//	     a package specification, package body, function or
//	     procedure. In particular, make sure that each code
//	     block after a BEGIN keyword is terminated properly with
//	     "END;" or "END <block name> ;".
00079,2, "Module component %s contains table usages but its Datasource property = NONE"
// *Cause :  The named module component contains table usages.
//	     However, its Datasource Type property has been set to
//	     NONE. This setting is only appropriate for generating
//	     non-database control blocks from module components that
//	     contain no table usages.
// *Action : If the module component is to be generated as a
//	     non-database control block, remove the table usage(s).
//	     If the module component is to be generated as a database
//	     block, set the Datasource Type property to a value other than
//	     NONE (refer to the help system to find out which datasource to use).
00080,1, "Query property of module component %s is set, but its Datasource = NONE"
// *Cause :  The Query property of the named module component has
//	     been set to Yes. However, the module component's
//	     Datasource Type property has been set to NONE, indicating
//	     that it is to be generated as a non-database control block. It is
//	     not possible to query non-database control blocks, so the setting of
//	     the Query property is inappropriate.
// *Action : If the module component is to be generated
//	     as a non-database control block, set the module
//	     component's Query property to No.
//	     If the module component is to be generated
//	     as a queryable database block, select a value other
//	     than NONE for the module component's Datasource
//	     Type property (refer to the help system to find out
//	     which datasource to use).
00081,2, "Module component %s contains table usages but its Datatarget property = NONE"
// *Cause :  The named module component contains table usages.
//	     However, its Datatarget Type property has been set to
//	     NONE. This setting is only appropriate for generating
//	     non-database control blocks from module components that
//	     contain no table usages.
// *Action : If the module component is to be generated as a non-database control
//	     block, remove the table usage(s).
//	     If the module component is to be generated as a database
//	     block, set the Datatarget Type property to a value other than
//	     NONE (refer to the help system to find out which datatarget to use).
00082,1, "Ins/Upd/Del properties of module component %s set, but its Datatarget = NONE"
// *Cause :  One or more of the Insert, Update, or Delete properties
//	     of the named module component has
//	     been set to Yes. However, the module component's Datatarget
//	     Type property has been set to NONE, indicating that it is to be
//	     generated as a non-database control block. It is not possible to
//	     perform DML operations on non-database control blocks, so the
//	     setting of the Insert/Update/Delete property is inappropriate.
// *Action : If the module component is to be generated
//	     as a non-database control block, set the module
//	     component's Insert, Update and Delete properties to No.
//	     If the module component is to be generated
//	     as a database block on which DML operations can be
//	     performed, select a value other
//	     than NONE for the module component's Datatarget
//	     Type property (refer to the help system to find out
//	     which datatarget to use).
00100,0, "ERROR"
// *Cause :  Text used in building up error messages.
// *Action : None.
00101,0, "WARNING"
// *Cause :  Text used in building up warning messages.
// *Action : None.
00102,0, "ERROR: SYSTEM"
// *Cause :  Text used in building up system error messages.
// *Action : None.
00104,3, "Error reading input file."
// *Cause :  The operating system detected an error while reading a file.
// *Action : Check disk for physical errors.
00105,3, "Error rewinding input file."
// *Cause :  The operating system detected an error while trying to reposition
//	     the file pointer to the beginning of the file.
// *Action : Check the disk for physical errors since the file was opened.
00113,4, "Buffer overflow in %s"
// *Cause :  This is an internal error message not normally issued.
// *Action : Contact your Customer Support representative.
00117,4, "Location %s,	invalid code %d"
// *Cause :  This is an internal error message not normally issued.
// *Action : Contact your Customer Support representative.
00158,2, "Log file %s is empty"
// *Cause :  The log file, which should contain any errors or warnings issued
//	     during generation, does not contain any non-space characters.
// *Action : Ensure that there is enough disk space available to write the
//	     file.
00160,4, "Assertion failed in %s, at %s:%d"
// *Cause :  This is an internal error message not normally issued.
// *Action : Please make a note of the full error stack following this
//	     error message and contact your Customer Support representative.
00162,0, "Call failed in %s, at %s:%d"
// *Cause :  This is an internal error message not normally issued.
// *Action : Contact your Customer Support representative.
/
/ 00200 .. 00299 Generator User Preferences Errors and Warnings
/
00200,1, "BLKSBP value different for consecutive subcomponents"
// *Cause :  A floating scrollbar can only be in one
//	     place for all the subcomponents which
//	     share it, therefore all those subcomponents
//	     should have the same BLKSBP value
// *Action : Set BLKSBP to the same value for all
//	     subcomponents which share a floating
//	     scrollbar
00228,4, "Invalid configuration: No registry key found for product"
// *Cause :  An unexpected internal error has been encountered
// *Action : Call your support representative
/
/ 01001 .. 02000 Forms generator Errors and Warnings
/
01001,1, "No PL/SQL block text for button item	%s.%s; Button has no functionality."
// *Cause :  an item has been defined having a display datatype
//	     of 'BUTTON', but no PL/SQL has been defined that will determine
//	     the generated buttons functionality.
// *Action : Define PL/SQL block text for button item.
01002,2, "Too many alternate regions"
// *Cause :  The Oracle Form Generator can only support one
//	     alternate region per block
// *Action : Stack all the item groups into one alternate region
01003,1, "Set Placement property to New Tab Canvas Page because no preceding component"
// *Cause :  Form Generator has detected that:
//	     --- the module component has the Placement property
//	     set to Same Tab Canvas Page
//	     --- there is no preceding module component with
//	     its Placement property set to New Tab Canvas Page
//	     Therefore, Form Generator has set the module component's
//	     Placement property to New Tab Canvas Page during generation.
//	     Form Generator attempts to save (or proposes) this
//	     adjustment to the property to bring the module
//	     definition into line with the generated output.
// *Action : If adjustment saved, no action necessary (Form Generator has
//	     saved the change to the property).
//	     If adjustment proposed, browse/edit the proposed change
//	     before saving/discarding it.
//	     If adjustment failed, no action necessary (Form Generator is
//	     unable to save the change to the property).
01004,1, "Placement property ignored: Not enough tab pages can be generated"
// *Cause :  Form Generator only generates blocks onto
//	     tab canvas pages when at least two module
//	     components within the same content
//	     canvas have Placement properties
//	     set to New Tab Canvas Page.
// *Action : To generate blocks onto tab canvas pages,
//	     set the Placement property of at least one other module
//	     component within the same content canvas
//	     to New Tab Canvas Page.
01005,1, "OCX/ActiveX Control Implementation %s for %s.%s not found"
// *Cause :  The given item has a Display Datatype of OCX but a Custom Item
//	     of type OLE Container named as its Implementation cannot be
//	     found in the template form.
// *Action : Ensure that the Implementation for the Repository Item is the
//	     name of a Custom Item in the template form of type OCX Control.
01006,1, "Descriptive Flex name not defined, DFLEX usage ignored"
// *Cause :  The preference DFNAME has a null value in the context of the
//	     given item, but a value is required.
// *Action : Specify the name of the required descriptive flex using the
//	     preference DFNAME
01007,1, "No Implementation specified for OCX/ActiveX Control %s.%s"
// *Cause :  The specified Repository item is defined as display datatype OCX
//	     but the 'Template/Library Object' property is not set.
// *Action : Set the 'Template/Library Object' property of the Repository
//	     item to an OCX control in the template form.
01008,1, "Failed to change directory to %s"
// *Cause :  No further information available.
// *Action :
01009,1, "Application short name not defined, DFLEX usage ignored"
// *Cause :  The preference DFAPPL has a null value in the context of the given
//	     item, but a value is required
// *Action : Specify the application short name using the preference DFAPPL
01010,1, "Lookup Validation WHERE clause is invalid:\n%s"
// *Cause :  The Lookup Validation where clause and any column ordering have
//	     been built up into a WHERE clause for the block.
//	     This has failed to parse.
// *Action : Correct the restrictive lookup validation condition held on the
//	     detailed table usage in the module definition.
01011,1, "Block with name %s already exists in form, existing block has been deleted."
// *Cause :  One of the following:
//	     --- The template contains a block with a name
//	     that is also specified in the Repository
//	     --- The Preserve Layout option has been chosen and
//	     a block originally generated for a particular
//	     window in the form, has been moved to a
//	     different window in the form or the corresponding
//	     module component has been moved to a different
//	     window in the Repository.
// *Action : One of the following:
//	     --- Change name of block
//	     --- If preserving layout, ensure that the
//	     block in the original form and the
//	     equivalent module component in the
//	     Repository are positioned in the same
//	     window.
01012,2, "Inter-module key based links are not supported by this generator"
// *Cause :  The Repository definition of a module includes a
//	     module component with a key based link from
//	     a module component belonging to a different
//	     module.
// *Action : Remove the Key Based Data Link from
//	     the module component in the source
//	     module. Use the 'called module' with
//	     'passed parameters' functionality to
//	     pass data from one module to another.
01013,1, "Module component %s has multiple multi-row layout regions with scrollbars"
// *Cause :  You have defined more than one scrollbar for
//	     the specified primary module component and/or
//	     its module subcomponents by setting their
//	     Rows Displayed properties to values other than 1.
//	     However, a multi-region block (like any other block
//	     in a form) can only have one scrollbar.
//	     Form Generator cannot determine
//	     which layout
//	     region is to have the scrollbar and therefore:
//	     ---creates the scrollbar for
//	     the first multi-row layout region
//	     ---issues this warning
// *Action : Do one of the following:
//	     ---set MRBVSB to Yes for the module
//	     component from which the multi-row
//	     layout region containing the scrollbar is generated, and
//	     set MRBVSB to No for all other
//	     multi-row module components generated
//	     into the multi-region block
//	     ---change the Rows Displayed properties of the primary
//	     module component and its module sub-components so
//	     that only one of them has its Rows Displayed
//	     property set to a value not equal to 1
01014,1, "'Validate in LOV' for item %s.%s not available. Building trigger code."
// *Cause :  It has been requested that List of Values be used to perform the
//	     validation of the specified item (by setting the preference
//	     LOVVAL=Y). However this is not possible because the column on
//	     which the item is based is:
//	     --- part of a multi-column foreign key, or
//	     --- within a domain which includes ranges as well as discrete values
//	     Validation will therefore be performed by PL/SQL code built on
//	     triggers.
// *Action : No action required
01015,1, "Failed to load template form %s"
// *Cause :  Form Generator cannot find the template form you have specified.
// *Action : Make sure the template form exists either in the file system
//	     or on the specified database.
01016,1, "Failed to extract PL/SQL Block Text property"
// *Cause :  To capture the PL/SQL Block Text property of this
//	     Repository item, the corresponding form item's
//	     WHEN-BUTTON-PRESSED trigger code must be
//	     syntactically correct. However, Form Generator
//	     detected a syntax error while parsing the trigger code
//	     and was therefore unable to capture the PL/SQL
//	     Block Text property.
// *Action : To locate the syntax error,
//	     load the form into Form Builder and attempt
//	     to compile the trigger.
//	     When you have corrected the syntax error,
//	     capture the form again.
01017,1, "Flag %s ignored on column with range"
// *Cause :  The column specified has been defined to have a range but also has
//	     either the 'Suggested List' flag and/or the 'Dynamic List' flag set
//	     against the column.  It is not considered sensible to have these
//	     flags set AND ranges as well, therefore the flags will be ignored
//	     and the column will be generated with validation against the range.
// *Action : You will need to decide which method of validation is appropriate
//	     for the column in question and set the flags accordingly.
01018,1, "Flags %s and %s ignored on column with ranges"
// *Cause :  The column specified has been defined to have a range but also has
//	     either the 'Suggested List' flag and/or the 'Dynamic List' flag set
//	     against the column.  It is not considered sensible to have these
//	     flags set AND ranges as well, therefore the flags will be ignored
//	     and the column will be generated with validation against the range.
// *Action : You will need to decide which method of validation is appropriate
//	     for the column in question and set the flags accordingly.
01019,1, "An equivalent relationship already exists between blocks '%s' and '%s'"
// *Cause :  During generation the generator has attempted to
//	     create a relationship between two blocks which already
//	     exists.
//	     The existing relationship will be used.
// *Action : None.
01020,1, "Not generating help for module as help table not created"
// *Cause :  The CG_FORM_HELP table does not exist, therefore unable
//	     to store help information.
// *Action : Create the CG_FORM_HELP table.
01021,1, "Inclusion Object '%s' can not be found in the Object Library"
// *Cause :  An object name has been entered in the module's
//	     "Template/Library Objects" list that could not be
//	     found in the Object Libraries used in this generation.
// *Action : Check that the object exists in the Object Libraries used
//	     in generation.
//	     Check that the Object Libraries required are being used
//	     in generation.
01022,2, "No base canvas in window %s for stacked canvas %s"
// *Cause :  during generation, the Form Generator checks that a popup
//	     canvas has a base canvas (named CG$PAGE_...) in the same window.
//	     This error is flagged because no base canvas has been found.
// *Action : Check that the CG$PAGE... canvases have not been deleted or renamed
//	     since the form was generated.
01023,1, "Value in item Help Context Id Prefix contains a negative value or is unset."
// *Cause :  The Help Context Id item is only allowed to have a positive number
//	     specified.  It must contain a value for Help to work.
//	     Help information will not be available at this level.
// *Action : Make sure it is set to a positive number
01024,2, "Underlying column with the prefix '%s' may cause problems in generated code"
// *Cause :  This is an integrity check on the Repository.
//	     Because Form Generator creates parameters for form
//	     level procedures with this prefix there may problems resolving
//	     the names of the column and the PL/SQL parameter.
//	     This is most likely to be a problem if the column is named
//	     P_ROWID or the cascade delete rule is enforced in the form.
// *Action : Rename the column.
01025,1, "Help Generator has not been run or a new help item has been added since"
// *Cause :  The Help Context Id is null in the Repository.
//	     Help information will not be available at this level.
// *Action : Run the Help Generator
01026,1, "'%s' is not a valid overflow action for block %s based on table %s"
// *Cause :  In the table layout, a block position of "NEW STACKED CANVAS
//	     or "SAME STACKED CANVAS" has been chosen. In addition,
//	     an overflow style of "SPREAD TABLE" has been set or
//	     defaulted from the default block overflow action preference
//	     (BLKOVF).
//	     The generator cannot build a spread table on a stacked canvas
//	     since if the canvas view size is smaller than the canvas size,
//	     the spread table will remain fixed when the popup scrolls. This is
//	     because the spread table is implemented as a stacked canvas
//	     which is anchored to the underlying content canvas, not the
//	     stacked canvas.
// *Action : The generator created the block using the "WRAP LINE" overflow
//	     style.  Set an overflow style of something other than "SPREAD TABLE"
//	     to remove this warning.
01027,1, "Preference %s has invalid value, defaulted to zero"
// *Cause :  For a preference which can use real units, the generator cannot
//	     read a valid number from the entered value, or the preference is
//	     null.
// *Action : Enter a valid value in the correct format, eg "0.25 in"
01028,1, "No implementation class specified for Bean Area"
// *Cause :  The Display Type of the specified Repository item is
//	     set to Bean Area but its Template/Library Object
//	     property is not set.
// *Action : Set the specified Repository item's Template/Library Object
//	     property to the name of a Bean Area item in the object library.
01029,1, "Visual Attribute %s not found in template form"
// *Cause :  To generate current record indicator items the visual attributes
//	     named CG$CURRENT_RECORD and CG$OTHER_RECORD should exist in the
//	     template form.
// *Action : Create these visual attributes in the template form.
01030,2, "Parameter prefix %s not allowed; try %s instead"
// *Cause :  The preference PARAMP is used as a prefix for parameters in
//	     generated PL/SQL.	It must start with a letter and
//	     contain only those characters which are legal in PL/SQL variable
//	     names; i.e. alpha-numeric, underscore and dollar sign.
// *Action : Correct the preference PARAMP.
01031,1, "Table names %s and %s are not unique within %s characters"
// *Cause :  The table names as entered in the Repository are not unique
//	     within the specified number of characters. This may cause
//	     problems during generation as they are used for naming and
//	     identifying objects in the generated code.
// *Action : Rename the tables identified in the Repository.
01032,1, "Item groups are on stacked canvases not tab canvases"
// *Cause :  In the form being captured, a stacked
//	      item group appears on
//	     a stacked canvas that has the same dimensions as
//	      another stacked
//	     canvas.  Form Generator considers the stacked
//	     canvases to be an
//	     alternative implementation of a native Oracle Forms
//	      tab canvas.
// *Action : If you generate a form from the captured module,
//	     use CANNTC to control how Form Generator
//	     generates the stacked item group:
//	     --set CANNTC to No to generate the stacked
//	     item group onto a stacked canvas
//	     --set CANNTC to Yes to generate the stacked
//	     item group onto a native Oracle Forms tab
//	     canvas page
01033,1, "Form '%s' may not return the domain meaning."
// *Cause :  If the DVDSPM (display domain meaning) preference is set to 'Y'
//	     and the DVLOVF preference is set to use a form.
// *Action : The list of values form specified with the DVLOVF preference must
//	     assign the meaning item to the global variable
//	     ':GLOBAL.CG$REF_MEANING' after the user has selected a value.
01034,2, "Column %s.%s is not allowed in an expression"
// *Cause :  A lookup table column that is part of a foreign key has been
//	     used in an expression.
// *Action : Remove column reference from expression.  Use the base table column
//	     of the foreign key.
01035,1, "OLBLST preference specifies object '%s'  that already exists in the form"
// *Cause :  The OLBLST preference specifies
//	     the name of an object which is already
//	     present in the form being generated. This may
//	     have occurred because an object of the same
//	     name and type is also present in the template
//	     form being used for generation.
// *Action : Ensure the object of the same name and type is
//	     not present in the original form being generated
//	     (eg. if present in the template remove the
//	     object from the template).
//	     Otherwise, remove the name of the
//	     object from the OLBLST preference
01036,1, "Block %s has the Current Record Visual Attribute property set"
// *Cause :  The block has the Current Record Visual Attribute Group property
//	     set.
// *Action : If you wish to achieve the same results as setting this property on
//	     generation, set the CURREC preference against the captured
//	     module component.
01037,1, "Cannot generate a block node for '%s'"
// *Cause :  The module component for this block has
//	     a base table usage based on a table with
//	     no primary key defined in the server model.
// *Action : Specify a primary key for the Server Model
//	     table which the module component base
//	     table is based.
01038,1, "Cannot add valid value '%s' to record group for item"
// *Cause :  A valid value has been specified for a
//	     data/number column but the correct
//	     format mask property for the column has
//	     not been specified.
// *Action : Specifiy an appropriate format mask for the
//	     repository column definition for this item and
//	     ensure that all valid values for this column
//	     are in a format which matches this format
//	     mask.
01039,1, "Non-validated FK is ignored"
// *Cause :  The foreign key specified is has a "Validate In" property on "NONE".
//	     as such it cannot be used in this table usage where
//	     INSERT and/or UPDATE are allowed.
// *Action : None required.
01040,1, "Preference %s has invalid units - character cells selected"
// *Cause :  The specified preference value includes a string to
//	     represent the units, but this cannot be understood
//	     by Forms Generator
// *Action : Enter the units string correctly into the preference,
//	     or simpy enter a numeric value for character cells.
01041,1, "Block %s cannot be placed to the right of block %s"
// *Cause :  The block being captured was originally generated
//	     to the right of another block. However, that second
//	     block no longer exists in the same window. Therefore,
//	     the Right of Component property of the module
//	     component created from the captured block cannot
//	     be set.
// *Action : If appropriate, use the Right of Component property
//	     of the module component created from the captured
//	     block to specify the name of another module
//	     component in the same window.
01042,1, "Could not find environment variable %s : Report cannot be run"
// *Cause :  The generator could not find the environment variable specified
//	     in the registry and therefore cannot run the report.
// *Action : The report uses Oracle Reports runtime to show the logfile, you may
//	     not have this installed.
//	     If you have Oracle Reports installed then the environment variable
//	     specified needs to be set in the registry.
01043,1, "Custom links are not supported by this generator."
// *Cause :  A custom link has been defined between two
//	     module components in a module.
// *Action : No action required; Generator will just ignore any
//	     custom links in the module. To avoid this message,
//	     the custom link must be deleted from the module.
01044,2, "Return list of LOV '%s' does not include associated item (%s)"
// *Cause :  The LOVVAL preference is set to Yes
//	     but the LOV being processed does not return a value to
//	     the item that the LOV is associated with.	Therefore, it is
//	     not possible to validate the item with this LOV.
// *Action : Do one of the following:?
//	     --- do not specify a return list (for LOVs associated with bound
//	     items) so that Form Generator creates a default return list
//	     --- include the item with which the LOV is associated with in the
//	     return list
01045,1, "Set Overflow property to %s because %s invalid with stacked item groups"
// *Cause :  Form Generator has detected that:
//	     --- the module component contains items that
//	     are in a stacked item group
//	     --- the module component has the Overflow property
//	     set to Spread Table
//	     Therefore, Form Generator has set the module
//	     component's Overflow property to Wrap Line
//	     during generation instead.
//	     Form Generator attempts to save (or proposes) this
//	     adjustment to the property to bring the module
//	     definition into line with the generated output.
// *Action : If adjustment saved, no action necessary (Form Generator has
//	     saved the change to the property).
//	     If adjustment proposed, browse/edit the proposed change
//	     before saving/discarding it.
//	     If adjustment failed, no action necessary (Form Generator is
//	     unable to save the change to the property).
01046,1, "Drilldown generated as current record indicator"
// *Cause :  You have defined a drilldown indicator in a block that has no
//	     detail blocks. Therefore there is nothing to drilldown to and the
//	     item will be generated as a normal current record indicator
// *Action : Define a detail block for the block containing the drilldown
//	     indicator
01047,2, "Form template %s not on template path"
// *Cause :  The specified form template could not be found on the template
//	     path
// *Action : Check your template path, form template name and if the form
//	     template exists
01048,1, "Unable to process the following ORDER BY clause: <%s>"
// *Cause :  During the Design Capture operation a block's ORDER BY clause
//	     was found to contain expressions that were not simple column names.
//	     This type of information is not stored in the Repository, so
//	     nothing can be extracted from the clause.
// *Action : Column usages resulting from this default ordering specification
//	     must be entered manually, if desired.
01049,1, "Conflicting LOV usages defined.  Only using 'Query & Data Entry' usage."
// *Cause :  You have a 'Query & Data Entry' usage of a LOV
//	     as well as a 'Query' or 'Data Entry' usage.
//	     Form Generator will ignore the 'Query' or 'Data Entry'
//	     usages since they	conflict with the 'Query & Data
//	     Entry' usage.
// *Action : Delete one of the usages to remove the conflict.
01050,1, "Item(s) in block %s have the Current Record Visual Attribute property set "
// *Cause :  One or more items in the block has the Current Record Visual
//	     Attribute Group property set.
// *Action : If you wish to achieve the same results as setting this property on
//	     generation, either set the CURREC preference against the captured
//	     module component to an appropriate value, or create an unbound
//	     item of type "CURRENT RECORD" in the captured module component.
01051,1, "Preference PAGEXP ignored since canvas expansion required for %s  "
// *Cause :  The current content canvas needs to be expanded
//	     to display the number of rows requested.
//	     However, the user preference 'PAGEXP' is set to N
//	     so this has been ignored.
// *Action : Set the user preference 'PAGEXP' to 'Y'
01052,1, "Failed to load referenced form %s"
// *Cause :  At least one object in the form you are capturing has
//	     been subclasses from an object in another form that
//	     cannot be located.
// *Action : Include the specified form in a directory in the
//	     FORMS60_PATH Registry variable.
01053,1, "'%c' is used for ITMSPM and ITMFPS"
// *Cause :  The same character has been specified (via the preferences) to
//	     indicate the optional item split prompt marker (ITMSPM) and the
//	     mandatory item force prompt split marker (ITMFPS).
// *Action : Review why the same character has been chosen for each of these
//	     preferences.
01054,1, "'%c' is used for ITMFPS and ITMPPM"
// *Cause :  The same character has been specified (via the preferences) to
//	     indicate the mandatory item force prompt split marker (ITMFPS) and
//	     the item post prompt marker (ITMPPM).
// *Action : Review why the same character has been chosen for each of these
//	     preferences.
01055,2, "Unable to do %s of item %s in block %s"
// *Cause :  A summary item is based on an item which cannot be summarized.
// *Action : Either base the summary item on an item which can have
//	     summaries performed on it or change the type of the summarized
//	     item.
01056,2, "Column %s.%s required for derivation expression not found"
// *Cause :  The derivation text references a column that has not been
//	     included in the block which contains the derived column.
// *Action : Add the column to your module definition in the same
//	     module component as the derived column. If the added
//	     column belongs to a lookup table ensure that the
//	     "Create Lookup Item?" property is set to "Yes"
01057,2, "Unable to do %s of item %s in block %s"
// *Cause :  The formula item summarized by the summary item contains
//	     references to other formula items. This is not allowed when there
//	     is more than one row in the master block containing the
//	     summary item.
// *Action : Remove references to other formula items in the summarized
//	     formula item.
01058,2, "Object library %s is not on template path"
// *Cause :  The specified object library could not be found on the template
//	     path.
// *Action : Check your template path, object library name and if the
//	     object library exists.
01059,2, "Failed to load object library %s"
// *Cause :  Form Generator failed to load the object library
// *Action : Try loading the object library into
//	     Form Builder to check the file is not corrupt.
01060,2, "Failed to load menu template %s"
// *Cause :  The menu failed to load.
// *Action : Try loading the menu into Form Builder to check
//	     the file is not corrupt.
01061,2, "Invalid derivation expression '%s' for this item's type"
// *Cause :  The derivation expression is invalid for an item of this type.
// *Action : Amend the derivation expression so that it is valid
//	     for the item type.
01062,2, "Required item %s used in derivation expression not found in module"
// *Cause :  An item referenced in a derivation expression recorded
//	     against an item or column was not found in the
//	     repository module definition.
// *Action : Add the missing item to the module definition or
//	     change the derivation expression.
01063,1, "Failed to load object library %s"
// *Cause :  At least one object in the form you are capturing has
//	     been subclasses from an object in an object library that
//	     cannot be located.
// *Action : Include the specified object library in a directory in the
//	     FORMS60_PATH Registry variable.
01064,1, "Action Item %s has illegal Source for CALL METHOD Named Passed Value"
// *Cause :  When using the Named Passed Value CALL METHOD, you
//	     should only set it's source to be Value, not Item or Argument.
//	     Otherwise the default CALL METHOD is used (OPEN FORM).
// *Action : Set the source of the Named Passed Value CALL METHOD
//	     to be a Value, not an Item or Parameter.
01065,2, "Invalid PL/SQL Block text - '%s'"
// *Cause :  Invalid text was entered in the PL/SQL text for this item.
// *Action : Correct the text.
01066,1, "Dynamic list flag ignored for item with range"
// *Cause :  The item specified has been defined to have a range but also has
//	     'Dynamic List' flag set against the domain being used.
//	     It is not considered sensible to have this flag set AND ranges
//	     as well, therefore the flags will be ignored and the column will
//	     be generated with validation against the range.
// *Action : You will need to decide which method of validation is appropriate
//	     for the item in question and set the flag accordingly.
01067,1, "%s is unsupported language for called modules from Forms"
// *Cause :  A Navigation Action Item was defined with a target module in
//	     an unsupported language.
// *Action : Change the target of the Navigation Action Item to be
//	     a module of a supported language.
01068,1, "is not supported"
// *Cause :  The Named Passed Value is not supported and so will be ignored.
// *Action : Use one of the supported Named Passed Values or remove
//	     this one.
01069,1, "Object Library/Template %s does not exist in the Forms Path"
// *Cause :  The Forms Path registry variable does not
//	     include the object library/template path.
//	     With the current registry settings,
//	     compilation errors may occur when
//	     trying to compile and/or run the generated
//	     form.
// *Action : Modify the Forms Path registry variable
//	     to include the template/object library
//	     path.
01070,1, "Skipping data block '%s' as it is not based on a table or view"
// *Cause :  A database block was found in the form that is not
//	     based on either a table or view.
// *Action :
01071,1, "Path for Object Library/Template %s is inconsistent with Forms Path"
// *Cause :  The Forms Path registry variable includes
//	     another directory	(of higher precedence) which
//	     contains an object library/template with the same
//	     name. If the generated form is compiled/run,
//	     with the current registry settings, the object
//	     library/template from a different directory
//	     will take precedence and be used by the Forms
//	     Compiler.
// *Action : Modify the Forms Path registry variable
//	     to include the template/object library
//	     path. Ensure this path has a higher
//	     precedence than any other directories
//	     which include an object library/template
//	     of the same name.
01072,1, "Skipping item '%s' as it is displayed on a toolbar canvas"
// *Cause :  This control block item is displayed on a toolbar
//	     canvas, which may cause problems on
//	     generation.
// *Action : If you want to capture this item you should change
//	     the canvas it is displayed on to something other than
//	     a toolbar canvas.
01073,1, "Formula item '%s' has an invalid formula"
// *Cause :  This calculated formulan item either has an invalid formula
//	     or the formula property for the item is empty.
//	     This item will be marked as a custom unbound item.
// *Action : If you want to capture this item as the correct
//	     type you should either change the formula to
//	     make it valid or mark the item as non-calculated.
01074,1, "Summary item '%s' has an empty mandatory property"
// *Cause :  This calculated summary item has an empty
//	     mandatory property on the form.
// *Action : To capture this item correctly set the empty
//	     property on the form to a valid value. The
//	     possible empty values are summary function,
//	     summarized block name or summarized item
//	     name.
01075,2, "Failed to create HTML file for form module %s"
// *Cause :  The command to create the HTML file required to run
//	     the form as a webform has failed.
//	     There might be a problem with your environment.
// *Action :
01076,1, "Implementation source object specified (%s), but no Object Library loaded"
// *Cause :  An implementation source object was specified but no object
//	     library is currently being used. Generation will continue, but the
//	     implementation source object cannot be used.
// *Action : Specify an object library that contains the implementation
//	     source object, or remove the implementation source object
//	     from the definition of the Repository object.
01077,1, "Implementation source object %s of correct type not found in Object Library"
// *Cause :  An implementation source object was specified but an
//	     object of that name and type does not exist in the
//	     object library that is currently being used. Generation
//	     will continue but the object will not be based on the
//	     implementation source object.
// *Action : Add a definition of the named implementation source object
//	     to the object library that is currently being used, or specify an
//	     object library that contains a definition of the named object.
01078,1, "Invalid default value %s"
// *Cause :  The argument CG$STARTUP_MODE or named passed
//	     value STARTUP_MODE is used to control the
//	     default mode which this module starts in. The value you
//	     enter was not a supported startup mode. The generator has
//	     defaulted to use startup mode NORMAL.
// *Action : Change the default value of argument CG$STARTUP_MODE or
//	     named passed value STARTUP_MODE to
//	     be one of the supported values.
01079,3, "Cannot find a content canvas for stacked canvas %s"
// *Cause :  Form Generator is trying to generate canvas
//	     management code to manage the stacked canvas.
//	     It cannot find a base canvas (a canvas named CG$PAGE...)
//	     for this stacked canvas.
//	     The most likely cause is that the FMB file has been edited
//	     and the content canvas has been renamed or deleted.
// *Action : Make sure that the names of CG$PAGE canvases
//	     have not been changed.
//	     If this error still occurs, please inform your support
//	     representative
01080,1, "Default value for item is greater than %s characters"
// *Cause :  The length of the default value for an item or
//	     module argument is greater than the Repository
//	     limit.  The default value will be ignored.
// *Action : Either change the default value in the form
//	     and run the Design Capture tool again, or
//	     amend the default value in the Repository to
//	     a correct value.
01081,1, "Hint text for item is longer than %s characters"
// *Cause :  The length of the hint text for an item is
//	     greater than the Repository limit.
//	     The hint text will be truncated to be
//	     within the limit.
// *Action : Either change the hint text for the item in
//	     the form and run the Design Capture tool again, or
//	     amend the hint text in the Repository.
01082,1, "Nested stacked groups not supported; stacked flag ignored"
// *Cause :  Tab canvases must be placed on a content canvas.
//	     A tab canvas cannot be placed on another tab
//	     canvas; there is no implementation of nested
//	     tab canvases.
// *Action : To remove this warning, unset the item group
//	     stacked flag.
01083,1, "Making item %s the first item in List of Values '%s'"
// *Cause :  The validate using LOV preference 'LOVVAL' is set to 'Y'
//	     and the item being validated is currently not the first
//	     item in the lookup table usage. This item needs
//	     to be the first item in the list so that Forms can do the
//	     validation.
// *Action : If you want this item to appear elsewhere in the
//	     list you must set LOVVAL to 'N' so that validation
//	     is carried out using triggers.
01084,1, "Library module '%s' not found in the Repository"
// *Cause :  An attached library in the form being captured has no corresponding
//	     module in the Repository. Therefore no link will be created from the
//	     form module.
// *Action : If you want to create a link from the form module you should
//	     do  one of the following:
//	     --- Create a library module in the Repository with the same name
//	     as the attached library, and then re-run the Forms Design Capture
//	     tool.
//	     --- Use the Library Design Capture tool to capture the library, and
//	     then re-run the Forms Design Capture tool.
01085,1, "Not extracting template from database, already exists on file system (%s)"
// *Cause :  Template with same name as template being extracted from the
//	     database exists in the current directory.
// *Action : Remove template on file system.
01086,1, "Attached library '%s' not found in forms search path. Using full path name."
// *Cause :  Form Generator could not locate the library to attach
//	     to the generated form in any of the paths specified by
//	     the appropriate Oracle Forms Registry variables.
//	     However, Form Generator did locate the library in the path
//	     specified as the destination for generated library modules.
//	     To ensure that the library is located at runtime, Form
//	     Generator has hard coded that path into the generated form.
//	     However, hard coding the path into the form makes the
//	     generated application significantly less portable, and is
//	     therefore not recommended.
// *Action : Add the path identifying the location of the attached library
//	     module to the appropriate Oracle Forms Registry variable.
//	     Consult the Oracle Forms documentation if you are not sure
//	     which Registry variable to use.
01087,1, "'%s' Lookup list item not generated: other lookup items are also displayed"
// *Cause :  A lookup list item (Poplist or Textlist) has
//	     been specified in a lookup table usage
//	     where other lookup items are also set
//	     as displayed.
// *Action : Ensure that the lookup list item is
//	     the only lookup table usage item
//	     with the 'display' property set to
//	     'yes'.
01088,1, "'%s' Lookup list item not generated: foreign key item is set to displayed"
// *Cause :  At least one base table usage
//	     foreign key item is specified as
//	     displayed.
// *Action : Ensure that all base table usage foreign
//	     key columns have the 'display' property
//	     set to 'no'.
01089,1, "'%s' Lookup list item not generated: source column is not unique"
// *Cause :  The table column which the
//	     lookup list item is based upon
//	     is not the only member column
//	     of a unique key for the table.
// *Action : Set the lookup list item to be based
//	     upon a table column where the
//	     column is the only member column
//	     of a unique key defined for the table.
01090,1, "Lookup item %s is enforced by a constraint that is not validated in the form"
// *Cause :  The form module created from this Repository
//	     module definition would have a non-base table
//	     item for the lookup item. However, this
//	     lookup is enforced by a constraint that has its
//	     Validate In property set to SERVER or NONE.
//	     Form Generator will override this setting
//	     and treat the constraint as a client
//	     validated constraint
// *Action :
01091,2, "Cannot open user-specified HTML file"
// *Cause :  The forms generator was unable to open the HTML
//	     file specified by preference WEBHTM.
//	     The file may be missing or corrupted.
// *Action : Ensure that the value entered for WEBHTM points to
//	     a valid HTML file.
01092,1, "Content canvas items may not be aligned with tab content canvas items"
// *Cause :  The preference CANNTC is set to Yes and there
//	     are multi-record stacked item groups.
//	     Items on the generated tab canvases may not
//	     be aligned with items on the underlying content
//	     canvas.
// *Action : Do one of the following:
//	     --- Include all items in stacked item groups and
//	     generate the form again.
//	     --- Set CANNTC to No and generate the form
//	     again to produce an alternative
//	     implementation of tab canvases in which stacked
//	     item groups are placed on different stacked canvases
//	     and accessed via a poplist.
//	     --- Set the item group's Layout property to Standard
//	     and generate the form again to display a single
//	     record on the tab canvases .
//	     --- Use Form Builder to change the generated layout
//	     and align the items on the tab canvases with the items on
//	     the content canvas.
//	     --- If the items are not aligned because of the offset caused
//	     due to the width of tab page edge, you can alter it using
//	     the x attribute of the CG$VIEW_OFFSET tag in the comment
//	     property of tab canvas standard object. For more information,
//	     refer to the help topic Aligning context items on tab canvases
//	     with items on spreadtable blocks.
01093,1, "'%s' Lookup list item not generated: some foreign key items are not present"
// *Cause :  At least one base table
//	     foreign key column has not
//	     got an item defined for it.
// *Action : Ensure that all base table foreign
//	     key columns have base table usage
//	     items defined for them and that all the
//	     items' display' properties are set to 'no'.
01094,1, "'%s' Lookup Table Usage contains illegal validation clause"
// *Cause :  The Lookup's 'Validation Where Clause Property'
//	     contains a reference to a generated item in the
//	     current block/module component, which means
//	     that the lookup list item will not have its values
//	     populated correctly in a running form.
// *Action : Remove part of the validation clause
//	     which references an item in the current
//	     block/module component.
01095,1, "Contains Hierarchical Tree Item - must not contain any other items"
// *Cause :  Module components containing Hierarchical Tree Items should
//	     not have any other items, whether they be bound or unbound items.
// *Action :
01096,1, "Updateable item %s in non-updateable key; Update set to No"
// *Cause :  The Update Allowed propery of the specified Oracle Forms item
//	     is set to Yes.  However, Form Generator has detected that the
//	     item is based on a column that is part of a non-updateable
//	     primary key or unique key.  During design capture, Form
//	     Generator therefore sets the captured Repository item's
//	     Update property to No.
// *Action :
01097,1, "Generation of more than two master module components is not supported "
// *Cause :  The module contains a module component which has
//	     more than two master module components linked
//	     to it.
// *Action : Remove excess links to the detail module component
//	     so that only two master module components are linked
//	     to the detail module component.
01098,2, "Table Usage contains no items"
// *Cause :  A table usage has been defined containing no items
// *Action : Either remove the table usage or add some items
01099,2, "Unable to pass value from item %s; item not included in generated form"
// *Cause :  The argument passed value or named passed
//	     value is based on the specified repository item. However,
//	     the repository item does not have a corresponding item in
//	     the generated form. One reason for this might be that the
//	     repository item is a lookup list item.
// *Action : Create a usage of the module argument definition by
//	     a different repository item.
01100,1, "Ignoring unrecognized object %s attached as a called module"
// *Cause :  Form Generator does not recognize an object attached
//	     to the module via the module network.  Therefore, Form
//	     Generator has ignored the attachment.
//	     For example, you might attach a function to a module
//	     under Called Modules.  However, Form Generator does
//	     not recognize such an attachment as valid and ignores it.
// *Action : No action required.  Form Generator ignores the attachment
01101,2, "Failed to insert some or all of the required help text into the help table"
// *Cause :  The Generator has failed to insert help text into
//	     the help table (either directly or using a synonym)
//	     for one or both of the following reasons:
//	     --- the help table has an incorrect structure
//	     --- you do not have INSERT access to the help table
// *Action : Make sure:
//	     --- the help table has the correct structure (with the correct
//	     columns and column sizes)
//	     --- you have INSERT access to the help table
//	     Note: Any help that was successfully inserted before this
//	     error occurred will be updated next time help is generated
//	     for this module.
01102,2, "Impossible prompt layout"
// *Cause :  This is an internal error message not normally issued.
// *Action : Contact your Customer Support representative.
01103,1, "Item is not a text item so ignoring LOV attachment"
// *Cause :  There is a list-of-values attached to a repositiory
//	     item that has its display type not set to Text.
//	     This is not valid in Developer and therefore will
//	     be ignored
// *Action : If you want a list-of-values for this item then
//	     set the display type to text
01104,1, "Table Usage Where Clause cannot be included in Navigator: '%s'"
// *Cause :  Where Clause contains a reference to a form item.
// *Action : Remove item reference from Where Clause, if
//	     Where Clause is required in the Navigator.
01105,1, "Display length of right justified item %s.%s has been truncated."
// *Cause :  This occurs when the generator has to truncate the display length
//	     of the named item in order to fit it into the necessary width.
//	     This may result in the whole or part of the item's value not
//	     being visible when records are queried. However, the item will be
//	     scrollable so that the whole of the value can eventually be seen.
// *Action : No action required.  To avoid this warning in future executions
//	     of Form Generator, consider altering preference values so that
//	     more width is available in order to layout the items of the form.
01106,3, "Corrupt information in Comment property of generated item %s"
// *Cause :  During generation, Form Generator adds information to the
//	     Comment property of generated items to enable the items to
//	     be captured correctly. However, during design capture
//	     Form Generator has detected
//	     that the information in the Comment property for the specified
//	     generated item has been altered or corrupted in some way. Form
//	     Generator is therefore unable to capture the item.
// *Action : Use Form Builder to do one of the following:
//	     --- recreate the information in the
//	     item's Comment property as it was generated
//	     --- delete the contents of the item's Comment property
//	     to enable Form Generator to capture the item without
//	     using the information in the Comment property
01107,1, "%s can only be displayed as IMAGE or OLE CONTAINER"
// *Cause :  The only valid usage of a LONG RAW column is to display it as
//	     an IMAGE or OLE CONTAINER.
// *Action : Use IMAGE or OLE CONTAINER as the Display Datatype of this Item
//	     in the Repository.
01108,1, "ROWLOV preference ignored; LOV missing items for primary key columns"
// *Cause :  To generate row LOV functionality when ROWLOV is
//	     set to Yes, the repository LOV definition must include
//	     all primary key columns of the base table. Form Generator
//	     has detected that not all primary key columns are included
//	     as items in the repository LOV base table usage.
// *Action : Include the missing primary key columns as items
//	     in the repository LOV base table usage.
01109,3, "No functions found for flavor %d"
// *Cause :  This is an internal error message not normally issued.
// *Action : Contact your Customer Support representative.
01110,1, "Default value of column %s.%s not used because column is auto-generated."
// *Cause :  A column definition in the Repository has been defined as both
//	     having a default value, and as having its value derived from a
//	     unique source. In this situation, Form Generator ignores the
//	     default value.
// *Action : No action required.  To avoid this warning in future executions
//	     of Form Generator, remove the default value from the column
//	     definition in the Repository.
01111,1, "Unique ID generated column %s.%s is not in any primary or unique keys."
// *Cause :  A column is defined in the Repository as having its value
//	     derived from a unique source, but that column is not
//	     included in any of its table's Unique or Primary keys.
// *Action : This warning is simply highlighting an area of the design in the
//	     Repository that does not seem correct. Generation of the current
//	     module is not affected.
01112,1, "ROWLOV preference ignored; cannot find corresponding module component"
// *Cause :  To generate row LOV functionality when ROWLOV is
//	     set to Yes, both of the following conditions must be met:
//	     --- the repository LOV definition must have the same
//	     name as the queryable module component with which it is
//	     to be associated
//	     --- the repository LOV definition must have the same base table
//	     usage as the module component with the same name
//	     Form Generator cannot find a suitable module component to associate
//	     with the repository LOV definition.
// *Action : Do the following:
//	     --- make sure the repository LOV definition has the
//	     same name as the module component it is to be
//	     associated with
//	     --- make sure the module component is queryable
//	     and that the repository LOV has the same base table usage
01113,2, "Failed to create List-of-Values"
// *Cause :  Oracle Form Generator was unable to
//	     create the list-of-values as defined within
//	     Designer.	The most common reasons for
//	     this are:
//	     Invalid SQL in LOVs where clauses
//	     The tables used by the LOV do not
//	     exist in the schema Form Generator is
//	     being run against.
// *Action : Either correct the SQL or create the tables in
//	     the schema.
01114,2, "The .fmx file cannot be saved"
// *Cause :  The .fmx file may have been successfully compiled, but Form
//	     Generator cannot save the compiled file. One possible
//	     reason is that the form is already running.
// *Action : If an older version of the form is already running, close the
//	     running form and generate the module again.
//	     Otherwise, examine the drive for other reasons why Form
//	     Generator cannot save the compiled file.
01115,1, "Format mask '%s' is not Year 2000 Compliant"
// *Cause :  The format mask you have specified is not Year 2000 compliant
//	     because it does not include the century.
// *Action : To make the format mask Year 2000 compliant, change the format
//	     mask to include the century.
01116,1, "OLBLST specifies object library objects but no object library is used"
// *Cause :  The OLBLST preference specifies objects
//	     and/or object groups to subclass or copy into the generated form
//	     from one or more object libraries. However, Form Generator is not
//	     using any object libraries during generation. Therefore the
//	     objects specified by OLBLST cannot be included in the
//	     generated form.
// *Action : To subclass or copy objects and/or object groups specified by
//	     OLBLST into the generated form, indicate the object libraries to use
//	     during generation in one of the following ways:
//	     --- by setting the STOOLB preference
//	     --- by specifying object libraries on the Generate Form dialog box
01117,2, "Invalid display type used in LOV column %s.%s"
// *Cause :  The display type of the specified item is not a
//	     valid type for use in LOVs. For example, the
//	     display type is set to 'image'
// *Action : Either remove this item from the LOV, or change its
//	     display type to a valid value.
01118,1, "List item %s, implied by program unit %s, not found in form"
// *Cause :  The name of the specified program unit implies
//	     that there is a list item to be captured.
//	     However, Form Generator cannot find the item
//	     named in the program unit.
// *Action : Do one of the following:
//	     --- if you wish to capture a list item and
//	     associated LOV add an appropriately
//	     named list item to the form.
//	     --- if you do not wish to capture a list
//	     item and LOV, then remove the
//	     program unit and any references to it
01119,1, "Base table %s of block %s has no primary or unique keys"
// *Cause :  A table that has no Unique or Primary key is being used in this
//	     module to create or update records.
// *Action : No action is required. This warning is highlighting an area
//	     in the database design that does not seem correct.
//	     Generation of the current module is not
//	     affected.
01120,1, "Program unit %s does not contain SELECT statement for list item"
// *Cause :  The name of the specified program unit
//	     implies that it is used for populating list
//	     items. However, Form Generator cannot
//	     find the expected SELECT statement in
//	     the program unit.
// *Action : Do one of the following:
//	     --- remove the program unit
//	     and any references to it from the form
//	     --- modify the format of the
//	     program unit to match that of other
//	     generated CGLL$ program units
01121,1, "LOV %s is a row LOV, so make sure ROWLOV=Yes"
// *Cause :  The name of the specified LOV implies
//	     that it was generated to support row LOV
//	     functionality. This type of functionality is
//	     only generated when the ROWLOV
//	     preference is set ot Yes.
// *Action : If you intend to generate from the
//	     captured module, set the ROWLOV
//	     preference to Yes for the captured LOV.
01122,1, "Item format mask %s cannot be validated against column definition"
// *Cause :  Form Generator cannot confirm that the specified item format
//	     mask is valid because the repository column definition on
//	     which this item is based does not have its Maximum Length
//	     and Decimal Places properties set.
// *Action : Add values to the repository column definition's Maximum
//	     Length and Decimal Places properties.
01123,2, "No Primary/Unique Key defined for Foreign Key %s of Table/View %s"
// *Cause :  A foreign key was defined to a
//	     table usage in the module with
//	     cascade update.  However the table
//	     has no primary or unique key constraint
//	     defined for the foreign key
// *Action : Create a unique key or a primary key for
//	     the table which is referenced by the foreign key
01124,1, "Missing columns in key %s in table %s in insert/update block"
// *Cause :  There are missing usages for one or more columns in the given
//	     unique or primary key, from a table usage in which Insert is
//	     allowed.
// *Action : This warning is simply highlighting an area of the design in the
//	     Repository that does not seem correct. Generation of the current
//	     module is not affected.
01125,3, "Connect string %s is not valid"
// *Cause :  The connect string specified on the Compile tab of the
//	     Form Generator Options dialog is not valid for one of
//	     the following reasons:
//	     --- the username, password, and/or database name
//		  are incorrect
//	     --- the database is not currently available
// *Action : Depending on the cause, either correct the
//	     connect string or start the database.
01126,4, "cflufl() called with no candidate items"
// *Cause :  This is an internal error message not normally issued.
// *Action : Contact your Customer Support representative.
01127,2, "Named routine '%s' is not valid"
// *Cause :  The specified named routine does not start with the correct
//	     PL/SQL keyword (i.e. FUNCTION, PROCEDURE,
//	     PACKAGE) for the named routine's type. For example,
//	     a named routine of type function must start with the
//	     keyword FUNCTION.
// *Action : To include the specified named routine in the
//	     generated module, add the correct PL/SQL keyword
//	     (i.e. one of FUNCTION, PROCEDURE, or
//	     PACKAGE).
//	     If you do not want to include the specified named routine
//	     in the generated module, do one of the following:
//	     --- delete the named routine from the repository
//	     --- exclude the named routine from generation
01128,1, "Ignoring CG$FF template item"
// *Cause :  CG$FF template items cause Form Generator to create
//	     calls to program units that are only created
//	     if the CALLFM preference is set to Yes.
// *Action : Do one of the following:
//	     --- set the CALLFM preference to Yes
//	     --- consider using navigation action items
//	     for inter-form navigation instead of obsolete
//	     CG$FF template items
01129,3, "Inverted master-detail key-based links are not supported"
// *Cause :  Form Generator has detected an inverted
//	     master-detail key-based link between module
//	     components. Inverted master-detail links
//	     are not supported by this version
//	     of Form Generator.
// *Action : Modify the structure of the module to remove
//	     inverted master-detail key-based links.
01130,2, "Template form and form being preserved use different coordinate systems"
// *Cause :  Form Generator has detected that the template form
//	     and the form being preserved use different coordinate
//	     system information. The layout of the generated form
//	     will be unsatisfactory.
// *Action : Make the coordinate system information identical
//	     by changing either the template form or the form being
//	     preserved.
01131,2, "Recursion found in referential integrity rules (foreign key %s on table %s)"
// *Cause :  The cascade delete/update rules specified on the foreign key
//	     definition(s) in the Repository have an infinite loop.  You will
//	     get this, for example if you have a foreign key from one table to
//	     itself, where the cascade delete rule is set to Cascade.
// *Action : Redefine the foreign key definition(s) such that recursion does
//	     not exist;  typically this will be changing the cascade
//	     delete/update rule from Cascade to Restricted
01132,2, "Updateable view-based module component is missing primary key items"
// *Cause :  The named module component has been defined as updateable
//	     or deleteable and based on a view. Since views do not necessarily
//	     support ROWIDs, records to be updated or deleted within a view
//	     must be identified by their primary key items. However, not all of
//	     the view's primary key columns have repository items bound to them
//	     in the base table usage. Form Generator is therefore unable to
//	     proceed with generation.
// *Action : Make sure that an item exists in the base table usage
//	     of the module component for every column in the
//	     view's primary key.
01133,2, "Cannot journal table %s;  no usages for entire primary key"
// *Cause :  The table specified is defined in the Repository as being
//	     journaled, but either the table has no primary key, or not all
//	     columns in the primary key are being used in this module.
//	     A journaled table must have a non-updateable primary key.
// *Action : Define a primary key for your table and/or ensure that the
//	     module definition includes items for all columns
//	     in the primary key.
01134,2, "Cannot journal table %s;  primary key item(s) updateable"
// *Cause :  The table specified is defined in the Repository as being
//	     journaled, but its primary key is defined as being updateable.
//	     Because the primary key identifies the row in the journal table,
//	     it may not be updateable.
// *Action : Modify the primary key definition in the Repository to make it
//	     non-updateable.
01135,2, "Updateable module component is based on a view that has no primary key"
// *Cause :  The named module component has been defined as updateable
//	     or deleteable and based on a view. Since views do not necessarily
//	     support ROWIDs, records to be updated or deleted within a view
//	     must be identified by their primary key items. However, no primary
//	     key has been defined for the view on which the module component
//	     is based. Form Generator is therefore unable to proceed with
//	     generation.
// *Action : Perform the following steps:
//	     1. Define a primary key for the view on which the
//	     module component is based.
//	     2. Make sure that an item exists in the base table usage
//	     for every column in the view's primary key.
01136,1, "Unable to refresh server-derived items from view after insert operation"
// *Cause :  The named module component has been defined as insertable
//	     and based on a view. Since views do not necessarily
//	     support ROWIDs, records within a view must be identified by their
//	     primary key items. However, Form Generator has determined that
//	     primary key values of inserted records will not be available to the
//	     generated form for one of the following reasons:
//	     --- no primary key has been defined for the view
//	     --- one or more of the view's primary key columns do not have
//	     items bound to them in the module component
//	     --- one or more of the items bound to the primary key columns of
//	     the view have their Server Derived? property set to Yes.
//	     This means that the generated form will be unable to retrieve
//	     inserted records from the database, and that server derived items
//	     in the record will remain unpopulated until the view is re-queried.
// *Action : If you want derived items to be populated
//	     automatically on insert, perform the following steps:
//	     1. Make sure a primary key is defined for the view
//	     on which the module component is based.
//	     2. Make sure that an item exists in the base table
//	     usage for every column in the view's primary key.
//	     3. Set the Server Derived? property to No on all items
//	     bound to primary key columns in the view.
01137,1, "No valid format mask found for date item"
// *Cause :  None of the format masks supplied for this item
//	     are valid.
// *Action : Provide a valid format mask in the item's format
//	     mask property, or in an appropriate object library
//	     item's format mask property, or in the appropriate
//	     TXTDDF or TXTDTF preferences.
01138,1, "Format mask '%s' taken from the object library is invalid, mask ignored: %s"
// *Cause :  The object library object that the item is
//	     subclassed/copied from has an invalid
//	     format mask.
// *Action : No action is required. To prevent this warning
//	     occuring in subsequent generation, ensure that
//	     the object library object that the item is subclassed
//	     from has a valid format mask.
01139,1, "No validation generated on partially specified foreign key %s.%s"
// *Cause :  The foreign key displayed has usages for some but not all of
//	     its columns, within the given table usage. Form Generator has
//	     not generated any code that will validate against this foreign
//	     key.
// *Action : This warning is simply highlighting an area of the design in the
//	     Repository that does not seem correct. Generation of the current
//	     module is not affected.
//	     to avoid this warning in future executions of Form Generator,
//	     include usages in the module definition for those columns that
//	     are missing.
01140,2, "Unable to layout form due to invalid relative tab stop settings"
// *Cause :  The generator has detected that there are inconsistent
//	     relative tab stop settings.  This could be because:
//	     --  end tab stops are set at a value less than the start tab
//	     stops on the same item
//	     -- items within item groups have relative	tab stops that
//	     would place them outside of the item group
//	     Therefore the canvas layout could not be determined
//	     and the form has not been generated.
// *Action : Correct the relative tab stop setting that is causing the problem
//	     and generate the form again.
01141,2, "Table usage %s requires primary key column for referential integrity"
// *Cause :  You have modelled a table usage which requires
//	     referential integrity code to be generated for it,
//	     but you have not included its primary key column.
// *Action : Add the primary key column to the table usage
//	     (this column need not be displayed or enabled).
01142,1, "Item datatype LOB in not valid in Forms 9i"
// *Cause :  Item datatype LOB is obsolete in Forms 9i
// *Action : Designer has defaulted the item datatype to LONG.
01143,1, "Item datatype FILE in not valid in Forms 9i"
// *Cause :  Item datatype FILE is obsolete in Forms 9i
// *Action : Designer has defaulted the item datatype to ALPHA
01145,2, "Template form %s does not exist"
// *Cause :  The generator cannot load the template form whose name is defined
//	     in the STFFMB preference.
// *Action : Log into Form Builder, and ensure that the form exists in
//	     the Form Builder database. If the owner of the form is not yourself,
//	     check that its owner has granted you access to it.
//	     Or ensure the template form exists in the file system.
01153,1, "Cannot derive value for column %s.%s with default value"
// *Cause :  A column is defined in the Repository as both being derived
//	     from an expression, and as having a default value.
// *Action : This warning is followed by a question asking if the default is
//	     not to be used.  Form Generator will then either not use the
//	     default value, or will not use the derivation expression.
01154,1, "Derivation expression ignored for unique id generated column %s.%s"
// *Cause :  A column is defined in the Repository as both being derived
//	     from an expression, and as being derived from a Unique ID source.
// *Action : No action required; the derivation is ignored.
//	     to avoid this warning in future executions of Form Generator,
//	     the column definition in the Repository should be amended
//	     accordingly.
01156,2, "Table %s has no primary key"
// *Cause :  The table specified is defined in the Repository as being
//	     journaled, but the table has no primary key.  Journaled tables
//	     must be given primary keys.
// *Action : Define a primary key for your table in the Repository, and ensure
//	     that there exists usages for all columns in the primary key in
//	     your module definition.
01157,1, "Foreign key item(s) in %s not enterable; those in lookup not a unique key"
// *Cause :  Form Generator has found the need to validate a foreign key.
//	     however, Form Generator has also determined from
//	     the lookup table usage's properties that none of the items
//	     forming part of the foreign key are to be generated as
//	     enterable (regardless of their Insert/Update/Query properties).
//	     Instead, validation code is to be generated for those lookup
//	     items that form a unique or primary key in the lookup table.
//	     If none of the lookup items form such a key, this message is issued
//	     and Form Generator generates code to perform validation across
//	     all the lookup items.
// *Action : No action is necessary. If this is not required
//	     behavior, change the properties of the lookup table
//	     usage.
01160,1, "Allowed value(s) of column bigger than item length"
// *Cause :  A column is defined in the Repository as having a list of valid
//	     values, and one or more of such values are bigger than the
//	     length of the corresponding item definition.
// *Action : This warning is simply highlighting an area of the design in the
//	     Repository that does not seem correct. Generation of the current
//	     module is not affected.
//	     to avoid this warning in future executions of Form Generator,
//	     investigate the maximum and minimum allowed values.
01170,2, "Foreign key from %s (in block %s based on %s)  in same arc as link to parent"
// *Cause :  Form Generator has recognized the need for validation against
//	     column(s) in a foreign key. However, the foreign key is in an arc
//	     with a second foreign key that has already been used to link this
//	     block back to a previous block, and this item is not updateable.
//	     Updating this item will therefore invalidate the arc
//	     unless the join to the parent is nullified
// *Action : Correct the module definition by removing the item(s) based
//	     on one or other of the foreign keys or make the join to the parent
//	     block updateable
01171,1, "Masters of block %s based on %s are linked via foreign keys in the same arc"
// *Cause :  This block is has two links back to previous blocks via two
//	     foreign keys that are in the same arc.
// *Action : This warning is highlighting an area in the module design that
//	     does not seem correct.  Generation of the current module is not
//	     affected.	No action is required.
01173,1, "Display datatype of item is inappropriate for column datatype"
// *Cause :  The display datatype recorded against the column usage is
//	     inappropriate for the column's actual datatype.  For example you
//	     will get this warning if you have a HIREDATE column of type DATE,
//	     which when used in a module has been given a display datatype of
//	     INT.
// *Action : Change the display datatype of the Column Usage to be something that
//	     corresponds to the actual datatype of the column.
01177,1, "No list of values form found for table %s"
// *Cause :  The user preference FKLOVT indicates that the list of values
//	     processing for foreign keys in the given table is to be supplied
//	     via modules defined in the Repository as being called by this
//	     module, and being of format 'LOV'.  No such modules can be found.
// *Action : Define such a module, or change the preference value.
01178,1, "All table usage flags will be updated to query only"
// *Cause :  The format of the current module is defined as 'LOV' which indicates
//	     that it is to be used to provide a list of valid values for a
//	     foreign key in another module.  One or more of the detailed
//	     table usages in the current module have usage flags other than
//	     'Select' set.  A List of Values form should be query only.
// *Action : You will be asked whether or not you wish to continue.
//	     If you choose to do so, Form Generator will update your detailed
//	     table usages to make them query only.
01182,2, "Lookup usages for non-enterable foreign key must be displayed"
// *Cause :  The foreign key is not enterable, and a lookup exists, and none of
//	     the lookup's items are displayed.
// *Action : Modify the module definition so that the foreign key is enterable,
//	     or the lookup items are displayed. If Form Generator
//	     has unset the Display properties of lookup items, and you have
//	     also set the Display in LOV property of the lookup item based on the
//	     primary key column(s) of the lookup table, unset the Display in LOV
//	     properties and set them on foreign key items in the base table.
01195,2, "Failed to compile .fmb into .fmx file for form module %s"
// *Cause :  The command to compile the .fmb file into a .fmx file has failed.
//	     Possible causes include:
//	     --- a problem in the .fmb file that has
//	     resulted in a compilation error
//	     --- a problem with your environment
//	     (e.g. you might have the wrong version of Form Builder
//	     installed)
//	     --- an object (e.g. a table or view) required by the form might
//	     not exist in the database
// *Action : If compilation errors occurred during generation, Form Generator
//	     creates a log file detailing the problem. For more information
//	     about the	compilation error, view the log file from
//	     the Build Action dialog box.
01196,1, "Item has display length %d but format of length %d"
// *Cause :  An item of type DATE has a format mask that
//	     is of a different length to its display length.
// *Action : This warning is highlighting an area in the module design that
//	     does not seem correct.  Generation of the current module is not
//	     affected.	No action is required.
01197,1, "Item has an invalid date format '%s', mask ignored: %s"
// *Cause :  An item of type DATE has a format mask that
//	     is invalid.
// *Action : No action is required. To avoid this warning during
//	     further runs of Form Generator, change the mask on the item.
01198,1, "Auto-generated item %s.%s should not be enterable"
// *Cause :  A column is defined in the Repository as being auto-generated as
//	     'sequence within parent', but the item indicates
//	     that the resulting item should be made enterable.
// *Action : This warning is highlighting an area in the module design that
//	     does not seem correct.  Generation of the current module is not
//	     affected.	No action is required.	To avoid this warning in further
//	     runs of Form Generator, update the item in
//	     the Repository to unset the Insert and Update allowed flags.
01199,1, "Block based on table %s will have no queryable item"
// *Cause :  A table usage has the query allowed flag set, but none
//	     of its items have the associated flag set.
// *Action : Navigate to the table usage and set the query flag on the items
//	     you wish to allow the user to query in the form.
01203,1, "Invalid preference for date format %s"
// *Cause :  The preference for default mask for DATE items contains a value
//	     that is not a valid date mask.
// *Action : Change the value of the preference to either a valid mask, or null.
01204,2, "Table %s used as first block in LOV form is not referenced by other tables"
// *Cause :  You have defined a list of values form, based on the given table
//	     name, but there are no other tables that have foreign keys that
//	     go to this table.	It therefore makes no sense to have a list of
//	     values form based on this table, as no other tables will require
//	     a list based on this table.
// *Action : Change the module format from LOV, or define foreign keys that
//	     reference this table.
01223,4, "Message CGF-6815 must contain a '-'"
// *Cause :  The NLS message 6815 / utility CGF has been converted to a
//	     string that does not contain a hyphen.
//	     This is an internal error message not normally issued.
// *Action : Contact your Customer Support representative.
01224,2, "Column in key %s is optional"
// *Cause :  A column defined in the Repository as being optional is also
//	     defined as being in a primary key.  Form Generator assumes
//	     primary key columns are mandatory when generating SQL code that
//	     validates uniqueness, etc.
// *Action :
01227,1, "Invalid default value '%s' for %s.%s; default ignored"
// *Cause :  The table usage has a numeric display datatype, but the
//	     default value on the column definition is not numeric.
// *Action : This warning is highlighting an area in the design that
//	     does not seem correct.  Generation of the current module is not
//	     affected.	No action is required.
01228,1, "Default value '%s' not in range %s to %s"
// *Cause :  A numeric column has a default value that is outside the range
//	     specified in the allowed values/ranges for the column.
// *Action : This warning is highlighting an area in the database design that
//	     does not seem correct.  Generation of the current module is not
//	     affected.	No action is required.
01230,1, "Prompt for %s in %s is too long; truncated to 130 characters"
// *Cause :  The prompt specified against the item is longer
//	     than that permitted in this version of Form Generator.
// *Action : No action required; Form Generator automatically truncates the
//	     prompt.
01231,1, "Generated parameter %s has been truncated to 30 characters"
// *Cause :  A parameter for a form level procedure has been generated whose
//	     name is based on the name of an item in the module.  The
//	     resulting parameter name is longer than that allowed in PL/SQL.
// *Action : If you don't want the parameter to be truncated,
//	     rename the item so that when the value of the PARAMP preference is
//	     prefixed to it, the number of characters is less than 30.
01235,1, "Item %s.%s maximum length %d, this is different to the column length %d"
// *Cause :  An item in the form being generated has a length that is
//	     different from the maximum length of the column in the Repository.
// *Action : Modify the column definition so that the column maximum length
//	     matches the item length, or modify the item definition in
//	     Form Builder as appropriate.
01236,1, "Item %s.%s is %s, this is different to the column which is %s"
// *Cause :  An item in the form being generated is defined differently to
//	     the corresponding column definition.
// *Action : Modify either the item in the form using Form Builder to match
//	     the corresponding column definition or modify column definition
//	     to match the item.
01239,1, "Item %s.%s of type DATE, but pref WHTIME indicates time should be recorded"
// *Cause :  An item has a display datatype of date, but that
//	     column is used to record the Record Creation/Update date, and the
//	     preference WHTIME indicates that the time should be recorded as
//	     well as the date.
// *Action : Change the display datatype to DATETIME on the detailed column
//	     usage.
01241,2, "Cascade upd/del rule on fk %s not consistent with column properties"
// *Cause :  The cascade delete or update rule for the foreign key
//	     is either NULL or DEFAULT and a column in the key is mandatory.
// *Action : Either make the column optional or change the rule.
01242,1, "%s.%s enabled and navigable to allow scrolling on queried values"
// *Cause :  A column usage in a table usage that does not allow insert
//	     has been defined such that the display length is less than the
//	     actual length of the column. Form Generator has made the resultant
//	     item enabled and navigable to allow the user to scroll the queried
//	     value.
// *Action : No action required.
01246,1, "Query property has invalid WHERE clause:\n%s"
// *Cause :  The query where clause and any column ordering have been built
//	     into a WHERE clause for the block.  This has failed to parse.
// *Action : Correct the restrictive query condition held on the detailed
//	     table usage in the module definition.
01247,1, "Hidden or non-insertable item %s.%s is mandatory"
// *Cause :  The item is not displayed and is mandatory.  It is not auto-
//	     generated, that is it does not have a copy value, default,
//	     sequence, it is not a formula item and it is not auto-generated
//	     for journaling.
// *Action : Amend the item in the Repository to ensure
//	     that the item is made displayed and enterable.
01250,1, "Default value removed/modified on audit item %s"
// *Cause :  An audit column (i.e. Date Created/User Created/Date modified
//	     /User modified) is defined as having a default value.
//	     Form Generator will ignore the default value. values for the
//	     audit columns will be created during commit processing in the
//	     generated form.
// *Action : Correct the Repository column definition of the column
//	     indicated.
01251,1, "Column %s.%s not wide enough to hold username; must be CHAR(30)."
// *Cause :  An audit column has been defined with a maximum length that is
//	     insufficiently large to allow the storage of the audit data.
//	     the Form Generator will continue processing.
// *Action : Correct the Repository column definition of the column
//	     indicated. The column should have a minimum length of 30 characters.
01252,1, "Enterable audit item %s.%s updated to be non-enterable"
// *Cause :  An audit column has been defined as updateable in the current
//	     module. Form Generator has updated it to be non-enterable.
//	     Values for the audit columns will be created during commit
//	     processing in the generated form.
// *Action : Correct the Repository module column usage definition for
//	     the current module's usage of the column indicated.
01253,1, "Length of audit item %s.%s increased to %d"
// *Cause :  An audit column has been defined with a display length which is
//	     less than 30. Form Generator has increased the display length
//	     to the maximum length if the audit column.
// *Action : Correct the Repository column or module column usage
//	     definition for the column indicated.
01254,1, "Check constraint %s in table %s ignored; no base usages for column(s) %s"
// *Cause :  Form Generator is processing a table usage for a
//	     table that has a check constraint defined for it, and there
//	     exists items for some but not all of the
//	     columns mentioned in the constraint text.
// *Action : This warning is simply highlighting an area of the design in the
//	     Repository that does not seem correct. Generation of the current
//	     module is not affected. You may however wish to add usages for the
//	     missing columns.
01258,1, "Missing mandatory column %s in usage of table"
// *Cause :  The Usage of the given table has the Insert Allowed usage flag set,
//	     but there is no detailed usage of the given column, which is defined
//	     as being mandatory in the Repository.
// *Action : Add a detailed data usage of this column to the module definition
//	     in the Repository.
01261,1, "Module must be generated prior to loading help text"
// *Cause :  The utility to load up module level help text has been run for
//	     a module that has yet to be generated.
// *Action : Run Form Generator for that module prior to loading its help text.
01263,2, "User-defined condition (%s) has an error: %s"
// *Cause :  Form Generator has detected an error in a validation
//	     condition defined in the Repository against either
//	     a check constraint or a column on the database. Either an
//	     invalid condition has been entered in the Repository, or
//	     one or more of the tables/columns
//	     involved in the condition do not exist on the database.
// *Action : Correct the error in the Repository.
01264,2, "User-defined expression (%s) has an error: %s"
// *Cause :  A derivation expression defined in the Repository has a syntax
//	     error in it.
// *Action : Correct the error in the Repository.
01277,1, "Set Insert, Update, and/or Optional properties to No for non-base table item"
// *Cause :  Form Generator has detected that:
//	     --- the item is a non-base table item (either a
//	     lookup item or a formula item)
//	     --- the item has one or more of the Insert, Update,
//	     and/or Optional properties set to Yes
//	     Therefore, Form Generator has set the item's
//	     Insert, Update, and/or Optional properties to No
//	     during generation instead.
//	     Form Generator attempts to save (or proposes) this
//	     adjustment to the property to bring the module
//	     definition into line with the generated output.
// *Action : If adjustment saved, no action necessary (Form Generator has
//	     saved the change to the property).
//	     If adjustment proposed, browse/edit the proposed change
//	     before saving/discarding it.
//	     If adjustment failed, no action necessary (Form Generator is
//	     unable to save the change to the property).
//	     Hint: Define allowed operations for foreign key lookup items
//	     against the foreign key items in the base table usage
//	     (regardless of whether the base table items are displayed).
//	     Do not define allowed operations for formula items because
//	     the generated items are not enterable.
01280,1, "display length = %d, item length = %d;"
// *Cause :  The display length on the item is bigger than
//	     that which is computed to be used for the item length.
//	     Note, the item length is based on the column maximum length.
//	     If the underlying column type is numeric, the item length may
//	     be increased to allow space for a sign and decimal point.
// *Action : No action necessary.
01281,2, "Oracle Forms binary file for %s has NOT been created"
// *Cause :  An error occurred during the generation process, and consequently
//	     no Oracle Forms binary file has been created for this module.
// *Action : No action required.
01284,1, "Table %s doesn't exist \n"
// *Cause :  This message is used by the Form Generator utilities
//	     when the required table does not exist in the database.
// *Action : A question follows this warning which, if answered positively, will
//	     create the required table in the database. Answering negatively to
//	     the question will stop execution of the utility.
01288,1, "Check constraint on column %s.%s contains references to other columns."
// *Cause :  Check constraints specified against a column should contain
//	     only references to that column. Cross-column validation should be
//	     specified at the table level.
// *Action : The generated form will enforce the constraint. However, to
//	     prevent the warning appearing on subsequent generations of the
//	     form, specify the constraint at the table level
01291,1, "Code is already present against KEY-LISTVAL for %s.%s"
// *Cause :  The KEY-LISTVAL trigger already has code present.
//	     The new list of values code will be added as well.
// *Action : Check that the new list of values code does not duplicate the
//	     functionality of the existing code.
01295,1, "Set Display property to No because this lookup item based on column in join"
// *Cause :  Form Generator has detected that:
//	     --- the item is in a lookup table usage
//	     --- the item is based on a column that forms part of the
//	     join condition between the base table and the lookup table
//	     --- the item has the Display property set to Yes
//	     Therefore, Form Generator has set the item's
//	     Display property to No during generation instead.
//	     Form Generator attempts to save (or proposes) this
//	     adjustment to the property to bring the module
//	     definition into line with the generated output.
// *Action : If adjustment saved, no action necessary (Form Generator has
//	     saved the change to the property).
//	     If adjustment proposed, browse/edit the proposed change
//	     before saving/discarding it.
//	     If adjustment failed, no action necessary (Form Generator is
//	     unable to save the change to the property).
//	     Hint: To display the data from the lookup column, set the
//	     the corresponding base table column's Display property
//	     to Yes.
01298,2, "Primary/Unique key has a name that is not unique within %s chars"
// *Cause :  The primary or unique keys specified are not unique within
//	     the number of characters.	They must be unique, because they are
//	     used for naming and identifying objects in the generated code.
// *Action : Modify the Repository definitions to make them unique.
01299,2, "Table names %s and %s are not unique within %s characters"
// *Cause :  The table names as entered in the Repository are not unique
//	     within the specified number of characters.  They must be unique
//	     because they are used for naming and identifying objects
//	     in the generated code.
// *Action : Modify the Repository definitions to make them unique.
01312,4, "Following PL/SQL line %d chars too long\n%s"
// *Cause :  The length of a line of generated PL/SQL is
//	     greater than the value of the
//	     MAXPLS preference.
// *Action : Either reduce the length of generated PL/SQL lines
//	     to less than the value of MAXPLS, or increase the value of
//	     MAXPLS to greater than the length of the
//	     longest PL/SQL line to be generated.
01313,1, "Following PL/SQL statement cannot be split to fit onto a line\n%s"
// *Cause :  Form Generator cannot generate the form, because one of the
//	     generated lines of PL/SQL is too long, and it cannot be split
//	     sensibly into more than one line.
//	     The normal cause for such an error is in the data defined in the
//	     Repository or user preferences, such as a very long value for
//	     the ONMES preference without any embedded spaces.
// *Action : The line of PL/SQL displayed should indicate the data that is
//	     causing the problem.  This data should be modified appropriately.
//	     If the cause is not that as described above, then make a note of
//	     the exact text of the error message, and contact your Customer
//	     Support representative.
01314,3, "No linked-in function list for flavor %d."
// *Cause :  This is an internal error message not normally issued.
//	     Form Generator cannot find a linked-in list of functions defining
//	     the functionality of the given flavor.
// *Action : Contact your Customer Support representative.
01316,1, "Foreign key constraint %s in %s has no enterable items or lookups"
// *Cause :  Entry of the foreign value is required in this module,
//	     but none of the items associated with the foreign key (i.e. the
//	     base table items and associated lookup items) are enterable.
// *Action : Items should be added for the lookup table, to
//	     allow entry of the foreign key value.
01318,1, "Set Width property to %d to show format %s"
// *Cause :  Form Generator has detected that:
//	     --- the item has a format mask applied to it
//	     --- the item's maximum length is not large enough
//	     to display the specified format mask (and
//	     possibly a minus sign as well)
//	     --- the item's maximum length is derived from
//	     the item's Width property
//	     Therefore, Form Generator increases the item's
//	     Width property during generation.
//	     Form Generator attempts to save (or proposes) this
//	     adjustment to the property to bring the module
//	     definition into line with the generated output.
// *Action : If adjustment saved, no action necessary (Form Generator has
//	     saved the change to the property).
//	     If adjustment proposed, browse/edit the proposed change
//	     before saving/discarding it.
//	     If adjustment failed, no action necessary (Form Generator is
//	     unable to save the change to the property).
//	     Hint: If you do not want to increase the width of the item, do
//	     one of the following:
//	     --- reduce the characters in the format mask applied to the item
//	     --- if the format mask has exactly the same number of
//	     characters as the width and the
//	     column will only contain positive values, specify this by entering
//	     a low value of '0' (and a high value) against the column in the
//	     Repository. This will remove the possibility of the item
//	     having to display a minus sign, allowing the format to fit.
01319,1, "Usage format %s is invalid, not applied"
// *Cause :  The format defined against the item cannot be
//	     applied as an item format mask because it is invalid.
// *Action : This warning is highlighting an area in the module design that
//	     does not seem correct. Form Generator has ignored the format this
//	     run. To avoid the same warning in later runs, correct the format
//	     defined against the item.
01322,1, "Check constraint on column %s.%s ignored; no base usages for column(s) %s"
// *Cause :  Form Generator is processing an item for a column
//	     that has a check constraint defined for it, and there exists
//	     items for some but not all of the columns
//	     mentioned in the constraint text.
// *Action : This warning is simply highlighting an area of the design in the
//	     Repository that does not seem correct. Generation of the current
//	     module is not affected. You may however wish to add usages for this
//	     missing columns. Constraints involving cross_column validation are
//	     normally specified at table level rather than column level.
01325,1, "Form Builder module %s already exists"
// *Cause :  The Oracle Forms application being generated already exists in the
//	     database.
// *Action : You will be asked whether or not you wish to overwrite the existing
//	     Oracle Forms module. If this form has previously been generated
//	     and changes have been made via the Form Builder then these
//	     changes will be lost if you choose to overwrite.
//	     To avoid this question being asked on future runs of Form
//	     Generator you may set the ANOVRW preference to the answer required.
01326,2, "User cannot access tablespace: %s\n"
// *Cause :  The user has requested that one of the utility tables should be
//	     created in a tablespace to which the user has no resource
//	     privileges.
// *Action : Enter a tablespace to which the user has resource privileges or use
//	     the default tablespace.
01327,8, "Existing Oracle Forms module %s not overwritten"
// *Cause :  The existing Oracle Forms application has not been overwritten
//	     either because you answered 'No' when asked whether you wanted
//	     to overwrite it, or because the value of the ANOVRW preference was
//	     set to 'N'.
// *Action : No action is required.
01329,1, "Form Generator internal name %s not recognized"
// *Cause :  A PL/SQL comment line has been identified with an unknown
//	     Form Generator keyword.
//	     The most likely cause is that the text has been amended
//	     using Form Builder.
// *Action : The offending comment line should be removed from the form
//	     definition, or restored to its original state.
01333,1, "Usage format %s is shorter than max length %d"
// *Cause :  The format specified for the repository item produces a
//	     generated item whose Maximum Length property
//	     is less than the value specified for one of the following
//	     (in order of precedence):
//	     --- the repository column definition's Length property
//	     --- an object library source object's Maximum Length property
//	     --- the repository item's Display Length property
//	     --- the TXTDNL preference
// *Action : This warning is highlighting an area in the module design that
//	     does not seem correct.
//	     Form Generator has applied the format mask to the item, but to
//	     avoid the same warnings in later runs, modify either the format
//	     mask or one of the lengths mentioned above.
//	     For more information about the Maximum Length property,
//	     refer to the Designer online help system.
01334,1, "Set Query property to No because queries not allowed on LONG/LOB item"
// *Cause :  Form Generator has detected that:
//	     --- the item's Datatype property is set to LONG or LOB
//	     --- the item has the Query property set to Yes
//	     Therefore, Form Generator has set the item's
//	     Query property to No during generation instead.
//	     Form Generator attempts to save (or proposes) this
//	     adjustment to the property to bring the module
//	     definition into line with the generated output.
// *Action : If adjustment saved, no action necessary (Form Generator has
//	     saved the change to the property).
//	     If adjustment proposed, browse/edit the proposed change
//	     before saving/discarding it.
//	     If adjustment failed, no action necessary (Form Generator is
//	     unable to save the change to the property).
01337,2, "Unable to create forms object"
// *Cause :  The two most likely causes are that the memory has been exhausted
//	     or that the DE environment has been installed incorrectly.
// *Action : Check the memory available and the memory consumption of the
//	     other programs that may be running.
//	     Also check your environment by invoking Form Builder
//	     and verify that you can create and run forms.
//	     If the problem persists contact your Customer Support representative
01338,2, "Failed to load form %s"
// *Cause :  The form module currently being processed does not exist.
// *Action : Ensure that the form module that is being processed exist either
//	     in the file system or on the specified database.
01339,1, "Unable to generate check box; ranges exist in the valid values"
// *Cause :  The display datatype of the item is set to
//	     CHECK BOX, and the underlying column or its domain does not possess
//	     exactly one or two valid values.  If the column is mandatory, it
//	     must have exactly two allowed values. Ranges are not permitted.
// *Action : Ensure that the column that the item is based
//	     on (or its domain) has only one or two allowed values.  If only one
//	     allowed value is specified, ensure that the column is not
//	     mandatory, and that the nullify flag is set on the detailed
//	     column usage.  Note that ranges are not allowed for a domain
//	     when used as valid values for a check box.
01340,1, "Unable to generate radio group; valid values contain ranges."
// *Cause :  The display datatype of the item is set to
//	     RADIO GROUP, and the underlying column usage or its domain
//	     one or more ranges.
// *Action : Ensure that the column that the item is based
//	     on (or its domain) has a set of distinct values (not ranges).
//	     If only one allowed value is specified, ensure that the column is
//	     not mandatory, and that the nullify flag is set on the detailed
//	     column usage.  Note that ranges are not allowed for a domain
//	     when used as valid values for a radio group.
01341,1, "Radio group has too many buttons; %d valid values (max is %d)"
// *Cause :  The number of valid values defined for the underlying column for
//	     which the radio group is being generated (and therefore the
//	     number of generated buttons) is greater than the number specified
//	     in the butgrp preference.	note that if the item
//	     is defined a 'Nulls Allowed', then an extra button will be
//	     created to represent a NULL value.
// *Action : This warning is highlighting an unusual aspect of the end user
//	     interface to the generated form.  You may wish to change the
//	     display datatype for this item to something
//	     other than RADIO GROUP.
//	     To remove the warning during future generation either increase (or
//	     set to NULL) the value of the preference BUTGRP.
01342,2, "VGS function call failed in %s, at %s:%d"
// *Cause :  This is an internal error message not normally issued.
// *Action : Contact your Customer Support representative.
01343,2, "Display datatype '%s' for '%s.%s' not appropriate for derived values"
// *Cause :  This item or column is derived from one of the following:
//	     --- SQL Expression
//	     --- Client Side Function
//	     --- Server Side Function
//	     [lastlistitem]
//	     However, the display type for such an
//	     item or column is not allowed.
// *Action : Change the display type for this item or column to one of the
//	     following:
//	     --- text item
//	     --- check box
//	     --- list item
//	     --- radio group.
01352,1, "Set Placement property to %s because invalid in current context"
// *Cause :  Form Generator has detected that
//	     the module component has the Placement property set to
//	     a value that is not valid in the current context.
//	     Therefore, Form Generator has changed module component's
//	     Placement property as specified during generation.
//	     Form Generator attempts to save (or proposes) this
//	     adjustment to the property to bring the module
//	     definition into line with the generated output.
// *Action : If adjustment saved, no action necessary (Form Generator has
//	     saved the change to the property).
//	     If adjustment proposed, browse/edit the proposed change
//	     before saving/discarding it.
//	     If adjustment failed, no action necessary (Form Generator is
//	     unable to save the change to the property).
01354,2, "Invalid layout requirements found on usage of table"
// *Cause :  Generator has found one or more invalid layout requirements against
//	     the given table usage.
// *Action : This is an internal message that should not normally be issued. It
//	     suggests that corruption of data in the Repository has taken place.
01355,1, "Positive value for block indentation on content canvas ignored"
// *Cause :  The PAGBIN preference for block indentation on canvases contains a
//	     positive value, yet the preference PAGSTB indicates that block stubs
//	     should not be generated on canvases. Generator is unable to produce
//	     positive block indentation unless block stubs are generated.
// *Action : Change the value of the PAGSTB preference so that stubs are
//	     generated on canvases.
01356,1, "Positive value for block indentation on stacked canvas ignored"
// *Cause :  The POPBIN preference for block indentation on stacked canvases
//	     contains a positive value, yet the preference POPSTB indicates
//	     that block stubs should not be generated on canvases. Generator
//	     is unable to produce positive block indentation unless block stubs
//	     are generated.
// *Action : Change the value of the POPSTB preference so that stubs are
//	     generated on stacked canvases.
01357,1, "Unable to generate check box; mandatory column must have 2 values"
// *Cause :  The display datatype of the item is set to
//	     CHECK BOX, and the underlying column or its domain does not possess
//	     exactly one or two valid values.  If the column is mandatory, it
//	     must have exactly two allowed values. Ranges are not permitted.
// *Action : Ensure that the column that the item is based
//	     on (or its domain) has only one or two allowed values.  If only one
//	     allowed value is specified, ensure that the column is not
//	     mandatory, and that the nullify flag is set on the detailed
//	     column usage.  Note that ranges are not allowed for a domain
//	     when used as valid values for a check box.
01358,2, "Unable to generate check box; Optional column must have 1 value"
// *Cause :  The display datatype of the item is set to
//	     CHECK BOX, and the underlying column or its domain does not possess
//	     exactly one or two valid values.  If the column is mandatory, it
//	     must have exactly two allowed values. Ranges are not permitted.
// *Action : Ensure that the column that the item is based
//	     on (or its domain) has only one or two allowed values.  If only one
//	     allowed value is specified, ensure that the column is not
//	     mandatory, and that the nullify flag is set on the detailed
//	     column usage.  Note that ranges are not allowed for a domain
//	     when used as valid values for a check box.
01359,1, "Unable to generate radio group; No valid values"
// *Cause :  The display datatype of the item is set to
//	     RADIO GROUP, and the underlying column does not have any valid
//	     values defined.
// *Action : Ensure that the column that the item is based
//	     on (or its domain) has a set of distinct values (not ranges).
//	     If only one allowed value is specified, ensure that the column is
//	     not mandatory, and that the nullify flag is set on the detailed
//	     column usage.  Note that ranges are not allowed for a domain
//	     when used as valid values for a radio group.
01360,1, "Unable to generate list; No valid values"
// *Cause :  This column is not appropriate as a list item as neither valid
//	     values, nor a domain with valid values have been specified for
//	     the column.
// *Action : Either change the display type or provide some valid value.
01361,1, "Unable to generate list; ranges exist in the valid values"
// *Cause :  This column is not appropriate as a list item as the list of valid
//	     values contains one or more ranges
// *Action : Either change the display type or remove the ranges from the list
//	     of valid values
01362,1, "Popup list has too many values; %d valid values (maximum is %d)"
// *Cause :  Too many valid values have been specified.
//	     Note that if the column is optional, NULL counts as a valid value.
// *Action : Reduce the number of valid values for the column
//	     or Increase the maximum size of a pop up list (preference PLSMAX)
//	     or choose a different display data type
01363,1, "Text list has too many values; %d valid values (maximum is %d)"
// *Cause :  The number of valid values exceeds the maximum number of values
//	     allowed in a text list.
//	     Note that if the column is optional, NULL counts as a valid value.
// *Action : Reduce the number of valid values
//	     or increase the maximum number of valid values allowed
//	     (preference TLSMAX) or choose a different display data type.
01364,2, "Available width on %s %d (%d) less than minimum allowable width (%d)"
// *Cause :  The width available to Generator on the given canvas is
//	     less than the minimum width in which blocks can be laid out. The
//	     available width is dependent on the width of the canvas,
//	     the canvas margin, whether boxes are being generated or not,
//	     and, if boxes are being generated, the space taken up by boxes.
// *Action : Ensure that Generator has sufficient space for the layout of blocks
//	     on the given canvas by checking values for width taken from
//	     canvases in the template form, from information specified against
//	     a table usage in the Repository. Also check the values of the
//	     preferences PAGMAR or POPMAR.
01367,1, "Insert flag ignored for %s.%s"
// *Cause :  The item flags allow insert into this image.
//	     however, there is no mechanism for entering the image.
// *Action : Either remove the insert flag,
//	     or specify an image control item (Preference IMCTR1 = Y)
01368,1, "Insert flag ignored for file based image in %s.%s"
// *Cause :  The underlying column for the image is of type CHAR.
//	     Therefore the database holds the filename of a file containing the
//	     image. The Repository column usage indicates that INSERT
//	     is allowed.  However, the form does not have an item into which
//	     we can insert the filename, only the image is displayed
// *Action : Either remove the INSERT flag from the usage
//	     or display the image control item (preference IMCTR1 = YES)
01369,1, "Update flag ignored for file based image in %s.%s"
// *Cause :  The underlying column for the image is of type CHAR.
//	     Therefor the database holds the filename of a file containing the
//	     image. The Repository column usage indicates that UPDATE
//	     is allowed.  However, the form does not have an item into which
//	     we can UPDATE the filename, only the image is displayed
// *Action : Either remove the UPDATE flag from the usage
//	     or display the image control item (preference IMCTR1 = YES)
01370,1, "Delete flag ignored for file based image in %s.%s"
// *Cause :  The underlying column for the image is of type CHAR.
//	     Therefor the database holds the filename of a file containing the
//	     image. The Repository column usage indicates that DELETE
//	     is allowed.  However, the form does not have an item where
//	     we can DELETE the filename, only the image is displayed.
// *Action : Either remove the DELETE flag from the usage
//	     or display the image control item (preference IMCTR1 = YES)
01371,2, "IMAGE item is based on an invalid column datatype  - %s.%s"
// *Cause :  The underlying column for an IMAGE display type is neither a
//	     LONG RAW, BLOB, BFILE nor a VARCHAR2
//	     If the underlying column type is LONG RAWor BLOB, the
//	     image is held on the database.  If the underlying column type
//	     is BFILE or VARCHAR2 the name of a file holding the image
//	     is held on the database. The generator cannot handle any
//	     other underlying column type.
// *Action : Reconsider displaying this column as an image.
01373,2, "Unable to attach library %s"
// *Cause :  Form Generator could not find one or more PLL files to
//	     attach to the generated form/menu.
//	     If the PLL file corresponds to a Repository library module
//	     attached to the form/menu by a module network link,
//	     Form Generator searched the following in turn:
//	     --- the path specified by the appropriate Oracle Forms
//	     Registry variable (e.g. FORMS60_PATH)
//	     ---  if the attached library module is repository-based, the
//	     path specified by the current Library Generator PLL file
//	     location option
//	     ---  if the attached library module is file-based, the path
//	     specified by the library module's Source Pathname property
//	     [lastlistitem]
//	     If the PLL file does not correspond to a Repository library
//	     module attached to the form/menu by a module network
//	     link (i.e. the PLL file is one of the libraries shipped with
//	     Form Generator, or is specified by the MODLIB preference,
//	     or is attached to a template), Form Generator searched the
//	     following locations in turn:
//	     --- the Form Generator PLL file location option (if set)
//	     --- the path specified by the appropriate Oracle Forms Registry
//	     variable (only searched if the Form Generator PLL file
//	     location option is not set)
//	     [lastlistitem]
// *Action : We recommend you include the location of the
//	     library file in the appropriate Oracle Forms Registry
//	     variable (e.g. FORMS60_PATH).
//	     Alternatively, you can hard code the location into the
//	     generated form/menu by specifying the location in
//	     one of the following:
//	     --- the Library Generator PLL file location option for
//	     attached Repository-based library modules
//	     --- the Source Path Name property of attached file-based
//	     library modules
//	     --- the Form Generator PLL file location option for library
//	     files supplied with Form Generator
//	     [lastlistitem]
//	     Note that a hard coded library location makes a generated
//	     application significantly less portable than if the location is
//	     specified using Registry variables.
01376,2, "Cannot delete form  application %s"
// *Cause :  An ORACLE error occurred when attempting to delete a form from the
//	     database. The ORACLE error message is displayed immediately after
//	     this message.
// *Action : Refer to the "ORACLE Error and Codes Messages Manual" for a
//	     full description of the ORACLE error, its cause, and the action
//	     you should take.
01377,2, "Failed to write form %s"
// *Cause :  An ORACLE database or Oracle Forms error occurred when
//	     attempting to write the form. The text of the message is
//	     displayed immediately after this message.
// *Action : Refer to either the "ORACLE Error and Codes Messages Manual" or
//	     "Oracle Forms Reference Manual" for a full description of the error,
//	     its cause, and the action you should take.
01378,1, "Invalid placement '%s'"
// *Cause :  The table usage on which the block is based has a
//	     layout position which is invalid in the current context.
// *Action : If there is more than one valid alternative layout position then
//	     you will be asked to select from a list of more appropriate ones.
//	     Otherwise, the layout position will be changed to the one valid
//	     alternative available.
01379,1, "Block %s : Cannot fit a complete row on any canvases"
// *Cause :  One of the following:
//	     --- There is no room on any canvas for Generator to fit a
//	     complete row of the given block. This could be due to a combination
//	     of factors including canvas sizes being too small, canvas
//	     expansion being prevented, requirements for large headers/footers
//	     as specified in preferences or in the template form, or various
//	     layout preferences either decreasing the space available to
//	     Generator, or increasing the amount of space required by generated
//	     objects.
//	     --- The block does not contain any displayed items.
// *Action : If the block does not contain any displayed items,
//	     consider if this is really what you want.
//	     Otherwise,
//	     Increase canvas sizes by modifying preferences and/or increasing
//	     canvas sizes specified against table usages and/or
//	     reducing the size of header/footer objects by modifying preferences
//	     or canvases in the template form.
01380,2, "'%s' is not a valid layout position"
// *Cause :  The user was prompted with list of valid layout positions
//	     for a block.
//	     An invalid layout position has been chosen.
// *Action : Choose a valid layout.
01381,1, "Set Displayed Rows property to %d because of limited space"
// *Cause :  Form Generator has detected that:
//	     --- a certain maximum number of rows can be displayed
//	     --- the module component has the Displayed Rows property
//	     set to a value greater than the maximum number of rows
//	     that can be displayed
//	     Therefore, Form Generator reduces the module component's
//	     Displayed Rows property to the maximum number
//	     during generation.
//	     Form Generator attempts to save (or proposes) this
//	     adjustment to the property to bring the module
//	     definition into line with the generated output.
// *Action : If adjustment saved, no action necessary (Form Generator has
//	     saved the change to the property).
//	     If adjustment proposed, browse/edit the proposed change
//	     before saving/discarding it.
//	     If adjustment failed, no action necessary (Form Generator is
//	     unable to save the change to the property).
//	     Hint: If you do not want to reduce the number of rows displayed,
//	     consider some or all of the following options:
//	     --- increase canvas sizes by modifying preferences
//	     --- increase canvas sizes specified against module components
//	     --- reduce the size of header/footer objects in the template form
01382,1, "Expanding %s %d to fit %d row(s)"
// *Cause :  Generator will expand the given canvas in order to fit the
//	     requested number of rows.
// *Action : No action is necessary.
01384,1, "Block will span multiple canvases (starting on %s %d)"
// *Cause :  Generator has insufficient room on the current canvas to fit
//	     a complete row of the block. The block will therefore be spread
//	     across one or more canvases (starting on the given canvas).
// *Action : No action is necessary. If this situation is undesirable, consider
//	     providing more space on the canvas by changing preference
//	     values, table usage values and/or dimensions of canvases
//	     in the template form. Alternatively, allow Generator to expand
//	     canvases by setting the PAGEXP/POPEXP preferences to 'Y'.
01385,2, "Data Block  %s: Can no longer fit a complete row on %s %d"
// *Cause :  As only 1 row of the given block will be displayed and the ITMPAS
//	     preference indicates that prompts cannot be displayed over items
//	     in a single-row block, Generator has re-laid out the block taking
//	     this restriction into account. Now, however, the one row cannot be
//	     fitted into the space available.
// *Action : Consider increasing the size of the canvas on which you wish
//	     the given block to be displayed. Alternatively, allow the canvas
//	     to expand by setting the PAGEXP/POPEXP preference to 'Y'.
01387,1, "Database trigger required on table %s to validate arc number %d"
// *Cause :  All foreign keys in the table and arc number specified are enforced
//	     in the server only, however, the server cannot enforce an arc
//	     declaratively.
// *Action : Write a database trigger on the table to ensure that not more than
//	     one of the foreign keys has a value, and if the arc is mandatory
//	     that there is always one foreign key with a value.
01390,1, "Editor %s specified by preference %s is not defined in template form"
// *Cause :  One of the default editor preferences DFTCED or DFTLED contains
//	     the name of an editor that cannot be found in the current template
//	     form used during generation.
// *Action : Ensure that any user defined editor name as specified by one of
//	     the default editor preferences DFTCED or DFTLED is defined in the
//	     template form used during generation
01398,2, "Cannot link blocks based on tables %s and %s. FK %s references optional cols"
// *Cause :  The foreign key in the first table does not refer to a unique or
//	     primary key in the second, and not all columns in the foreign key
//	     map to mandatory columns in the referenced table.
// *Action : Modify the module definition such that the tables are linked by a
//	     foreign key which maps onto a unique or primary key, or make one of
//	     referenced columns mandatory.
01399,2, "Cannot link blocks based on tables %s and %s. FK %s references opt key %s"
// *Cause :  You are attempting to link two blocks via a foreign key which
//	     maps onto an optional unique key.
// *Action : Make the unique key mandatory.
01400,2, "Cannot manage canvases where block %s spread over multiple canvases"
// *Cause :  The specified block is spread over more than one canvas which
//	     cannot be managed.
// *Action : Modify the canvas attribute of the items in the block so that they
//	     all lie on the same canvas.
01401,1, "Foreign key %s in table %s does not reference a unique or primary key"
// *Cause :  The specified foreign key, which is enforced in the server only,
//	     does not map onto a primary or unique key.  This message
//	     should not normally be given as a foreign key declared in the
//	     server must map onto a unique or primary key.
// *Action : Contact your Customer Support representative.
01402,2, "Cannot link blocks based on tables %s and %s. FK %s does not reference UK/PK"
// *Cause :  You are attempting to link two blocks via a foreign key which does
//	     not reference a unique or primary key in the master block.
// *Action : Modify the module definition so that the foreign key maps onto a
//	     unique or primary key.
01404,2, "Stacked canvas %s has inappropriate name"
// *Cause :  The canvas name starts "CG$PAGE".	This implies that the canvas
//	     is a canvas template.  Canvases are not stacked.
// *Action : Prefix stacked canvas names by "CG$STACKED"
01405,2, "Content canvas %s has inappropriate name"
// *Cause :  The canvas name prefix implies that it is a template for a
//	     stacked canvas. However is not stacked.
//	     Name prefixes which imply a stacked canvas are:
//	     "CG$POPUP", "CG$SPREAD_TABLE", "CG$SINGLE_AREA" and "CG$OVERFLOW".
// *Action : Rename the canvas.
01406,1, "Require DB constraint to ensure all columns not null for mandatory key %s"
// *Cause :  There is a constraint which is mandatory and enforced by the Server
//	     only, but all its columns are optional.
// *Action : One of the following:
//	     --- Write a database constraint (i.e. table level check constraint)
//	     to ensure that not all columns are null (if null is a valid value)
//	     --- Modify the definition of at least one of the
//	     columns in the constraint to make it mandatory.
01407,1, "Item has no valid values, cannot be displayed as a GUI item"
// *Cause :  The item display datatype specifies this as a GUI item
//	     (i.e. RADIO GROUP, CHECK BOX, POP-LIST or T-LIST).
//	     However, GUI items can be generated only when the column
//	     has known valid values.  Neither domain nor column validation
//	     has been specified.
// *Action : Add column validation to the column specification in the
//	     CASE the Repository.
01408,2, "Limit of %s canvas sequence numbers reached"
// *Cause :  This is an internal error message not normally issued. The Generator
//	     has run out of internal sequence numbers to allocate to canvases
//	     of the given type.
// *Action : Contact your Customer Support representative.
01409,2, "Limit of %s window sequence numbers reached"
// *Cause :  This is an internal error message not normally issued. The Generator
//	     has run out of internal sequence numbers to allocate to windows
//	     of the given type.
// *Action : Contact your Customer Support representative.
01410,2, "Function call used in a condition (%s) is invalid: %s"
// *Cause :  The function specified as the validation condition defined in the
//	     Repository against either a check constraint or a column is
//	     invalid. This may have been caused by a syntax error or one of
//	     the columns used as arguments to the function does not exist in the
//	     current table.
// *Action : Correct the text in the Repository
01411,2, "Invalid function name"
// *Cause :  The function specified as a derivation or a condition does not have
//	     a valid name.
// *Action : Check the validation and derivation code held against the detailed
//	     table usages, the columns and the tables.
//	     Remove or correct the text.
01412,1, "Derivation expression ignored for LONG RAW, BLOB or BFILE column %s.%s"
// *Cause :  A usage of a LONG RAW, BLOB or BFILE column cannot be
//	     derived from an expression.
// *Action : No action required; the derivation is ignored.
//	     To avoid this warning in future executions of Form Generator,
//	     the derivation should be removed from the column definition in the
//	     Repository.
01413,1, "Display datatype IMAGE for '%s.%s' not appropriate for lookup items"
// *Cause :  A column of type CHAR or VARCHAR2 has a display datatype of
//	     IMAGE specified on the item.
// *Action : No action required; the column is displayed as a CHAR
01414,2, "%s is not an appropriate type for lookup item usage"
// *Cause :  A column with a lookup usage is of type LONG.
//	     Oracle Forms record group columns must have a length in the
//	     range 1 - 255, a LONG RAW is not appropriate.
// *Action : Remove this column from the lookup.
01424,1, "Column datatype mismatch between tables %s and %s for foreign key %s"
// *Cause :  The data types of at least one pair of corresponding columns in the
//	     foreign key and the unique/primary key onto which it maps are
//	     different.
// *Action : If this is not required, modify the data type of one of the columns.
01425,1, "The datatype CHAR is not suitable in an Oracle 7 database"
// *Cause :  This is an integrity check on the Repository.
//	     The datatype CHAR is not suitable in an Oracle 7 database
//	     for most purposes.
// *Action : Use the datatype VARCHAR2 instead.
01427,1, "FK %s considered mandatory in order to link blocks based on tables %s and %s"
// *Cause :  The optional foreign key which is specified to link the two blocks
//	     will be considered mandatory in this context.  That is, any records
//	     entered in the detail block must reference a record in the master.
//	     This will not affect the functionality of the module.
// *Action : No action required.
01429,1, "Increase Width property by %d to show check box indicator"
// *Cause :  Form Generator has detected that:
//	     --- the item has the Display Type property set to Check box
//	     --- the Width property of the item is too small
//	     to display the check box indicator
//	     Therefore, Form Generator increases the item's
//	     Width property during generation.
//	     Form Generator attempts to save (or proposes) this
//	     adjustment to the property to bring the module
//	     definition into line with the generated output.
// *Action : If adjustment saved, no action necessary (Form Generator has
//	     saved the change to the property).
//	     If adjustment proposed, browse/edit the proposed change
//	     before saving/discarding it.
//	     If adjustment failed, no action necessary (Form Generator is
//	     unable to save the change to the property).
01430,1, "Set Height property to %d to show check box indicator"
// *Cause :  Form Generator has detected that:
//	     --- the item has the Display Type property set to Check box
//	     --- the Height property of the item is too small
//	     to display the check box indicator
//	     Therefore, Form Generator increases the item's
//	     Height property during generation.
//	     Form Generator attempts to save (or proposes) this
//	     adjustment to the property to bring the module
//	     definition into line with the generated output.
// *Action : If adjustment saved, no action necessary (Form Generator has
//	     saved the change to the property).
//	     If adjustment proposed, browse/edit the proposed change
//	     before saving/discarding it.
//	     If adjustment failed, no action necessary (Form Generator is
//	     unable to save the change to the property).
01431,1, "Increase Width property by %d to show radio button indicator"
// *Cause :  Form Generator has detected that:
//	     --- the item has the Display Type property set to Radio
//	     Group
//	     --- the Width property of the item is too small
//	     to display the radio button indicator
//	     Therefore, Form Generator increases the item's
//	     Width property during generation.
//	     Form Generator attempts to save (or proposes) this
//	     adjustment to the property to bring the module
//	     definition into line with the generated output.
// *Action : If adjustment saved, no action necessary (Form Generator has
//	     saved the change to the property).
//	     If adjustment proposed, browse/edit the proposed change
//	     before saving/discarding it.
//	     If adjustment failed, no action necessary (Form Generator is
//	     unable to save the change to the property).
01432,1, "Set Height property to %d to show radio button indicator"
// *Cause :  Form Generator has detected that:
//	     --- the item has the Display Type property set to Radio
//	     Group
//	     --- the Height property of the item is too small
//	     to display the radio button indicator
//	     Therefore, Form Generator increases the item's
//	     Height property during generation.
//	     Form Generator attempts to save (or proposes) this
//	     adjustment to the property to bring the module
//	     definition into line with the generated output.
// *Action : If adjustment saved, no action necessary (Form Generator has
//	     saved the change to the property).
//	     If adjustment proposed, browse/edit the proposed change
//	     before saving/discarding it.
//	     If adjustment failed, no action necessary (Form Generator is
//	     unable to save the change to the property).
01433,1, "Increase Width property by %d to show pop list indicator"
// *Cause :  Form Generator has detected that:
//	     --- the item has the Display Type property set to Pop
//	     list
//	     --- the Width property of the item is too small
//	     to display the radio button indicator
//	     Therefore, Form Generator increases the item's
//	     Width property during generation.
//	     Form Generator attempts to save (or proposes) this
//	     adjustment to the property to bring the module
//	     definition into line with the generated output.
// *Action : If adjustment saved, no action necessary (Form Generator has
//	     saved the change to the property).
//	     If adjustment proposed, browse/edit the proposed change
//	     before saving/discarding it.
//	     If adjustment failed, no action necessary (Form Generator is
//	     unable to save the change to the property).
01434,1, "Increase Width property by %d to show text list vertical scroll bar"
// *Cause :  Form Generator has detected that:
//	     --- the item has the Display Type property set to Text
//	     list
//	     --- the Width property of the item is too small
//	     to display the vertical scroll bar
//	     Therefore, Form Generator increases the item's
//	     Width property during generation.
//	     Form Generator attempts to save (or proposes) this
//	     adjustment to the property to bring the module
//	     definition into line with the generated output.
// *Action : If adjustment saved, no action necessary (Form Generator has
//	     saved the change to the property).
//	     If adjustment proposed, browse/edit the proposed change
//	     before saving/discarding it.
//	     If adjustment failed, no action necessary (Form Generator is
//	     unable to save the change to the property).
01435,1, "Set Height property to %d to show pop list indicator"
// *Cause :  Form Generator has detected that:
//	     --- the item has the Display Type property set to Pop
//	     list
//	     --- the Height property of the item is too small
//	     to display the pop list indicator
//	     Therefore, Form Generator increases the item's
//	     Height property during generation.
//	     Form Generator attempts to save (or proposes) this
//	     adjustment to the property to bring the module
//	     definition into line with the generated output.
// *Action : If adjustment saved, no action necessary (Form Generator has
//	     saved the change to the property).
//	     If adjustment proposed, browse/edit the proposed change
//	     before saving/discarding it.
//	     If adjustment failed, no action necessary (Form Generator is
//	     unable to save the change to the property).
01436,1, "Increase Height property by %d to show text list horizontal scroll bar"
// *Cause :  Form Generator has detected that:
//	     --- the item has the Display Type property set to Text
//	     list
//	     --- the Height property of the item is too small
//	     to display the horizontal scroll bar
//	     Therefore, Form Generator increases the item's
//	     Height property during generation.
//	     Form Generator attempts to save (or proposes) this
//	     adjustment to the property to bring the module
//	     definition into line with the generated output.
// *Action : If adjustment saved, no action necessary (Form Generator has
//	     saved the change to the property).
//	     If adjustment proposed, browse/edit the proposed change
//	     before saving/discarding it.
//	     If adjustment failed, no action necessary (Form Generator is
//	     unable to save the change to the property).
01437,1, "Increase Width property by %d to show vertical scroll bar"
// *Cause :  Form Generator has detected that:
//	     --- the item is a multi-line text item
//	     --- the Width property of the item is too small
//	     to display a vertical scroll bar
//	     Therefore, Form Generator increases the item's
//	     Width property during generation.
//	     Form Generator attempts to save (or proposes) this
//	     adjustment to the property to bring the module
//	     definition into line with the generated output.
// *Action : If adjustment saved, no action necessary (Form Generator has
//	     saved the change to the property).
//	     If adjustment proposed, browse/edit the proposed change
//	     before saving/discarding it.
//	     If adjustment failed, no action necessary (Form Generator is
//	     unable to save the change to the property).
01438,1, "Increase Width property by %d to show vertical scroll bar"
// *Cause :  Form Generator has detected that:
//	     --- the item has the Display Type property set to Image
//	     --- the Width property of the item is too small
//	     to display the vertical scroll bar
//	     Therefore, Form Generator increases the item's
//	     Width property during generation.
//	     Form Generator attempts to save (or proposes) this
//	     adjustment to the property to bring the module
//	     definition into line with the generated output.
// *Action : If adjustment saved, no action necessary (Form Generator has
//	     saved the change to the property).
//	     If adjustment proposed, browse/edit the proposed change
//	     before saving/discarding it.
//	     If adjustment failed, no action necessary (Form Generator is
//	     unable to save the change to the property).
01439,1, "Increase Height property by %d to show horizontal scroll bar"
// *Cause :  Form Generator has detected that:
//	     --- the item has the Display Type property set to Image
//	     --- the Height property of the item is too small
//	     to display the horizontal scroll bar
//	     Therefore, Form Generator increases the item's
//	     Height property during generation.
//	     Form Generator attempts to save (or proposes) this
//	     adjustment to the property to bring the module
//	     definition into line with the generated output.
// *Action : If adjustment saved, no action necessary (Form Generator has
//	     saved the change to the property).
//	     If adjustment proposed, browse/edit the proposed change
//	     before saving/discarding it.
//	     If adjustment failed, no action necessary (Form Generator is
//	     unable to save the change to the property).
01442,2, "Cascade upd/del rule is Nullify for mandatory foreign key %s "
// *Cause :  You have specified that the referential integrity rule for either
//	     update, delete or both is nullify, but the foreign key is
//	     mandatory and therefore must contain a valid value.
// *Action : Update the foreign key definition to optional, or specify an
//	     alternative referential integrity rule.
01445,2, "Form has incompatible coordinate system"
// *Cause :  The form has a coordinate system that is incompatible with
//	     Form Generator. The form must use the character coordinate system
//	     with default font scaling.
// *Action : If the form is being generated, modify the template form so that
//	     it uses the character coordinate system with default font scaling.
//	     If the form is being generated, use Form Builder
//	     to change its coordinate system to character with default font
//	     scaling.
01446,1, "Not enough space to layout an LOV indicator next to %s.%s"
// *Cause :  The available width on the canvas is not enough to layout a
//	     list of values indicator button next to the item.	This item
//	     is laid out without a list of values indicator button.
//	     Note, the 'list of values' is available on the item.
// *Action : There are several possible courses of action:
//	     --- Do nothing, accept that this item does not have a list of values
//		 indicator button.
//	     --- Make the item display width smaller to allow space for the list
//		 of values indicator button.
//	     --- Increase the available width by making the canvas wider.
01450,2, "Function call used in a derivation (%s) is invalid: %s"
// *Cause :  The function specified as a derivation defined in the Repository
//	     against either a column or an item is invalid.
//	     This may have been caused by a syntax error or one of the columns
//	     used as arguments to the function do not exist in the current table
// *Action : Correct the text in the Repository
01451,1, "Cannot enforce '%s' rule declaratively in server.  Require triggers %s"
// *Cause :  The referential integrity rules (for delete and/or update) cannot
//	     be enforced declaratively on the server.
// *Action : Write data base triggers as detailed in the message to enforce the
//	     referential integrity and secondly, maintain the foreign key.
01455,1, "Client enforced %s constraint %s on table %s %s"
// *Cause :  Due to the delete/update referential integrity rule specified for
//	     the foreign key, there is a danger of the specified client-
//	     enforced constraint being violated.
// *Action : If possible, modify the constraint to be validated on the server.
01461,1, "Column validation on %s.%s %s"
// *Cause :  Due to the delete/update referential integrity rule specified for
//	     the foreign key, there is a danger of the column-level validation
//	     being violated.
// *Action : If possible, change the column level validation to a server-side
//	     table level check constraint.
01463,1, "'%c' is used for ITMSPM and ITMPPM"
// *Cause :  The same character has been specified (via the preferences)
//	     to indicate the item split prompt marker (ITMSPM) and the item
//	     post prompt marker (ITMPPM)
// *Action : Review why the same character has been chosen for each of these
//	     preferences.
01467,1, "Display datatype is TIME, this cannot take a format mask"
// *Cause :  The display datatype recorded in the item is
//	     TIME. It is not appropriate to apply a format mask to this
//	     item type. The format mask is removed.
// *Action : No further action is necessary.
01469,2, "Default value %s for %s in %s exceeds item length %ld"
// *Cause :  The default value length exceeds the item length.
//	     The default is ignored.
// *Action : Either increase the column size or choose a shorter default value.
01472,2, "Template form %s has incompatible coordinate system"
// *Cause :  The template form has a coordinate system that is incompatible with
//	     Form Generator. the template form must use the character
//	     coordinate system with default font scaling.
// *Action : Modify the template form so that it uses the character coordinate
//	     system with default font scaling.
01474,1, "Combo-box list style invalid"
// *Cause :  The generated form will allow values other than the valid value
//	     set to be entered into the form.
//	     The column definition in the Repository has not been flagged
//	     as containing a suggested set of values.
// *Action : No action is necessary, however you may care to review whether or
//	     not the valid values held against the Repository column definition
//	     are suggested values.
01475,1, "Combo-box has too many values; %d valid values (maximum is %d)"
// *Cause :  Too many valid values have been specified.
//	     Note that if the column is optional, NULL counts as a valid value
// *Action : Reduce the number of valid values for the column
//	     or increase the maximum size of a combo-box list (preference CLSMAX)
//	     or choose a different display data type
01476,1, "Increase Width property by %d to show combo box indicator"
// *Cause :  Form Generator has detected that:
//	     --- the item has the Display Type property set to Combo box
//	     --- the Width property of the item is too small
//	     to display the combo box indicator
//	     Therefore, Form Generator increases the item's
//	     Width property during generation.
//	     Form Generator attempts to save (or proposes) this
//	     adjustment to the property to bring the module
//	     definition into line with the generated output.
// *Action : If adjustment saved, no action necessary (Form Generator has
//	     saved the change to the property).
//	     If adjustment proposed, browse/edit the proposed change
//	     before saving/discarding it.
//	     If adjustment failed, no action necessary (Form Generator is
//	     unable to save the change to the property).
01477,1, "Set Height property to %d to show combo box indicator"
// *Cause :  Form Generator has detected that:
//	     --- the item has the Display Type property set to Combo box
//	     --- the Height property of the item is too small
//	     to display the combo box indicator
//	     Therefore, Form Generator increases the item's
//	     Height property during generation.
//	     Form Generator attempts to save (or proposes) this
//	     adjustment to the property to bring the module
//	     definition into line with the generated output.
// *Action : If adjustment saved, no action necessary (Form Generator has
//	     saved the change to the property).
//	     If adjustment proposed, browse/edit the proposed change
//	     before saving/discarding it.
//	     If adjustment failed, no action necessary (Form Generator is
//	     unable to save the change to the property).
01479,2, "OLE Container cannot be generated for %s.%s"
// *Cause :  The given item has a display datatype of
//	     OLE CONTAINER but the underlying column is not of type LONG RAW
//	     or BLOB.
// *Action : OLE containers can only be generated for items
//	     based on columns of type LONG RAW or BLOB since the value of an
//	     OLE Object is a byte-stream.
01480,1, "OLE Container Implementation %s for %s.%s not found"
// *Cause :  The given item has a display datatype of
//	     OLE CONTAINER but a Custom Item of type OLE Container named as
//	     its Implementation cannot be found in the template form.
// *Action : Ensure that the implementation for the item is the
//	     name of a Custom Item in the template form of type OLE Container
//	     that embodies a class definition for the OLE Container Custom Item.
//	     In the absence of such a definition Form Generator has
//	     created a 'vanilla' OLE Container Custom Item with default
//	     functional properties that will accept OLE Objects of any class.
01485,1, "Validation is ignored because column is server derived"
// *Cause :   A column is defined in the Repository as both having a list of
//	     valid values (or being a domain so defined), and as being derived
//	     by the server. In this situation, Form Generator ignores
//	     the valid values.
// *Action : This warning is simply highlighting an area of the design in the
//	     Repository that does not seem correct. Generation of the current
//	     module is not affected.
//	     to avoid this warning in future executions of Form Generator,
//	     modify the definition of the column in the Repository
//	     accordingly.
01486,1, "Column level check constraint ignored on server derived column %s.%s"
// *Cause :  A column is defined in the Repository as both having a column
//	     level check constraint and being derived by the server. In this
//	     situation, Form Generator ignores the constraint.
// *Action : This warning is simply highlighting an area of the design in the
//	     Repository that does not seem correct. Generation of the current
//	     module is not affected.
//	     to avoid this warning in future executions of Form Generator,
//	     modify the definition of the column in the Repository
//	     accordingly.
01487,1, "Column %s.%s is served derived: default ignored"
// *Cause :  A column that is defined as server derived also has a default
//	     defined. This default may be defined on the column definition or
//	     the item. In this situation Form
//	     Generator ignores the default.
// *Action : This warning is highlighting an area in the database design that
//	     does not seem correct.  Generation of the current module is not
//	     affected.
//	     To avoid this warning in future executions of Form Generator
//	     the column definition/item in the Repository
//	     should be amended accordingly.
01493,1, "Subclassed procedure found in template %s will not be included"
// *Cause :  Form Generator does not support the subclassing
//	     of procedures into the template form.
// *Action : Include the procedure in a library (.PLL)
//	     attached to the template form.
01494,1, "LOV button generated for mandatory item is mouse navigable"
// *Cause :  A button item generated to envoke an LOV for a
//	     mandatory item was generated from a template or
//	     object library object as mouse navigable.
// *Action : Set the 'Mouse Navigable' property of the source
//	     template or object library object to 'No'.
/
/ 03001 .. 04000 Menu generator Errors and Warnings
/
03001,1, "Custom substitution string '%s' needs manual implementation"
// *Cause :  Custom substitution strings (module arguments) in
//	     Menu Modules have no generator support in
//	     Designer 9i.
// *Action : You must add a code to support the substitution
//	     string, e.g. by creating and initialising a global
//	     variable instead.
03002,1, "No command line can be built for module %s. Menu  compilation will fail."
// *Cause :  The module command line or the MNUDFC or MNUDRC
//	     preferences are null.
// *Action : Set either the module command line or the preferences
//	     MNUDFC or MNUDRC.
03003,2, "Failed to create .mmx file for menu module %s"
// *Cause :  The command to compile the .mmb file into a .mmx file has failed.
//	     A possible cause is a problem in the .mmb file that has
//	     resulted in a compilation error.
//	     Alternatively, there might be a problem with your environment
//	     (e.g. you might have the wrong version of Form Builder
//	     installed).
// *Action : If compilation errors occurred during generation, Form Generator
//	     creates a log file detailing the problem. For more information
//	     about the	compilation error, view the log file from
//	     the Build Action dialog box.
03008,2, "Menu template %s not on template path"
// *Cause :  The specified menu template could not be found on the template
//	     path.
// *Action : Check your template path, menu template name and if the menu
//	     template exists.
03009,3, "Unable to generate unique substitution string"
// *Cause :  Too many parameters were specified to generate unique names for all
//	     of them.
// *Action : Try and reduce the number of parameters you require.
03010,6, "No menu modules to generate"
// *Cause :  No further information available.
// *Action :
03011,3, "Too many menus in the generated menu module"
// *Cause :  You have specified more modules of type MENU in the Repository
//	     than can be generated.
// *Action : Reduce the number of modules of type MENU that will be included
//	     in the generated menu module.
03014,3, "Command line for module %s is too long"
// *Cause :  The command line you have specified in the module definition is too
//	     long.
// *Action : Specify a shorter command line.
03016,3, "Invalid role name"
// *Cause :  A	group name you have specified is not appropriate for an
//	     Oracle Forms role.
// *Action : Change the group name appropriately.
03029,2, "Cannot find structure for role"
// *Cause :  This is an internal error message not normally issued.
// *Action : Contact your Customer Support representative.
03031,2, "Cannot delete menu module %s"
// *Cause :  This internal message should not normally be issued.
//	     The generator is attempting to delete the existing menu module
//	     from the database on which the Repository is also held.
// *Action : Contact your Customer Support Representative.
03032,2, "Failed to write menu module %s"
// *Cause :  The menu generator could not write out the binary file for the
//	     menu module that it has just generated.
// *Action : Investigate the reason given.
//	     Check that you have any write permissions necessary.
03036,2, "Specified module is not a valid start module, unable to generate menu"
// *Cause :  The module specified from which to start the menu generation is
//	     not a valid start module.
//	     To be valid, a start module must:
//	     --- be of type MENU or type DEFAULT
//	     --- be of language Forms
//	     --- call other modules in the module network
//	     [lastlistitem]
//	     Note that at least one of the called modules must also
//	     be of type MENU or type DEFAULT, and of language Forms.
// *Action : Modify the module definition and/or the module network to make
//	     the module a valid start module.
/
/ 04001 .. 04050 Forms generator Repository words
/
/
/ 04051 .. 04100 Forms generator GIO specific messages
/
/
/ 05101 .. 05150 Generator messages displayed to user
/
05101,6, "Hlp_Text column of help table %s increased to match source of help text\n"
// *Cause :
// *Action :
05120,8, "%ld rows deleted / %ld rows added from/to table %s for module %s\n"
// *Cause :  .
// *Action : .
05122,8, "%ld rows deleted / %ld rows added from/to table %s for table %s\n"
// *Cause :  .
// *Action : .
05133,1, "Call Key-Fn Trigger Code will not be generated to call other modules."
// *Cause :  The preference 'CALLFM' has been set to 'Y',
//	     but no other modules have been decalred
//	     in the module network.
// *Action : Establish the relevant 'called modules' in the
//	     module's Repository definition or set the
//	     preference CALLFM to 'N'.
05138,6, "What tablespace should table %s be created in? (NULL)"
// *Cause :
// *Action :
05139,1, "number mask 'DATE' not supported in Oracle Reports"
// *Cause :
// *Action :
05140,1, "number mask 'EEEE' not supported in Oracle Reports"
// *Cause :
// *Action :
05146,8, "Loading form template%s from %s (%s)"
// *Cause :
// *Action :
05148,8, "No template form being used"
// *Cause :
// *Action :
05149,8, "Loading object library%s from %s (%s)"
// *Cause :
// *Action :
05150,8, "Loading menu template%s from %s (%s)"
// *Cause :
// *Action :
/
/ 05151 .. 05200 Generator prompts requiring user response
/
05153,5, "Do you want to re-enter ?"
// *Cause :  .
// *Action : .
05163,5, "Do you want it created ?"
// *Cause :  .
// *Action : .
05165,5, "Do you want to check-in this file?"
// *Cause :
// *Action :
05166,8, "No object library being used"
// *Cause :
// *Action :
05171,5, "Do you want to remove the default value ?"
// *Cause :  .
// *Action : .
05177,5, "Enter name of log file to be created :"
// *Cause :
// *Action :
05178,5, "Do you want to display the log file ?"
// *Cause :
// *Action :
05179,6, "YES"
// *Cause :
// *Action :
05180,6, "NO"
// *Cause :
// *Action :
05181,6, "N"
// *Cause :
// *Action :
05182,6, "Y"
// *Cause :
// *Action :
/
/ 05201 .. 05250 Generator Preference messages
/
/
/ 05251 .. 05300 Generator for Application Systems messages
/
/
/ 05301 .. 05400 Generator banner & usage text for casegen.c
/
05325,6, "Loading Form"
// *Cause :
// *Action :
/
/ 05401 .. 05450 Generator log file messages
/
05402,6, "Form Generator log file '%s' created %s by %s"
// *Cause :
// *Action :
05403,6, "Total number of errors and warnings logged: %d"
// *Cause :
// *Action :
/
/ 06001 .. 07000 Messages in generator forms (eg cgpref.inp)
/
/
/ 07001 .. 08000 Form Generator Utilities
/
07001,2, "Failed to initialise Forms context handle"
// *Cause :
// *Action :
07002,2, "Failed to create new Form module"
// *Cause :
// *Action :
07003,2, "Failed to save Form to %s fmb file"
// *Cause :
// *Action :
07004,2, "Failed to load object library from %s olb file"
// *Cause :
// *Action :
07005,2, "Failed to create a new object library"
// *Cause :
// *Action :
07006,2, "Failed to save object library to %s olb file"
// *Cause :
// *Action :
07007,2, "Failed to connect to database"
// *Cause :
// *Action :
07008,2, "Failed to disconnect from database"
// *Cause :
// *Action :
07009,2, "Program Completed : File %s has been saved"
// *Cause :
// *Action :
07010,2, "Bad program command line : %s"
// *Cause :
// *Action :
07011,2, "Program Failure: Exception thrown in file %s (line %s)"
// *Cause :
// *Action :
07012,6, "because : %s"
// *Cause :
// *Action :
07013,2, "Program Failure: API exception thrown (Error status : %d )"
// *Cause :
// *Action :
07014,2, "Program Failure: A registry problem has occurred"
// *Cause :
// *Action :
07015,6, "    Form To Object Library Utility (fm2lib61.exe) Windows 95/98/NT"
// *Cause :
// *Action :
07016,6, "    Version %s,  Production on %s"
// *Cause :
// *Action :
07017,6, "    Copyright (c) 1995,2004 Oracle Corporation. All rights reserved"
// *Cause :
// *Action :
07018,6, "fm2lib61.exe -i formname.fmb -o libname.olb [APPEND]"
// *Cause :
// *Action :
07019,2, "A destination olb file has not been specified"
// *Cause :
// *Action :
07020,2, "A source fmb file must be specified"
// *Cause :
// *Action :
07021,1, "Warning : User has chosen APPEND option, but the named object library file"
// *Cause :
// *Action :
07022,1, "has not been found ( creating new object library)"
// *Cause :
// *Action :
07023,1, "Warning : User has not chosen the APPEND option, but the named object"
// *Cause :
// *Action :
07024,1, "library file has been found (overwriting existing file with new one)"
// *Cause :
// *Action :
07025,1, "Warning : Unable to find a tab for %s"
// *Cause :
// *Action :
07026,2, "CLibraryTab has not been instantiated with a context handle"
// *Cause :
// *Action :
07027,2, "In CLibraryTab, an attempt has been made to create a tab that already exists"
// *Cause :
// *Action :
07028,2, "A null object has been passed to LibraryTabAddObject"
// *Cause :
// *Action :
07029,2, "A null object name has been passed to LibraryTab::AddObject"
// *Cause :
// *Action :
07030,2, "Failed to add objects to object library tab (d2ferr %d)"
// *Cause :
// *Action :
07031,2, "A CLibraryTab has no name defined"
// *Cause :
// *Action :
07032,2, "Unable to open the key %s"
// *Cause :
// *Action :
07033,2, "Failed to load form from %s fmb file"
// *Cause :
// *Action :
07034,2, "Failed to retrieve child key"
// *Cause :
// *Action :
07035,2, "Unnamed key has been found in registry"
// *Cause :
// *Action :
07036,2, "A 'non-string' value has been found in the registry"
// *Cause :
// *Action :
07037,2, "Unnamed string value has been found in the registry"
// *Cause :
// *Action :
07038,2, "A destination fmb file has not been specified"
// *Cause :
// *Action :
07039,6, "  Process Form Utility (pfrm61.exe)  Windows 95/98/NT"
// *Cause :
// *Action :
07040,6, "    eg. pfrm61.exe -i OLD.FMB -o NEW.FMB"
// *Cause :
// *Action :
07041,2, "Process token is missing from command line"
// *Cause :
// *Action :
07042,6, " .....Process '%s'  successfully completed"
// *Cause :
// *Action :
07043,6, ".....Process '%s' NOT RECOGNISED"
// *Cause :
// *Action :
07044,6, "pfrm61 -i <oldfile.fmb> -o <newfile.fmb>"
// *Cause :
// *Action :
07045,6, "opt1(param1%param2%..) [opt2(param1%..) opt3...]"
// *Cause :
// *Action :
07046,6, "  Options"
// *Cause :
// *Action :
07047,2, "CLibraryTab has not been instantiated with an OLB handle"
// *Cause :
// *Action :
07048,6, " ChVisAt(arrows%none) AddTrg(Sometext)"
// *Cause :
// *Action :
07049,2, "CAddModTrigCmts has incorrect num of args"
// *Cause :
// *Action :
07050,2, "CAddPrgUntCmts has incorrect num of args"
// *Cause :
// *Action :
07051,2, "Unable to create a new visual attribute"
// *Cause :
// *Action :
07052,2, "Failed to remove ROOT_WINDOW"
// *Cause :
// *Action :
07053,2, "An error has occurred in the source code"
// *Cause :
// *Action :
07054,2, "A Form API macro call has failed to execute properly"
// *Cause :
// *Action :
07055,2, "No command line options have been specified"
// *Cause :
// *Action :
07056,2, "An error has occurred in accessing the registry"
// *Cause :
// *Action :
07057,2, "Dupilicate list members can not ne inserted"
// *Cause :
// *Action :
07058,6, "ChVisAt"
// *Cause :
// *Action :
07059,6, "Change visual attribute background property from <param1> to <param2>"
// *Cause :
// *Action :
07060,6, "AddTrg"
// *Cause :
// *Action :
07061,6, "Add comment <param1> to module level triggers"
// *Cause :
// *Action :
07062,6, "AddPUnit"
// *Cause :
// *Action :
07063,6, "Add comment '<param1> program unit name' to program units"
// *Cause :
// *Action :
07064,6, "ConvRootWn"
// *Cause :
// *Action :
07065,6, "Removes ROOT_WINDOW window and copies Font & Colour properties to CG$WINDOW"
// *Cause :
// *Action :
07066,6, "This v.a. has had its properties copied from removed window (ROOT_WINDOW)"
// *Cause :
// *Action :
07067,2, "Tried to insert two tabs with the same name"
// *Cause :
// *Action :
07068,2, "Invalid command line format"
// *Cause :
// *Action :
07069,2, "CLibraryTab has not been instantiated with an OLB handle"
// *Cause :
// *Action :
07070,2, "CLibraryTab has not been instantiated with a Tab name"
// *Cause :
// *Action :
07071,2, "Failed to create a new object library tab (d2ferr: %d)"
// *Cause :
// *Action :
07072,2, "Unspecified"
// *Cause :
// *Action :
07073,2, "Failed to create a new Form Module"
// *Cause :
// *Action :
07074,8, "  New FMB File %s has been saved"
// *Cause :
// *Action :
07075,2, "CChgVisAttFillPath has incorrect num of args"
// *Cause :
// *Action :
07076,2, "CConvRootWn has incorrect num of args"
// *Cause :
// *Action :
07077,2, "Failed to get Visual Attr. properties"
// *Cause :
// *Action :
07078,2, "CLibraryTab has not been instantiated with a Tab name"
// *Cause :
// *Action :