Help Index

Help for error messages is available by message. When a message box appears, Click on the HELP command button. You will be presented with a possible cause for the situation and recommended corrective action.


Invalid FormFile Version.
Message #3 Invalid Form File Version.

Possible Causes:

-	The file specified was created using a later version of JetForm.

Corrective Action:

-	Forms cannot be opened if they were created using a more recent version of JetForm than one being used.


Cannot Open another Form File.
Message #4 Cannot Open another Form File.

Possible Causes:

-	JetForm has found too many errors and cannot open another form file.

Corrective Action:

-	Exit JetForm and restart.


Error Renaming File.
Message #10 Error Renaming File.

Possible Causes:

-	The file is protected and cannot be renamed.

-	A file already exists with the new name.

-	The file is a network file that is flagged read only.

Corrective Action:

-	Change file attributes.

-	Change network attributes.

-	Select a different name.


Error creating a Temporary File.
Message #11 Error creating a Temporary File.

Possible Causes:

-	Insufficient disk space available to create file.

-	Windows tempfile variable points to a disk with no space.

-	Windows tempfile variable points to a network drive where write privileges are denied.

Corrective Action:

-	Delete unnecessary files to create more disk space.

-	Change Windows tempfile variable in WIN.INI to point to new location (see Windows manual).


This file was not compiled with data prompting enabled.
Message #12 This file was not compiled with data prompting enabled.

Possible Causes:

-	Include prompt information' option was not selected when form was compiled.

Corrective Action:

-	Recompile form with 'Include prompt information' selected.


Error writing to the data file.
Message #13 Error writing to the data file.

Possible Causes:

-	File is too large for available disk space.

-	Trying to write to a network drive without write privileges.

-	Diskette is not in the drive.

Corrective Actions:

-	Increase the available disk space by deleting unwanted files.

-	Change network specifications.

-	Use another diskette or disk drive with more available disk space.

-	Verify diskette is properly inserted in the drive and the correct drive and path are specified.


Invalid data file
Message #14 Invalid data file : Filename.

Possible Causes:

-	File specified is not a valid JetForm data file.

Corrective Action:

-	Check path and file name are correct.


Out of global memory.
Message #15 Out of global memory.

Possible Causes:

-	Windows has run out of available global memory.

Corrective Action:

-	Close other windows to free up memory.


Database record has been deleted
Message #16 Database record has been deleted

Possible Causes:

-	Data base record has been deleted.


Error reading Database file.
Message #17 Error reading Database file

Possible Causes:

-	File is an unsupported database type.

-	File has become corrupted.

Corrective Action:

-	Verify database type.

-	Verify file contents within the database system.


End of Database file
Message #18 End of Database file

Possible Causes:

-	End of file has been reached.


Error creating Database file
Message #19 Error creating Database file

Possible Causes:

-	Form has too many fields.

-	Field names exceed Database limit.

-	Insufficient disk space to create database file.

-	Trying to write to a network drive without write privileges.

-	Trying to write to a diskette when diskette is not in the diskette drive.

Corrective Actions:

-	Increase the available disk space by deleting unwanted files.

-	Change network specifications.

-	Use another diskette or disk drive with more available disk space.

-	Verify diskette is properly inserted in the disk drive and the correct drive and path are specified.

-	Modify form to allow for Database limits.


Invalid version for formset file
Message #21 Invalid version for form set file

Possible Causes:

-	The form set file specified was created using a later version of JetForm.

Corrective Action:

-	Recompile the form in the corresponding version of JetForm-Design, or upgrade to a more recent version of JetForm-Filler/G.


Error reading formset file
Message #22 Error reading form set file

Possible Causes:

-	File has become corrupted because of damaged disk media or incomplete saving.

-	File is being read from a diskette that has become damaged.

-	Disk drive cannot read the diskette.

-	Diskette is not in the diskette drive.

Corrective Action:

-	Try to load a different copy of the file.

-	Verify diskette is properly inserted in the disk drive and the correct drive and path are specified.


File Open Error.
Message #100 File Open Error.

Possible Causes:

-	File name or search path was incorrectly entered.

-	File is located in a directory other than the one specified.

-	File is a protected file or if you are on a network, it is a protected network file.

-	File does not exist.

Corrective Action:

-	Correct search path or file name.

-	Change file or network attributes to make it accessible.


Message #102 - The INI file is not compatible with this version
Message #102 - The INI file is not compatible with this version of Filler. Please verify your installation.

Possible Causes:

The 'Version' entry in the [JetForm] section of the JFILLER.INI file does not match the running version of JetForm Filler. Perhaps the installation did not run to completion, or the .INI file is not in the Working Directory when you run JetForm Filler, nor is it in the directory where the JetForm Filler program is.

Corrective Action:

Ensure that the proper version of JFILLER.INI file is in the Working Directory.


You must specify a non-blank character for commas.
Message #1000 You must specify a non-blank character for commas.

Possible Causes:

-	Blank specified as comma delimited data separator.

Corrective Action:

-	Select a character other than a blank as the data separator, preferably one that does not appear elsewhere in your data.


You must specify a non-blank character for quoting string.
Message #1001 You must specify a non-blank character for quoting strings.

Possible Causes:

-	Blank specified as the character for the quoting strings.

Corrective Action:

-	Select a character other than a blank, preferably one that does not appear elsewhere in your data.


Unable to create the export file 'filename'.
Message #1002 Unable to create the export file 'filename'.

Possible Causes:

-	File is too large for available disk space.

-	Trying to write to a network drive without write privileges.

-	Diskette is not in the diskette drive.

Corrective Actions:

-	Increase the available disk space by deleting unwanted files.

-	Change network specifications.

-	Use another diskette or disk drive with more available disk space.

-	Ensure diskette is properly inserted in the disk drive and the correct drive and path are specified.


Error writing data to the export file 'filename'.
Message #1003 Error writing data to the export file 'filename'.

Possible Causes:

-	File is too large for available disk space.

-	Trying to write to a network drive without write privileges.

-	Diskette is not in the diskette drive.

-	Diskette contains bad media.

Corrective Actions:

-	Increase the available disk space by deleting unwanted files.

-	Change network specifications.

-	Use another diskette or disk drive with more available disk space.

-	Ensure diskette is properly inserted in the disk drive and the correct drive and path are specified.


File 'fieldname' - A string constant has a missing quote charac
Message #1005 File 'fieldname' - A string has a missing quote.

Possible Causes:

-	Closing quote was omitted from string in calculation or validation of specified field.

Corrective Actions:

-	Add closing quote to calculation or validation of specified field.


This logo is too large to display at the selected Display Facto
Message #1006 This logo is too large to display at the selected Display Factor. Increase the Display Factor and re-try.

Possible Causes:

-	Logo bitmap created for display is greater that 64K.

Corrective Actions:

-	Increase Display Factor until JetForm is able the display the logo.


There are no fields to prompt for.  They have all been dropped.
Message #1007 There are no fields left to prompt for. They have all been dropped.

Possible Causes:

-	All the data entry fields have been dropped because they were not included in the data file that was opened.

Corrective Actions:

-	Load a data file that includes some or all of the fields on the form.

-	Edit the data file to include some or all of the fields on the form.


Copy protection Violation - you must install an authorized copy
Message #1008 Copy protection Violation - you must install an authorized copy of JetForm.

Possible Causes:

-	An unauthorized copy of JetForm was installed.

-	JetForm copy protection was not transferred properly onto the hard disk.

-	JetForm was not properly de-installed before it was re-installed.

Corrective Actions:

-	Obtain an authorized version of JetForm.

-	De-install properly and then attempt to re-install JetForm.


No key field has been selected yet.  Select a key field now.
Message #1009 No key field specified for record selection in prompt mode.

Possible Causes:

-	No field name was entered for record selection.

Corrective Actions:

-	Enter the name of the field to be searched and the key to search for.


No records were selected.
Message #1010 No records were selected.

Possible Causes:

-	No record was selected for the given key and field.

Corrective Actions:

-	Select a record or cancel.


This field has no name.  It cannot be used for selection.
Message #1011 This field has no name. It cannot be used for selection.

Possible Causes:

-	Field chosen for selection by key has been compiled without a name.

Corrective Actions:

-	Select another field.

-	Change form in JetForm-Design to give the selected field a name, then recompile the form.


Invalid field name.
Message #1012 Invalid field name.

Possible Causes:

-	Field name specified does not exist.

-	Field name specified contains embedded spaces.

-	Field name specified begins with a space.

Corrective Actions:

-	Verify that the field name is correct and does exist.

-	Enter a field name without any spaces.


No key value entered.  Enter a key value.
Message #1013 No key value entered. Enter a key value.

Possible Causes:

-	No key value was entered for record search.

Corrective Actions:

-	Enter the key value that is to be searched for in the specified field (note that DOS wildcards * and ? can be used - see JetForm-Filler/G User Manual for details)


More than one fieldname matches.
Message #1014 More than one fieldname matches.

Possible Causes:

-	More than one fieldname matches the field name given.

Corrective Actions:

-	Recompile the form with different field names.


Please enter a field name first.
Message #1015 Please enter a field name first.

Possible Causes:

-	No field name has been entered.

Corrective Actions:

-	Enter a field name.


This is a protected or calculated field.  You cannot position t
Message #1016 This is a protected data field. You cannot position to it.

Possible Causes:

-	Selected field has been specified as a protected field during design and compilation.

Corrective Actions:

-	Change the attributes of the specified field in JetForm-Design by picking the selected field, entering Format - Field and clicking on Protected (see the JetForm-Design Reference Manual for more details).


Error loading USERFUNC.JF library. Calculation function cannot
Message #1017 Error loading USERFUNC.JF library. Calculation function cannot be processed.

Possible Causes:

-	JetForm cannot locate USERFUNC.JF in JetForm directory.

-	USERFUNC.JF file has become corrupted.

-	There is insufficient free memory to load USERFUNC.JF

Corrective Actions:

-	Verify that working copy of USERFUNC.JF is in the JetForm directory. If it is not, copy it into the JetForm directory or re-install JetForm.

-	Close down any unnecessary Windows to free additional memory.


Database file has unsupported data type.  JetForm does not supp
Message #1018 Database file has unsupported data type. JetForm does not support memo fields.

Possible Causes:

-	Attempting to load a database file with a data type not supported by JetForm.

Corrective Actions:

-	Verify that field name has been correctly entered.

-	Use a database that does not contain memo fields.


No JetForm-EMail server name was specified with the '-h' flag.
Message #1020 No JetForm-EMail server name was specified with the '-h' flag.

Possible Causes:

-	No JetForm-EMail server name was specified with the '-h' flag.

Corrective Action:

-	Re-enter the command with a server name included.


No JetForm-EMail server alias was specified with the '-h' flag.
Message #1021 No JetForm-EMail server alias was specified with the '-h' flag.

Possible Causes:

-	No JetForm-EMail server alias was specified with the '-h' flag.

Corrective Action:

-	Re-enter the command with an alias.


No JetForm-EMail server password was specified with the '-h' fl
Message #1022 No JetForm-EMail server password was specified with the '-h' flag.

Possible Causes:

-	No JetForm-EMail server password was specified with the '-h' flag.

Corrective Action:

-	Re-enter the command with a password.


No JetForm-EMail forms server was specified with the '-h' flag.
Message #1023 No JetForm-EMail forms server was specified with the '-h' flag.

Possible Causes:

-	No JetForm-EMail forms server was specified with the '-h-' flag.

Corrective Action:

-	Re-enter the command, identifying a forms server.


Error error linking to the JetForm-EMail Dynamic Link Library.
Message #1024 Error error linking to the JetForm for E-Mail Dynamic Link Library.

Possible Causes:

-	Error Error linking to the JetForm for E-Mail Dynamic Link Library.

Corrective Action:

-	Contact Technical Support.


Error error linking to the EMail Dynamic Link Library.
Message #1025 Error error linking to the EMail Dynamic Link Library.

Possible Causes:

-	Error error linking to the EMail Dynamic Link Library.

Corrective Action:

-	Contact Technical Support.


Error creating drawing window
Message #1029 Error creating drawing window.

Possible Causes:

-	Error creating drawing windows.

Corrective Action:

-	Contact Technical Support.


Error creating push buttons
Message #1028 Error creating push buttons.

Possible Causes:

-	Error creating push buttons

Corrective Action:

-	Contact Technical Support.


Message #1037 - Error creating Header window.

Possible Causes:

-	Error creating header windows.

Corrective Action:

-	Contact Technical Support.


There are no data files in the set: 'setname.
Message #1062 There are no data files in the set: setname.

Possible Causes:

-	There are no data files in the set setname.


There is no data file after: filename  in the set: setname.
Message #1063 There is no data file after: filename in the set: setname.

Possible Causes:

-	There is no data file after: filename in the set setname'.


Invalid date format in picture string.
Message #1070 Invalid date format in picture string.

Possible Causes:

-	Field picture format does not fit with field calculation of date.

Corrective Actions:

-	Correlate the field picture with the date calculation.


Invalid input for a date.
Message #1071 Invalid input for a date.

Possible Causes:

-	Date input has days, months, years, in wrong order.

-	Date input is not a valid data.

-	Data input uses wrong format for date.

Corrective Actions:

-	Input a date that corresponds to the calculation/validation or picture for the field.


Message #1068 - Are you sure you want to delete this record?

Possible Causes:

You are deleting a record.

Corrective Action:

Confirm or reject the deletion.


Message #1069 - OK to create a new record?

Possible Causes:

You have tabbed off the end of the last record in the current data file or you have chosen Next Record (Ctrl-PgDn) when on the last record of the current data file.

Corrective Action:

Confirm or reject the adding of a new record.


Response data not allowed for field type
Message #1075 Response data not allowed for this type of field.

Possible Causes:

-	You cannot set up response data for this type of field.

Corrective Action:

-	Do not use user responses for this field.


Unable to select requested font
Message #1079 Unable to select the requested font

Possible Causes:

-	The selected combination of typeface, point size, and style is not available for the current configuration.

Corrective Action:

-	Select a different combination or change your configuration to include the desired combination.


A form must opened before the data
Message #1083 First time use requires a form to be opened first. Select 'Use Form' from the File menu.

Possible Causes:

-	This data file was saved with the "Associate Form with Data" check box turned off.

Corrective Action:

-	Open the desired form (File: Use Form menu option) before opening the data file (File: Open Data).


Message #1084 - Error number accessing Configuration data. Run
Message #1084 - Error number accessing Configuration data. Run JfConfig to configure JetForm.

Possible Causes:

JetForm cannot find or cannot read the configuration files (JETFORM.ICS and JETFORM.ICF) for the printer, for which the form was compiled.

Corrective Action:

Use the JfConfig utility to recreate the configuration file for the printer in question or copy configuration files into JetForm directory.


Error initializing Paradox Engine
Message #1092 Error initializing Paradox Engine

Possible Causes:

-	Insufficient memory available to initialize.

-	The Paradox Engine has not been installed, or has been installed incorrectly.

Corrective Action:

-	Close down other windows to free memory.

-	Verify that the Paradox Engine (available from Borland) has been installed correctly.


Invalid database file extension
Message #1093 Invalid Database file extension

Possible Causes:

-	The file extension of the database file is not the default

Corrective Action:

-	If the file is dBASE, ensure that the file extension is .DBF. If the file is Paradox, ensure that the file extension is .DB.


Currently open form not part of formset
Message #1094 Currently open form is not part of this form set. The form set cannot be made active.

Possible Causes:

-	A form referenced in a form set data file has been removed from the form set since the data file was created.

Corrective Action:

-	Add the form to the form set and then delete the corresponding unwanted data.


No forms in the formset are initially active
Message #1095 At least one form in the form set must be initially active.

Possible Causes:

-	None of the forms within the requested form set have been set as initially active.

Corrective Action:

-	Use the Define Form Set command to edit the form set to define at least one form as initially active.


Last page of this formset
Message #1096 At the last page of this form set

Possible Causes:

-	You have completed the last page in the form set.

Corrective Action:

-	If you wish to enter more data for any one of the forms in the form set, ensure that the form is active (Select Form command) and then use the Goto Form command to access the form.


Form is not part of this formset
Message #1097 Form is not in the current form set. Record cannot be displayed

Possible Causes:

-	A form referenced in a form set data file has been removed from the form set since the data file was created.

Corrective Action:

-	Add the form to the form set.


^Form command missing from formset data record
Message #1098 ^ Form line is missing from this form set data record. Record cannot be displayed.

Possible Causes:

-	The requested data file is missing a ^form command which identifies the form to use.

Corrective Action:

-	Edit the data file and insert the missing ^form command for the identified record.


Database files cannot be processed with a form set
Message #1099 Only Non-database (ASCII) files may be accessed when using a form set.

Possible Causes:

-	Attempted access of a database file with a form set.

Corrective Action:

-	Use the File - New command to set the data file type to ASCII.


Can't print blank form compiled for Windows Print driver
Message #1106 Can't print a blank form compiled for a Windows Print driver.

Possible Causes:

-	The requested form was compiled for use with a Windows Print driver, and not for use with a JetForm Print driver.

Corrective Action:

-	The Print Blank Form command only supports forms compiled for use with a JetForm Print driver. Refer to the JetForm-Filler/G User Manual.


Too many fonts
Message #1110 Too many fonts.

Possible Causes:

-	JetForm supports approximately 1000 fonts. There are more than 1000 fonts installed for your Windows default printer.

Corrective Action:

-	Reduce the number of Windows printer fonts.


File name is too long or contains an invalid character
Message #1111 File name is too long or contains an invalid character.

Possible Causes:

-	The entered file name is greater than 8 characters, contains spaces, or contains other characters that are invalid for a DOS file name.

Corrective Action:

-	Correct the file name.


Message #1112 - Both an MDF and a data file are required for pr
Message #1112 - Both an MDF and a data file are required for printing.

Possible Causes:

The JetForm (Merge) printing facility has been run with too few parameters. Either the form (MDF file) name is missing or the data file name is missing.

Corrective Action:

Supply the required parameters. If the data file has been saved with a form file associated with it, you may supply the placeholder parameter (*) in lieu of the actual MDF file name.


Unable to load security library
Message #1114 Unable to load security library

Possible Causes:

-	An unauthorized copy of JetForm was installed.

-	JetForm copy protection was not transferred properly onto the hard disk.

-	JetForm was not properly de-installed before it was re-installed.

Corrective Actions:

-	Obtain an authorized version of JetForm.

-	De-install properly and then attempt to re-install JetForm.


* * Undefined message number* *
Message #1115 **Undefined Message number**

Possible Causes:

-	JetForm issued an undefined error message

Corrective Action:

-	contact technical support


Message #1120 - Invalid custom command operation: text=text

Possible Causes:

The operation in the custom command is invalid.

Corrective Action:

Change the operation in the custom command.


Message #1121 - Custom command menu not found: text=text

Possible Causes:

Corrective Action:


Message #1122 - Unsupported custom command call-back request nu
Message #1122 - Unsupported custom command call-back request number

Possible Causes:

Your custom command routine has called one of the JetForm callback functions but has passed an unrecognized request number to that function.

Corrective Action:

Supply the correct request number.


Message #1130 - You have read-only access to your data file

Possible Causes:

You do not have write access to your data file.

Corrective Action:

It is OK to proceed, however you will not be able to 'Save' any modifications back to this data file. Instead you should use 'Save As' to save modifications to another file location. Alternatively, you may use the DOS 'ATTRIB -R' command to allow write access to the data file.


Message #1131 - You cannot save to a read-only data file

Possible Causes:

You are trying to save your data file to a file which is write protected.

Corrective Action:

Use 'Save As' to save the data to a different file location. Note that an entire directory may be write protected so that it may be necessary to pick a new directory location as opposed to just a new file name.


Cannot select a Windows compiled form for alternate printing;us
Message #1155 Cannot select a Windows compiled form for alternate printing; using current form

Possible Causes:

-	The alternate form that JetForm tried to print with was compiled using Windows drivers.

Corrective Action:

-	Use only forms compiled for JetForm drivers for alternate form printing.


Message #1257 - The -n option applies only to forms compiled fo
Message #1257 - The -n option applies only to forms compiled for Windows printing.

Possible Causes:

JetForm Filler has been run with a '-n' parameter. This option is allowed only for forms which have been compiled for Windows (not JetForm drivers) printing.

Corrective Action:

Either discontinue use of the '-n' parameter or recompile the form for Windows printing.


Message #1507 - Unable to load DLL referenced in: calculation r
Message #1507 - Unable to load DLL referenced in: calculation rule text.

Possible Causes:

The form uses the CallDLL function but references a DLL which cannot be found.

Corrective Action:

Ensure that the DLL name is spelled correctly and that the DLL file is located where the JetForm Filler program is, or is otherwise located somewhere in your DOS PATH.


Message #1508 - Unable to access DLL function referenced in: 'c
Message #1508 - Unable to access DLL function referenced in: 'calculation rule text'.

Possible Causes:

The CallDLL function references a user function which cannot be found within the specified user DLL.

Corrective Action:

Ensure that the function name has been spelled correctly and that the DLL has been linked with all the required functions.


Message #1509 - Invalid data type for parameter in DLL function
Message #1509 - Invalid data type for parameter in DLL function referenced in: 'calculation rule text'.

Possible Causes:

A user DLL function has been specified as having certain parameters with specific data types. However, that function is being called with a parameter that is not of the specified data type. For example, a character string is being passed where a numeric value is required.

Corrective Action:

Either change the DLL function so that it can accept the new data type(s) or provide the appropriate data types to the function.


Message #1510 - Invalid data type for return value in DLL funct
Message #1510 - Invalid data type for return value in DLL function references in: 'calculation rule text'.

Possible Causes:

A user DLL function has been specified as having a return value with a specific data type. However, that function is returning a different data type.

Corrective Action:

Either change the DLL function so that it returns the new data type(s) or change the form to expect the returned data type.


Message #1602 - OK to delete current JetNote?

Possible Causes:

You have requested deletion of the current JetNote.

Corrective Action:

Either confirm or reject the JetNote deletion.


Message #1700 - Error creating OLE Object. Error Type (number),
Message #1700 - Error creating OLE Object. Error Type (number), Error (number)

Click on one of the following for further information:

ERROR TYPE 0

ERROR TYPE 1

ERROR TYPE 2

ERROR TYPE 3

ERROR TYPE 4


Message #1701 - Error reading OLE Object data.

Possible Causes:

Corrective Action:


Message #1702 - Error loading OLE DLLs.  Object Linking and Emb
Message #1702 - Error loading OLE DLLs.  Object Linking and Embedding will not be available.  For more information or to suppress this Error message please see the on-line help.

Possible Causes:

Perhaps the OLE 2.0 DLLs are missing or are not in your DOS PATH.

Corrective Action:

Ensure that the OLE DLLs are located in the SYSTEM directory of your Windows installation.  The JetForm setup process will install the OLE DLLs in the appropriate location.


Message #1703 - Error creating OLE system file.  DOS SHARE must
Message #1703 - Error creating OLE system file.  DOS SHARE must be loaded for OLE to be available.  For more information or to suppress this error message please see the on-line help.

Possible Causes:

DOS SHARE is not running and the 'AllowOLE' setting of the JFILLER.INI file is 'Yes'.

Corrective Action:

Ensure that DOS SHARE is running.  Alternatively, if you do not wish to use OLE, you may change the 'AllowOLE' setting in the JFILLER.INI file to 'No'.


Message #1901 - Authorization file is empty; cannot perform ope
Message #1901 - Authorization file is empty; cannot perform operation.

Possible Causes:

The signature authorization file (.SAF) has not been properly constructed.

Corrective Action:

Create the signature authorization file using the JetForm Signature Administration tool.


Message #1902 - GlobalLock failed.

Possible Causes:

Possible internal software error.

Corrective Action:

Call JetForm Support staff and report the problem.


Open error on Signature Verification File
Message #1905 - Open error on Signature Verification File

Possible Causes:

-	File is a protected file, or if you are on a network you do not have read privileges for the file.

-	INI file contains incorrect directory specification for SignatureVerificationFile in [Paths] section.

Corrective Action:

-	Change file attributes or network privileges to provide access to JETFORM.SVF.

-	Exit from the application. Access the INI file and correct the directory specification.


Seek error on signature file
Message #1906 - Seek error on signature file.

Possible Causes:

-	File data has become corrupted or hard-disk read error has occurred.

Corrective Action:

-	Try to access a back-up copy or another copy of the file if it is available.


Read error on signature file
Message #1907 - Read error on signature file.

Possible Causes:

-	File data has become corrupted or hard-disk read error has occurred.

Corrective Action:

-	Try to access a back-up copy or another copy of the file if it is available.


Write error on signature file
Message #1908 - Write error on signature file.

Possible Causes:

-	Insufficient disk space.

-	Trying to write to a network drive without write privileges.

Corrective Action:

-	Increase available disk space by deleting unwanted files.

-	Modify the path specification for SignatureVerificationFile in JFDESIGN.INI to specify a drive and directory where there is sufficient free disk space.

-	Modify the path specification for SignatureVerificationFile in JFDESIGN.INI to specify a network drive and directory where you have write privileges.


Open error on Signature Authorization File
Message #1912 - Open error on Signature Authorization File

Possible Causes:

-	File is a protected file, or if you are on a network you do not have read privileges for the file.

-	An invalid file name has been entered.

Corrective Action:

-	Change file attributes or network privileges to provide access to JETFORM.SVF.

-	Verify that the entered file name is valid.


Invalid Password
Message #1913 - Invalid Password

Possible Causes:

-	The entered password is invalid.

Corrective Action:

-	Enter to correct password.


The passwords do not match
Message #1953 - The passwords do not match

Possible Causes:

-	The entered passwords do not match.

Corrective Action:

-	Re-enter the passwords.


No password has been given
Message #1954 - No password has been given

Possible Causes:

-	No password was specified.

Corrective Action:

-	Enter a password.


You did not sign this field
Message #1978 You did not sign this field

Possible Causes:

-	You cannot unsign a field you did not sign.


Cannot access library JFSFLIB.DLL for signature files
Message #1983 - Cannot access library JFSFLIB.DLL for signature files.

Possible Causes:

-	Access library JFSFLIB.DLL could not be found in the JetForm directory.

-	There was insufficient memory available for JetForm to load the access library.

Corrective Action:

-	Verify that JFSFLIB.DLL is in the JetForm directory.

-	Close down any unnecessary Windows applications to increase the available memory.


Message #1985 - The signature has verified successfully

Possible Causes:

You are verifying a signature and it has been validated.


Message #1986 - No log-in name is available for signature gener
Message #1986 - No log-in name is available for signature generation

Possible Causes:

You are using E-Mail based security but have not logged in to the E-Mail system.

Corrective Action:

Login to the E-Mail system or use JetForm based security checking.


Message #2000 - Creating output file filename.

Possible Causes:

You are creating an output file.


Error creating file Filename.
Message #2001 Error creating file Filename.

Possible Causes:

-	Insufficient space on disk to create compiled form file.

-	Attempting to write to a network drive without write privileges.

-	Diskette is not properly inserted in drive or is incompatible with drive.

Corrective Action:

-	Delete unwanted files from disk to increase available disk space.

-	Check network drive attributes or select another drive.

-	Verify diskette is compatible with drive and is properly inserted.


Error reading page number of document.
Message #2003 Error reading page number of document.

Possible Causes:

-	Data on specified page has become corrupted.

Corrective Action:

-	Copy specified page to clipboard, delete page, open new page and then paste from clipboard to new page.

-	Delete specified page and redesign it.


Error opening font file filename.
Message #2004 Error opening font file filename.

Possible Causes:

-	Soft fonts do not exist in the directory specified during configuration.

-	Soft font files are not usable with current configuration.

Corrective Action:

-	Run JFConfig and re-configure soft fonts compatible with the specified configuration


Error writing output.
Message #2006 Error writing output

Possible Causes:

-	Communication breakdown between printer and JetForm.

-	Error writing to disk when using a printer-ready file.

-	Printer jammed, out of paper, printer not switched on etc..

Corrective Action:

-	Check printer for errors.

-	Check printer cable(s) to verify it is properly plugged in.

-	Verify that there is sufficient free space on disk to write file.


Error opening logo file 'Filename'.
Message #2007 Error opening logo File 'Filename'.

Possible Causes:

-	Logo file specified is not in the same directory as it was when the form was designed.

-	Logo file specified is not in the same directory as it was when the form was compiled.

-	Entered file name does not exist.

Corrective Action:

-	Put the logo file in exactly the same directory as it was when the form was designed.

-	Put the logo file in exactly the same directory as it was when the form was compiled (Note: If this error was received when loading a form into Filler/G, it should not be of great concern since logos are compiled into the form and even if this error is ignored the logo will still appear during printing; although it will not be visible on the screen).

-	Ensure that the entered file name is correct and exists on the specified drive and directory.


Error reading logo file Filename.
Message #2008 Error reading logo file Filename.

Possible Causes:

-	Logo file data is corrupted.

-	Diskette is not properly inserted into drive.

Corrective Action:

-	Use a backup copy of the logo file.

-	Verify diskette is properly inserted in drive.

-	Try a different diskette.


Unable to open the MDF file 'Filename'.
Message #2011 Unable to open the MDF file 'Filename'

Possible Causes:

-	File specified is not a JetForm MDF file.

-	File is incompatible with JetForm.

-	MDF file data has become corrupted.

-	Invalid file name or path has been specified.

Corrective Action:

-	Verify that specified filename and path are correct.

-	Use backup copy of MDF file or re-compile MDF file.


Error reading MDF file 'Filename'.
Message #2012 Error reading MDF file 'Filename'

Possible Causes:

-	MDF file data has become corrupted because of damaged disk media or incomplete saving.

-	MDF file is being read from a diskette that has become damaged.

-	Disk drive cannot read the diskette.

-	Diskette is not in disk drive.

Corrective Action:

-	Try to load a different copy of the file or use a back-up copy if it is available.

-	Re-compile the form to create a new MDF.

-	Verify diskette is properly inserted in the disk drive and the correct drive and path are specified.


Unable to get memory for MDF file load.
Message #2013 Unable to get memory for MDF file load.

Possible Causes:

-	Too much memory used for other Window applications

-	Form file too big or too complicated for available memory.

Corrective Action:

-	Close one or more currently active Windows applications.

-	Simplify form file.


Unable to open the output device 'Device'.
Message #2014 Unable to open output device 'Device'.

Possible Causes:

-	Communication breakdown between printer and JetForm.

-	Printer jammed, out of paper, not switched on, etc..

Corrective Action:

-	Check printer for errors.

-	Check printer cable(s) to verify it is properly plugged in.

-	Verify that there is sufficient free space on disk to write file.


This is the last Field on this Page.  OK to proceed with the ne
Message #2051 This is the last Field on the Page. OK to proceed with the next Page?

Possible Causes:

-	The last field on the page has been filled.


This the last Field on the Record.  OK to proceed with next Rec
Message #2052 This is the last Field on this Record. OK to proceed with next Record?

Possible Causes:

-	The last field in the record has been filled.


Message #2218 - Error creating temporary data file for multi-pa
Message #2218 - Error creating temporary data file for multi-part.

Possible Causes:

-	Directory protection violations.

-	Insufficient disk space to create temporary file.

-	Trying to write to a network drive without write privileges.

-	Trying to write to a diskette when diskette is not in the diskette drive.

Corrective Actions:

-	Ensure that you have write privileges to your data directory and to your 'temporary' directory (as defined by the DOS 'TEMP' environment variable).

-	Increase the available disk space by deleting unwanted files.

-	Change network specifications.

-	Use another diskette or disk drive with more available disk space.

-	Verify diskette is properly inserted in the disk drive and the correct drive and path are specified.


Message #2220 - Error reading from multi-part temporary file.

Possible Causes:

A temporary file that has just been created as part of an operation with a multi-part form, has suddenly become unreadable. Perhaps it has been deleted by another process.

Corrective Action:

Redo the function.


Message #3460 - Wrapping record at field number. Increase MaxRe
Message #3460 - Wrapping record at field number. Increase MaxRecordLen in filename file.

Possible Causes:

The text for the specified field is too long. It has to be wrapped in order to fit within the MaxRecordLen constraint.

Corrective Action:

Increase the MaxRecordLen constraint.


Message #3461 - Data for field number is too large.  Increase M
Message #3461 - Data for field number is too large.  Increase MaxRecordLen in filename file.

Possible Causes:

The text for the specified field is too long. It has to be wrapped in order to fit within the MaxRecordLen constraint.

Corrective Action:

Increase the MaxRecordLen constraint.


Message #4000 - Global text string not found.

Possible Causes:

Software error.

Corrective Action:

Record what actions you have been doing and provide the information to JetForm Support staff.


Message #4009 - Cannot extract information for default fax.

Possible Causes:

Either the 'Fax' entry of the '[JetForm]' section of your JFILLER.INI file does not exist or the referenced fax is not in the '[devices]' section of your WIN.INI file.

Corrective Action:

Add the applicable entries to your JFILLER.INI and/or WIN.INI files.


Form exported to file name
Message # 4012 Form exported to file name

Possible causes:

A file was selected to export to.


Form file name has been stored on the clipboard. The form may n
Message # 4015 Form file name has been stored on the clipboard. The form may now be pasted in

Possible causes:

A form file was selected to copy from.


Message #4018 - The network appears to be very busy.  Would you
Message #4018 - The network appears to be very busy.  Would you like to retry accessing the Serial Number file now?

Possible Causes:

The Serial Number file referenced in the form is locked by another user or has become inaccessible despite a number of retry attempts.

Corrective Action:

Wait a moment and retry. Determine who has the file locked and how long it will be inaccessible.


Message #4019 - ERROR: The Serial Number file is incomplete.

Possible Causes:

A Serial Number file referenced in this form has been improperly constructed. It does not contain all of the required information.

Corrective Action:

Edit the Serial Number file and supply the missing information.


Message #4020 - Unable to find the Serial Number file.

Possible Causes:

The form uses the Serial() function and references a Serial Number file. That file cannot be found. Perhaps the directory specification is incorrect or the file name is misspelled.

Corrective Action:

Ensure the file name is spelled correctly and ensure that the file is in the specified directory.


Message #4021 - ERROR: The Serial Number file has depleted its'
Message #4021 - ERROR: The Serial Number file has depleted its' range of values.

Possible Causes:

The limit specified in a SerialNumber file has been reached.

Corrective Action:

Increase the limit or begin a new sequence.


Message #5021 - Warning!   Form 'form name' has already been in
Message #5021 - Warning!   Form 'form name' has already been included in the document.  OK to add another copy?

Possible Causes:

You are inserting or appending another form to an open form set. However that form is already included in the form set.

Corrective Action:

Confirm or reject the inclusion of the [duplicate] form.


Message #5022 - The data has been saved in file: 'file name'.

Possible Causes:

Your JFILLER.INI file setting requests confirmation of all data file saves and you have just successfully saved a data file. The .INI file entry is called 'ConfirmSave' and is in the '[Prompt]' section.

Corrective Action:

None required. The message is for your information only. If you no longer wish to receive this confirmation message edit your JFILLER.INI file to request no save confirmation messages.


No spelling errors were encountered
Message # 5090 No spelling errors were encountered

Possible causes:

No spelling errors were found


Spell checking is complete
Message # 5091 Spell checking is complete

Possible causes:

The spelling checker finished checking all selected areas on the form.


Message #5094 - Unable to open configuration file: 'file name'.

Possible Causes:

The configuration file for the printer for which the form was compiled cannot be found. Perhaps the installation process did not run to completion. Or, the 'ConfigFile' path specification in your JFDESIGN.INI file is missing or incorrect.

Corrective Action:

Ensure that the 'ConfigFile' path specification in your JFDESIGN.INI file is correct.


Message #5135

This error message warns that you attempted to start a second copy of JetForm Server.


Message #7009 - Unable to load message control file

Possible Causes:

this is only for Filler/C


Message #7010 - E-Mail program invoked with no parameters

Possible Causes:

this is only for Filler/C.


Unable to open file-name
Message # 7014 Unable to open file-name.

Possible Causes:

-	The error log file for the mail package could not be found.

Corrective Action:

-	Ensure that there is sufficient free disk space for the mail package to create the error log file.

-	Check the mail package to determine if there are problems with log-in or access to the mail database.


Message #7015 - Unable to send message

Possible Causes:

Corrective Action:


Message #7026 - Unable to access export file

Possible Causes:

Corrective Action:


Message #7027 - Unable to create mail-box list file

Possible Causes:

Corrective Action:


Message #7028 - Unable to create attachment file

Possible Causes:

Corrective Action:


Message #7029 - Unable to read mail-box list file

Possible Causes:

Corrective Action:


Message #7030 - No incoming mail

Possible Causes:

Filler/C only


Message #7031 Message not found

Possible Causes:

Software error. The string associated with a message number has not been found.

Corrective Action:

Call JetForm Support staff and report the problem.


Message #7032 Message was not generated by JetForm

Possible Causes:

A message with a subject line containing 'jfm: ' has been processed, but the message is not a JetForm generated message. There is no associated JetForm .jfm file for JetForm Filler to process.

Corrective Action:

Do not process this message with JetForm Filler. Use your standard mail facilities.


Message #7034 - Unable to redirect mail program output

Possible Causes

Filler/C only.


Message #7035 - Warning: this message contains non-JetForm atta
Message #7035 - Warning: this message contains non-JetForm attachment(s)

Possible Causes

a 3.1 message.

Corrective Action:


Message #7050 - Message has been forwarded

Possible Causes

The message has been forwarded per your request.


Message #7051 - Message has been returned

Possible Causes

The message has been returned per your request.


Message #7052 - New message has been sent

Possible Causes

The message has been sent as requested.


Message #7060 - Unable to open text file

Possible Causes

A text note file cannot be read. Possibly it has been deleted or has become corrupt.

Corrective Action:

Try reopening the message in the vendor mail package. The text note file, if it can be read, will be viewable via the vendor mail facilities.


Message #7061 - Unable to create text file

Possible Causes

A file write error occurred while trying to write a text note file. Perhaps you do not have write access to your temporary workfile directory, or your disk is full.

Corrective Action:

Ensure that you have the necessary write privileges and sufficient disk space.


Message #7062 Conflicting send index field values; message cann
Message #7062 Conflicting send index field values; message cannot be sent

Possible Causes

An incorrect data file specifies more than one SEND_INDEX field and their values are not identical. Possibly there are two or more SEND_INDEX fields in your form file.

Corrective Action:

Correct the data file or design the form so that only one SEND_INDEX field is present.


Message #7063 Conflicting To field values; message cannot be se
Message #7063 Conflicting To field values; message cannot be sent

Possible Causes

More than one 'To' field exists in your form or your data file -- and the values for those fields are not the same.

Corrective Action:

Correct the form definition or data file.


Message #7064 Conflicting CC field values; message cannot be se
Message #7064 Conflicting CC field values; message cannot be sent

Possible Causes

More than one 'CC' field exists in your form or your data file -- and the values for those fields are not the same.

Corrective Action:

Correct the form definition or data file.


Message #7065 Conflicting BCC field values; message cannot be s
Message #7065 Conflicting BCC field values; message cannot be sent

Possible Causes

More than one 'BCC' field exists in your form or your data file -- and the values for those fields are not the same.

Corrective Action:

Correct the form definition or data file.


Message #7066 Conflicting TRACK_TO field values; message cannot
Message #7066 Conflicting TRACK_TO field values; message cannot be sent

Possible Causes

More than one 'TRACK_TO' field exists in your form or your data file -- and the values for those fields are not the same.

Corrective Action:

Correct the form definition or data file.


Message #7067 Conflicting From field values; message cannot be
Message #7067 Conflicting From field values; message cannot be sent

Possible Causes

More than one 'From' field exists in your form or your data file -- and the values for those fields are not the same.

Corrective Action:

Correct the form definition or data file.


Message #7068 Conflicting Subject field values; message cannot
Message #7068 Conflicting Subject field values; message cannot be sent

Possible Causes

More than one 'Subject' field exists in your form or your data file -- and the values for those fields are not the same.

Corrective Action:

Correct the form definition or data file.


Message #7069 Conflicting Attachments field values; message can
Message #7069 Conflicting Attachments field values; message cannot be sent

Possible Causes

More than one 'Attachment' field exists in your form or your data file -- and the values for those fields are not the same.

Corrective Action:

Correct the form definition or data file.


Message #7070 Cannot save an attachment to its temporary source
Message #7070 Cannot save an attachment to its temporary source file

Possible Causes

An attachment copied out of the mail system into a temporary location cannot be saved over itself. If it were saved there, it would eventually be deleted by subsequent mail system processing.

Corrective Action:

Save the attachment to a new location.


Message #7071 Conflicting Mail Form field values; message canno
Message #7071 Conflicting Mail Form field values; message cannot be sent

Possible Causes

More than one 'Form' field exists in your form or your data file -- and the values for those fields are not the same.

Corrective Action:

Correct the form definition or data file.


Message 7072
Message #7072 Message includes form, but form file has the potential to change along the route

Possible Causes:

The form has a Mail_form field and the "Send form with data" option has been selected. These two are incompatible.

Corrective action:

Change your mail options so that the form is not included with the data before sending.


Message #7073
Message #7073 Warning: Message includes form, but form file has potential to change along the route

Possible causes:

The form has a MAIL_FORM field and the "Send form with data" option has been selected.

Corrective Action:

None. To send the message, follow the usual procedure. The form will not be sent with the message.


Message #7101 number records will be sent and each will be dele
Message #7101 number records will be sent and each will be deleted

Possible Causes

This is an information message.

Corrective Action:

Confirm or reject the message send operation.


Message #7102 number records will be sent

Possible Causes

This is an information message.

Corrective Action:

Confirm or reject the message send operation.


Message #7103 Record will be sent and then deleted

Possible Causes

This is an information message.

Corrective Action:

Confirm or reject the message send operation.


Message #7110 Sending record number of number ...

Possible Causes

Informational message.


Message #7122 Preparing Message

Possible Causes

Informational status message


Message #7123 OK to delete this message?

Possible Causes

You have selected Delete Message'.

Corrective Action:

Confirm or reject the message deletion.


Message #7126 number message(s)

Possible Causes

Informational status message


Message #7127 number unread message(s)

Possible Causes

Informational status message


Message #7129 Unable to start application for 'attachment file
Message #7129 Unable to start application for 'attachment file name'; status: number

Possible Causes

Perhaps the application cannot be found (is not in the DOS PATH) or there is insufficient memory/resources to run the application at this time.

Corrective Action:

Ensure that the application is in your DOS PATH. Possibly terminating some other application(s) will free sufficient resources to run the application in question.


Message #7130 OK to remove attachment  attachment file name?

Possible Causes

User request.

Corrective Action:

Either confirm or reject the attachment deletion.


Message #7132 Sending message ...

Possible Causes

Corrective Action:


Message #7133 Data will be sent and then deleted

Possible Causes

Informational status message


Message #7134 Saving attachment file name

Possible Causes

Informational message


Message #7135 Done saving attachment file name

Possible Causes

Positive confirmation that an attachment file has been successfully saved.


Message #7136 Unable to locate VIM.DLL.  Continue without E-Mai
Message #7136 Unable to locate VIM.DLL.  Continue without E-Mail?

Possible Causes

The VIM DLL is not in your DOS PATH.

Corrective Action:

Ensure that the VIM DLL is in your DOS PATH.


Message #8000 Unable to load button bar library BB.DLL, status:
Message #8000 Unable to load button bar library BB.DLL, status: number

Possible Causes

The button bar library BB.DLL is missing or not in your DOS PATH.

Corrective Action:

Ensure that the BB.DLL file is in your DOS PATH.


Message #8001 Out of global memory - Button Bar

Possible Causes

Software error.

Corrective Action:

Call JetForm Support staff and report the actions that led up to the error.


Message #8002 Unable to create window - Button Bar

Possible Causes

Software error.

Corrective Action:

Call JetForm Support staff and report the actions that led up to the error.


Message #8003 Unknown button bar error: number

Possible Causes

Software error.

Corrective Action:

Call JetForm Support staff and report the actions that led up to the error.


Message #9011 Field 'field name' referenced in database rule no
Message #9011 Field 'field name' referenced in database rule not found.

Possible Causes

A database rule references a form field which does not exist. Possibly it is a field name misspelling or a field has been deleted from the form definition after the rule was defined.

Corrective Action:

Correct the form definition so that the database rules references to form fields are valid.


Message #9012 No records were inserted.

Possible Causes

Information message.


Message #9013 1 record was inserted.

Possible Causes

Information message.


Message #9014 number records were inserted.

Possible Causes

Information message.


Message #9015 No records were updated.

Possible Causes

Information message.


Message #9016 1 record was updated.

Possible Causes

Information message.


Message #9017 number records were updated.

Possible Causes

Information message.


Message #9018 No records were deleted.

Possible Causes

Information message.


Message #9019 1 record was deleted.

Information message.


Message #9020 number records were deleted.

Possible Causes

Information message.


Message #9021 No rows were selected.

Possible Causes

Possibly the selection criteria result in no matches with any of the rows in the database table(s) involved.

Corrective Action:

A revision of the selection criteria may result in rows being selected.


Invalid Form File.
Message #2 Invalid Form File

Possible Causes:

-	The form file specified is not a JetForm form file.

Corrective Action:

-	Make sure file and path name are correct.


Unable to open file 'Filename'.
Message #20 Unable to open file Filename.

Possible Causes:

-	File name or search path was incorrectly entered.

-	File is located in a directory other than the one specified.

-	File is a protected file or if you are on a network, it is a protected network file.

-	File does not exist.

Corrective Action:

-	Correct search path or file name.

-	Change file or network attributes to make it accessible.


Error 'error' returned from print utility
Message #2200 Error 'error' returned from print utility

Possible Causes:

-	JetForm encountered specified error when attempting to print.


Error opening output device/file.
Message #2202 Error opening output device/file.

Possible Causes:

-	Communication breakdown between printer and JetForm.

-	Error writing to disk when using a printer-ready file.

-	Printer jammed, out of paper, not switched on etc..

Corrective Action:

-	Check printer for errors.

-	Check printer cable(s) to ensure it is properly plugged in.

-	Verify that there is sufficient free space on disk to write file.

-	Verify that destination directory is not a read only network directory.


Invalid version of .MDF file.
Message #2203 Invalid version of .MDF file.

Possible Causes:

-	Specified MDF was compiled under a later version of JetForm.

Corrective Action:

-	Recompile the form using the same version of JetForm-Filler as JetForm-Merge being used.

-	Use an updated version of JetForm-Filler.


Memory allocation failure.
Message #2204 Memory allocation failure.

Possible Causes:

-	Insufficient memory available for JetForm to print.

-	Currently running memory resident programs conflict with JetForm.

Corrective Action:

-	Terminate any other programs currently running or memory resident programs.


Error reading MDF file.
Message #2205 Error reading .MDF file.

Possible Causes:

-	MDF file data has become corrupted because of damaged disk media or incomplete save.

-	MDF file is being read from a diskette that has become damaged.

Corrective Action:

-	Try to load a different copy of the file or use a back-up copy if it is available.

-	Recompile the form to create a new MDF.

-	If using a diskette, verify diskette is properly inserted in the disk drive.

-	Verify that the correct drive and path are specified.


Error opening MDF file.
Message #2206 Error opening .MDF file.

Possible Causes:

-	MDF file data has become corrupted because of damaged disk media or incomplete save.

-	MDF file is being read from a diskette that has become damaged.

Corrective Action:

-	Try to load a different copy of the file or use a back-up copy if it is available.

-	Recompile the form to create a new MDF.

-	Verify diskette is properly inserted in the disk drive.

-	Verify that the correct drive and path are specified.


Invalid .MDF file.
Message #2207 Invalid .MDF file.

Possible Causes:

-	Specified file is not an MDF file.

-	MDF file data has become corrupted.

Corrective Action:

-	Check path and file name are correct.

-	Recompile the form.


Error writing to printer.
Message #2208 Error writing to printer.

Possible Causes:

-	Communication breakdown between printer and JetForm.

-	Printer jammed, out of paper, not switched on etc..

Corrective Action:

-	Check printer for errors.

-	Check printer cable(s) to verify it is properly plugged in.


No MDF file name specified.
Message #2209 No MDF file name specified.

Possible Causes:

-	No .MDF file was specified to be printed.

Corrective Action:

-	Verify that the name of the desired MDF is specified and that the file and path name are correct.


Unable to open datafile.
Message #2210 Unable to open datafile.

Possible Causes:

-	Data file data has become corrupted because of damaged disk media or incomplete save.

-	Data file path or name is incorrect.

-	Data file is being read from a diskette that has become damaged.

Corrective Action:

-	Try to load a different copy of the file or use a back-up copy if it is available.

-	If using a diskette, verify diskette is properly inserted in the disk drive.

-	Verify that the correct drive and path are specified.


Requesting too many files.
Message #2213 Requesting too many files.

Possible Causes:

-	Too many data files have been opened.

Corrective Action:

-	Close one or more data file.


Recursive file open request.
Message #2214 Recursive file open request.

Possible Causes:

-	Error in logic, data file call requests itself.

Corrective Action:

-	Correct logic such that data files do not request themselves.


Data file record length out of range.
Message #2215 Data file record length is out of range.

Possible Causes:

-	Selected data file record(s) is too long for selected form.

Corrective Action:

-	Shorten data file to the correct length.

-	Recreate correct length data file in text editor.


Error reading datafile.
Message #2216 Error reading datafile.

Possible Causes:

-	Data file data has become corrupted because of damaged disk media or incomplete saving.

-	Data file path or name is incorrect.

-	Data file is being read from a diskette that has become damaged.

Corrective Action:

-	Try to load a different copy of the file or use a back-up copy if it is available.

-	If using a diskette, verify diskette is properly inserted in the disk drive.

-	Verify that the correct drive and path are specified.


No form name on '^form' command line.
Message #2217 No form name on '^form' command line.

Possible Causes:

-	No form is specified in the data file following the ^form command.

Corrective Action:

-	Verify that a form is specified following the ^form command.


Error writing to multi-part temporary file.
Message #2219 Error writing to multi-part temporary file.

Possible Causes:

-	Insufficient disk space to write out the completed temporary file.

-	Trying to write to a network drive without write privileges.

-	Trying to write to a diskette when diskette is not in the diskette drive.

Corrective Action:

--	Increase the available disk space by deleting unwanted files.

-	Change network specifications.

-	Use another diskette or disk drive with more available disk space.

-	Verify diskette is properly inserted in the disk drive and the correct drive and path are specified.


This document has no data fields to merge this data file into.
Message #2222 This document has no data fields to merge this data file into.

Possible Causes:

-	Selected form does not have any fields available to be merged into.

Corrective Action:

-	Verify that form name and path are correct.

-	Redesign and recompile form to include fields.


Multi-part MDF file has different # of pages than previous one.
Message #2223 Multi-part MDF file has different # of pages than previous one.

Possible Causes:

-	Selected multi-part MDF file has an incompatible number of pages with the previous one.

Corrective Action:

-	Verify that the selected MDF file contains the same number of pages as the previous one.


MDF file has a different multi-part mode than the previous one.
Message #2224 MDF file has a different multi-part mode than previous one.

Possible Causes:

-	Selected multi-part MDF file has an incompatible multi-part mode than the previous one.

Corrective Action:

-	Recompile the forms with the same multi-part mode.


Switching to use Non-Database (ASCII) file format.
Message #4010 Switching to use Non-Database (ASCII) file format.

Possible Causes:

-	Created a new data file after the form was loaded, and the form is not compatible with the database format.


Unable to export an unnamed document.
Message #4011 Unable to export an unnamed document.

Possible Causes:

-	A filename has not been specified.

Corrective Action:

-	Specify a filename.


Error errnum using progname to display report.
Message #4013 Error errnum using progname to display report.

Possible Causes:

-	Tried to display a report using a non-existent program name.

-	Out of memory trying to display a report.

Corrective Action:

-	Make sure that NOTEPAD.EXE is available in a directory in your path.

-	Close down other applications to free memory.


Text from file name has been stored on the clipboard. The text
Message #4014 Text from file name has been stored on the clipboard. The text may now be pasted into a text block.

Possible causes:

A file was selected to copy from.


Error reading File.
Message #5 Error Reading File

Possible Causes:

-	File data has become corrupted because of damaged disk media or incomplete saving.

-	File is being read from a diskette that has become damaged.

-	Disk drive cannot read the diskette.

-	Diskette is not in disk drive.

Corrective Action:

-	Try to load a different copy of the file or use a back-up copy if it is available. JetForm makes a backup copy of every form each time it is saved. These backups are stored in the same directory as the form file with identical file prefixes and the extension .BAK.

-	Verify diskette is properly inserted in the disk drive and the correct drive and path are specified.


Error opening the data file.
Message #5001 Error opening the datafile.

Possible Causes:

-	Data file data has become corrupted because of damaged disk media or incomplete save.

-	Data file path or name is incorrect.

-	Data file is being read from a diskette that has become damaged.

-	Attempting to access a file with insufficient privileges.

Corrective Action:

-	Verify that the correct drive and path are specified.

-	Verify that appropriate privileges have been granted.


No destination (To) name provided
Message #5002 No destination (To) name provided.

Possible Causes:

-	The To field has been left blank..

Corrective Action:

-	Complete the To field.


Error creating file of merged data
Message #5003 Error creating file of merged data.

Possible Causes:

-	Insufficient disk space.

-	Attempting to write to a drive or directory without appropriate privileges.

Corrective Action:

-	Increase available disk space by removing obsolete or unwanted files.

-	Verify that read/write/delete privileges are available for the directory identified by the TEMP variable.


Unable to find attachment
Message #5014 Unable to find attachment.

Possible Causes:

-	The attachment is not in the current directory and a complete path has not been specified..

Corrective Action:

-	Define a complete file specification for the attachment.


Invalid EMail Address
Message #5015 Invalid EMail Address.

Possible Causes:

-	An invalid destination has been specified for TO, CC, or BCC.

Corrective Action:

-	Verify entered destinations are valid.


Unable to increment SEND_INDEX field
Message #5016 Unable to increment SEND_INDEX field.

Possible Causes:

-	The value in the SEND_INDEX field could not be increased.

Corrective Action:

-	Contact Technical Support.


Cannot create another instance of JetForm for E-Mail
Message #5019 Cannot create another instance of JetForm Filler.

Possible Causes:

-	JetForm Filler is already running. Only one session can be running.

Corrective Action:

-	Use the current session.


Unable to load Language/Spelling library JFLMLIB.DLL, status: s
Message #5040 Unable to load Language/Spelling library JFLMLIB.DLL, status: status

Possible Causes:

-	A needed file is missing from the hard disk.

-	Out of memory trying to check spelling.

Corrective Action:

-	Replace the missing file.

-	Close down other applications to free memory.


Spell-checking preference missing, File: filename, Section: [se
Message #5041 Spell-checking preference missing, File: filename, Section: [section], Keyword: key

Possible Causes:

-	One or more files used by the spelling checking software are missing

-	One or more of the preferences defined by the spelling checker are missing from the JetForm .INI file.

Corrective Action:

-	Contact JetForm technical support.


Unable to initialize spell-checking system
Message #5042 Unable to initialize spell-checking system

Possible Causes:

-	The spell-checking software was unable to initialize.


Unable to read language file
Message #5043 Unable to read language file

Possible Causes:

-	One or more files used by the spelling checking software are missing

-	One or more of the preferences defined by the spelling checker are missing from the JetForm .INI file.

Corrective Action:

-	Contact JetForm technical support.


Unable to establish language for spell-checking
Message #5044 Unable to establish language for spell-checking

Possible Causes:

-	One or more files used by the spelling checking software are missing

-	One or more of the preferences defined by the spelling checker are missing from the JetForm .INI file.

Corrective Action:

-	Contact JetForm technical support.


Unable to open spell-checking file (corelex)
Message #5045 Unable to open spell-checking file (corelex)

Possible Causes:

-	One or more files used by the spelling checking software are missing

-	One or more of the preferences defined by the spelling checker are missing from the JetForm .INI file.

Corrective Action:

-	Contact JetForm technical support.


Unable to open spell-checking file (linguibase)
Message #5046 Unable to open spell-checking file (linguibase)

Possible Causes:

-	One or more files used by the spelling checking software are missing

-	One or more of the preferences defined by the spelling checker are missing from the JetForm .INI file.

Corrective Action:

-	Contact JetForm technical support.


Unable to establish spell-checking cache
Message #5047 Unable to establish spell-checking cache

Possible Causes:

-	Out of memory.

Corrective Action:

-	Close some other applications and try again.


Unable to open spell-checking file (user dictionary)
Message #5048 Unable to open spell-checking file (user dictionary)

Possible Causes:

-	One or more files used by the spelling checking software are missing

-	One or more of the preferences defined by the spelling checker are missing from the JetForm .INI file.

Corrective Action:

-	Contact JetForm technical support.


Unable to word to internal memory
Message #5049 Unable to add word to internal memory

Possible Causes:

-	Out of disk space

-	Dictionary corrupted.

Corrective Action:

-	Delete unneeded files to clear some disk space.

-	Contact JetForm technical support.


Unable to add word to user dictionary
Message #5050 Unable to add word to user dictionary

Possible Causes:

-	Out of disk space

-	Dictionary corrupted.

Corrective Action:

-	Delete unneeded files to clear some disk space.

-	Contact JetForm technical support.


Word is invalid;cannot be remembered
Message #5051 Word is invalid; cannot be remembered

Possible Causes:

-	Spell checker was not able to add the word to the dictionary.


Error writing File.
Message #6 Error Writing File.

Possible Causes:

-	File is too large for available disk space.

-	Trying to save to a network drive without write privileges.

-	Diskette is not in the diskette drive.

Corrective Actions:

-	Increase the available disk space by deleting unwanted files.

-	Change network specifications.

-	Use another diskette or drive with more available disk space.

-	Verify diskette is properly inserted in the diskette drive and the correct drive and path are specified.


DDE send data failed.  Please check receiving application.
Message #6002 DDE send data failed. Please check receiving application.

Possible Causes:

-	DDE send data failed. Please check receiving application.

Corrective Action:

-	Verify that the receiving application is active.


Unable to communicate with other application
Message #6009 Unable to communicate with other application.

Possible Causes:

-	JetForm-Merge/DDE was unable to establish DDE communication with the specified application.

Corrective Action:

-	Ensure that the application was specified correctly. You may have to include the path specification as well as the application name.


Out of Memory
Message #7 Out of Memory.

Possible Causes:

-	JetForm has run out of allocated local memory.

Corrective Action:

-	Reduce number of elements on form.

-	Contact JetForm Technical Support.


Unable to open specified file-name
Message #7001 Unable to open file-name.

Possible Causes:

-	JetForm was unable to open the indicated attachment file because of insufficient access privileges, incorrect path information or file name, or insufficient free disk space.

Corrective Action:

-	Ensure that you have privileges to access the specified file.

-	Ensure that the path information and file name specified are correct.

-	Ensure that there is sufficient free space.


Write error on E-Mail file
Message #7002 Write error on E-Mail file.

Possible Causes:

-	JetForm Filler is unable to write one of its temporary files.

Corrective Action:

-	Ensure that the TEMP variable is set to a valid drive and directory where you have privileges to read, write, and delete files.

-	Ensure that there is sufficient free disk space to create temporary files.


Write Error on E-Mail File
Message #7002 Write error on E-Mail file

Possible Causes:

-	JetForm Filler is unable to write one of its temporary files.

Corrective Action:

-	Ensure that the TEMP variable is set to a valid drive and directory where you have privileges to read, write, and delete files.

-	Ensure that there is sufficient free disk space to create temporary files.


Unable to read data file to mail.
Message #7003 Unable to read data file to mail.

Possible Causes:

-	JetForm Filler is unable to read the temporary data file which was "packed" into the .JFM attachment. This could indicate a corruption of the file on disk.

Corrective Action:

-	This could indicate a potential hardware problem. Verify the integrity of the disk.

-	It may be necessary to have the sender re-issue the mail message.


Unable to read MDF file to mail.
Message #7004 Unable to read MDF file to mail.

Possible Causes:

-	JetForm Filler is unable to read the MDF file which was "packed" into the .JFM attachment. This could indicate a corruption of the file on disk.

Corrective Action:

-	This could indicate a potential hardware problem. Verify the integrity of the disk.

-	It may be necessary to have the sender re-issue the mail message.


Unable to read CFM file to mail.
Message #7005 Unable to read CFM file to mail.

Possible Causes:

-	JetForm Filler is unable to read the CFM file which was "packed" into the .JFM attachment. This could indicate a corruption of the file on disk.

Corrective Action:

-	This could indicate a potential hardware problem. Verify the integrity of the disk.

-	It may be necessary to have the sender re-issue the mail message.


Unable to create packed file to mail.
Message #7006 Unable to create packed file to mail.

Possible Causes:

-	JetForm Filler is unable to create the "packed" data file as the .JFM attachment. This is probable due to a lack of free space on the disk.

Corrective Action:

-	Delete unwanted files to provide additional free space on the disk.


Unable to create import file for mail package
Message #7011 Unable to create import file for mail package.

Possible Causes:

-	JetForm Filler was unable to create a temporary import file for the electronic mail package. This is probably due to a lack of free space on the disk.

Corrective Action:

-	Delete unwanted files to create more free space on the disk.


Unable to open attachment
Message #7012 Unable to open attachment.

Possible Causes:

-	JetForm Filler is unable to open the specified attachment file.

Corrective Action:

-	This could indicate a hardware problem. Verify the integrity of the disk.

-	Ensure that you have sufficient privileges to access the specified attachment file.


Unable to open error message file
Message #7013 Unable to open error message file

Possible Causes:

-	The error log file for the mail package could not be found.

Corrective Action:

-	Ensure that there is sufficient free disk space for the mail package to create the error log file.

-	Check the mail package to determine if there are problems with log-in or access to the mail database.


Unable to invoke mail program
Message #7016 Unable to invoke mail program

Possible Causes:

-	The program required could not be invoked because it has not been installed or is incorrectly specified within the .INI file.

Corrective Action:

-	Verify that the program has been installed and update the .INI file if necessary.


Unable to open JFASCII file
Message #7017 Unable to open JFASCII file .

Possible Causes:

-	JetForm Filler could not open the text file for inclusion in the message. This could indicate a disk problem.

Corrective Action:

-	Verify the integrity of the disk.


Unable to log-in to mail system
Message #7018 Unable to log-in to mail system.

Possible Causes:

-	The send operation failed because of an incorrect mail user id or password.

Corrective Action:

-	Use the Log-in command to correct the mail log-in information and then send the message again.


Unable to connect to mail database
Message #7019 Unable to connect to mail database.

Possible Causes:

-	The send operation could not be completed because of incorrect specification of mail database or the mail database was inaccessible.

Corrective Action:

-	Ensure that the mail database was specified correctly.

-	Ensure that you are logged on to the network and have the correct permissions to access the mail database drive and directory.


Unable to invoke import program
Message #7020 Unable to invoke mail import program.

Possible Causes:

-	The import program required by the mail package could not be invoked because it has not been installed or is incorrectly specified within the .INI file.

Corrective Action:

-	Verify that the import program has been installed and update the .INI file if necessary.


Unable to create received data file
Message #7021 Unable to create received data file.

Possible Causes:

-	When you executed the attachment, the extract of the message data file could not be created. This is probably due to a lack of free space on the disk.

Corrective Action:

-	Delete unwanted files to create more free space on the disk.


Unable to create received MDF file
Message #7022 Unable to create received MDF file.

Possible Causes:

-	When you executed the attachment, the extract of the MDF file could not be created. This is probably due to a lack of free space on the disk.

Corrective Action:

-	Delete unwanted files to create more free space on the disk.


Unable to create received CFM file
Message #7023 Unable to create received CFM file.

Possible Causes:

-	When you executed the attachment, the extract of the CFM file could not be created. This is probably due to a lack of free space on the disk.

Corrective Action:

-	Delete unwanted files to create more free space on the disk.


Unable to read packed mail file
Message #7024 Unable to read packed mail file.

Possible Causes:

-	The entered attachment file name (.JFM) is not correct.

Corrective Action:

-	Correct the specification of the .JFM file.


Unable to invoke mail-box list program
Message #7025 Unable to invoke mail-box list program

Possible Causes:

-	The program required by the mail package could not be invoked because it has not been installed or is incorrectly specified within the .INI file.

Corrective Action:

-	Verify that the program has been installed and update the .INI file if necessary.


Mail Database error;possible corruption
Message #7033 Mail Database error; possible corruption.

Possible Causes:

-	The mail package interface DLL has indicated that there is an error condition in the mail database/post-office.

Corrective Action:

-	Use the mail package diagnostics and tools to determine and correct the problem.


Insufficient memory to carry out operation
Message #7036 Insufficient memory to carry out operation.

Possible Causes:

-	There is not enough memory available to send the message. This could be a result of too many applications open or not enough memory on the system.

Corrective Action:

-	Close some of the open applications and try again.


Attachment cannot be found
Message #7037 Attachment cannot be found

Possible Causes:

-	The attachment is not in the current directory and a complete path has not been specified.

Corrective Action:

-	Define a complete file specification for the attachment.


Mail package preference missing
Message #7038 Mail package preference missing.

Possible Causes:

-	A required setting cannot be found in the mail package's INI file (or WIN.INI). This could be due to an incomplete installation of the mail package or incorrect editing of the INI file.

Corrective Action:

-	Re-install the mail package or edit the INI file to correct the error.


Unable to communicate with mail program.
Message #7039 Unable to communicate with mail program.

Possible Causes:

-	The mail package interface DLL cannot communicate with the mail program during the attempt to send a message.

Corrective Action:

-	Refer to the documentation provided with the mail package and correct the error.


Unknown recipient;cannot send message
Message #7040 Unknown recipient; cannot send message.

Possible Causes:

-	The message contains an invalid recipient name on the form or the Send dialog.

Corrective Action:

-	Determine which recipient is invalid, make the correction, and re-send the message. Use the mail package's addressing tools if possible.


Disk is full;cannot send message
Message #7041 Disk is full; cannot send message.

Possible Causes:

-	The mail package has indicated that the local disk or the mail database/post-office disk is full and the message cannot be sent.

Corrective Action:

-	Remove unwanted files from the disk to create free space.


Text is too large;cannot send message
Message #7042 Text is too large; cannot send message.

Possible Causes:

-	The text of the message (text entered as text note and/or ASCII version of the form) is too large for the mail package to handle.

Corrective Action:

-	Reduce the amount of text entered as the text note and/or disable the "Generate Text Message" mail option.


Too many attached files;cannot send message
Message #7043 Too many attached files; cannot send message.

Possible Causes:

-	The message includes more attachments than the mail package can handle.

Corrective Action:

-	Reduce the number of attachments included with the message. Note that the form is an attachment.


Too many recipients;cannot send message
Message #7044 Too many recipients; cannot send message.

Possible Causes:

-	The message includes more recipients than the mail package can handle.

Corrective Action:

-	Reduce the number of recipients of the message.


Unknown recipient name
Message #7045 Unknown recipient name.

Possible Causes:

-	Invalid recipient name specified on the form or the Send dialog.

Corrective Action:

-	Correct the invalid name and re-send the message. Use the mail package's addressing tools if possible.


Unable to read receipt information file to mail
Message #7047 Unable to read receipt information file to mail

Possible Causes:

-	JetForm Filler is unable to read the receipt information which was "packed" into the .JFM attachment. This could indicate a corruption of the file on disk.

Corrective Action:

-	This could indicate a potential hardware problem. Verify the integrity of the disk.

-	It may be necessary to have the sender re-issue the mail message.


Unable to create receipt information file
Message #7048 Unable to create receipt information file

Possible Causes:

-	File is too large for available disk space.

-	Trying to write to a network drive without write privileges.

-	Diskette is not in the diskette drive.

Corrective Actions:

-	Increase the available disk space by deleting unwanted files.

-	Change network specifications.

-	Use another diskette or disk drive with more available disk space.

-	Ensure diskette is properly inserted in the disk drive and the correct drive and path are specified.


No E-Mail DLL specified in JFEMAIL.INI
Message #710 No E-Mail DLL is specified.

Possible Causes:

-	The initialization file does not have the required mail interface DLL preference (VendorDLLName in the section [JfEMail - system]). This could be due to an incomplete installation of JetForm Filler or incorrect editing.

Corrective Action:

-	Reinstall JetForm Filler or correct the error.


No E-Mail system specified in JFEMAIL.INI
Message #7104 No E-Mail system is specified.

Possible Causes:

-	.INI file does not have the required mail system preference (EMailSystem in the section [JfEMail]). This could be due to an incomplete installation of JetForm Filler or incorrect editing.

Corrective Action:

-	Reinstall JetForm Filler or correct the error.


No E-Mail DLL has been specified in the JFEMAIL.INI file
Message #7105 No E-Mail DLL has been specified.

Possible Causes:

-	.INI file does not have the required mail interface DLL preference (VendorDLLName in the section [JfEMail - system]). This could be due to an incomplete installation of JetForm Filler or incorrect editing.

Corrective Action:

-	Reinstall JetForm Filler or correct the error.


Unable to load E-Mail library
Message #7106 Unable to load E-Mail library name; Error number.

Possible Causes:

-	The mail interface DLL specified in .INI file cannot be loaded. This could be due to an incomplete installation of JetForm Filler, incorrect editing, or too many applications are running.

Corrective Action:

-	Reinstall JetForm Filler, correct the error, or close idle applications.


No connection to the mail system has been established
Message #7107 No connection to the mail system has been established.

Possible Causes:

-	Mail interface DLL appears to have been called in the incorrect sequence.

Corrective Action:

-	Contact JetForm Technical Support.


Unknown mail system error number
Message #7108 Unknown mail system error number.

Possible Causes:

-	The mail system has reported an unusual error condition.

Corrective Action:

-	Contact JetForm Technical Support.


JFASCII.DLL does not have correct format
Message #7109 The JFASCII.DLL library does not have the correct format.

Possible Causes:

-	Incorrect installation of JetForm Filler or subsequent corruption of the file.

Corrective Action:

-	Re-install JetForm Filler. If the problem persists, contact JetForm Technical Support.


Cannot save form to filename
Message #7111 Cannot save form to filename.

Possible Causes:

-	The form file could not be saved during a Save Form operation.

Corrective Action:

-	Ensure that there is sufficient free disk space and that you have the appropriate permissions to create a file on the target drive/directory.


You must save at least one file
Message #7112 You must save at least one file.

Possible Causes:

-	In the Save Form dialog, you have disabled both the options to save the MDF file and the CFM file.

Corrective Action:

-	You must select at least one file type to save or cancel the command.


Mail package specific error text
Message #7117 Mail package specific error text.

Possible Causes:

-	An unusual mail package specific error has occurred.

Corrective Action:

-	Refer to the documentation provided with the mail package to determine the cause and/or solution to the problem.


Error Creating File.
Message #8 Error Creating File.

Possible Causes:

-	File is too large for available disk space.

-	Trying to write to a network drive without write privileges.

-	Diskette is not in the diskette drive.

Corrective Actions:

-	Increase the available disk space by deleting unwanted files.

-	Change network specifications.

-	Use another diskette or disk drive with more available disk space.

-	Verify diskette is properly inserted in the disk drive and the correct drive and path are specified.


Page does not exist.
Message #9 Page does not exist.

Possible Causes:

-	Page does not exist.

Corrective Action:

-	Verify file and page specified are correct.


Save current changes : Filename.
Message #915 Save current changes : Filename.

Possible Causes:

-	File has been altered since it was last saved; current changes will be lost unless saved.


You must specify a Filename.
Message #916 You must specify a Filename.

Possible Causes:

-	A filename has not been specified.

Corrective Action:

-	Specify a filename.


Replace existing Filename?
Message #923 Replace existing Filename?

Possible Causes:

-	A file already exists with the specified filename.

Corrective Action:

-	Click on OK to overwrite existing file or change filename.


Invalid number of copies
Message #928 Invalid number of copies.

Possible Causes:

-	A non-numeric value was entered in the Copies text box.

Corrective Action:

-	Replace the entered value with a numeric value.


Unable to output to the clipboard.
Message #929 Unable to output to the clipboard.

Possible Causes:

-	Windows clipboard is not available.

-	Selected data is too large to fit on clipboard.

Corrective Action:

-	Verify Windows clipboard is properly installed (see Windows manual).

-	Select smaller quantity of data to be copied to clipboard.


There are no fields to prompt for.
Message #935 There are no fields to prompt for.

Possible Causes:

-	No fields were included on the form when is was designed.

-	All fields on the form are protected or are calculated fields and will not accept user input.

-	Form was compiled with option to 'Include prompt information' switched off.

Corrective Action:

-	Redesign form to include fields.

-	Change attributes of fields on the form.

-	Recompile the form and verify that 'Include prompt information' is switched on.


Invalid Page name.
Message #936 Invalid Page name.

Possible Causes:

-	Specified page name is invalid.


There is no help text for this field.
Message #937 There is no help text for this field.

Possible Causes:

-	No help text was specified for this field when it was designed.


Already at the first record in the data file.
Message #938 Already at the first record in the data file.

Possible Causes:

-	Currently at the first record in the data file.


Already at the last record in the data file.
Message #939 Already at the last record in the data file.

Possible Causes:

-	Currently at the last record in the data file.


Invalid data record requested
Message #940 Invalid data record requested.

Possible Causes:

-	Record requested does not exist or is invalid.

Corrective Action:

-	Verify that selected record is correct.


No data file is currently open. Select File/Open or File/New.
Message #941 No data file is currently open. Select File/Open or File/New.

Possible Causes:

-	JetForm does not have a data file type specified.

-	A File - Open was canceled.

-	A File - New was canceled.

-	A requested file was not found.

Corrective Action:

-	Open a data file by selecting File - Open.

-	Select File - New to create a new data file.


Invalid macro number.
Message #948 Invalid macro number.

Possible Causes:

-	Invalid characters were entered as macro number such as letters, extended characters, etc..

Corrective Action:

-	Verify macro number only contains numbers.


A data file must be given.
Message #949 A data file must be given.

Possible Causes:

-	No data file was specified for merging with form.

Corrective Action:

-	Specify a data file or turn off merge option.


Invalid flag 'Flag' on the command line.
Message #950 Invalid flag 'Flag' on the command line.

Possible Causes:

-	Flag entered on command line is invalid.

Corrective Action:

-	Verify that the command line syntax is correct.


No data file should be included for this merge mode.
Message #951 No data file should be included for this merge mode.

Possible Causes:

-	A data file name was included when the No Data Mode was selected.

Corrective Action:

-	Either switch off No Data Mode or do not specify a data file.


Help file not found.
Message #953 Help file not found.

Possible Causes:

-	Help files could not be found by JetForm.

Corrective Action:

-	Copy help files into JetForm directory.

-	Re-install JetForm.


Unable to read the configuration data form the .MDF file.
Message #959 Unable to read configuration data from the .MDF file.

Possible Causes:

-	MDF file data has been corrupted.

-	MDF file not compatible with this version of JetForm-Filler/G.

Corrective Action:

-	Use backup copy of MDF file.

-	Recompile MDF file.


Unable to create an Atom.
Message #960 Unable to create ATOM.

Possible Causes:

-	A problem has been found with the internal file structure

Corrective Action:

-	Contact technical support.


Invalid ATOM identifier (Hex = 'Hexvalue' - Value = 'Value').
Message #961 Invalid ATOM identifier (Hex = Hex - Value = 'Value').

Possible Causes:

-	A problem has been found with the internal file structure.

Corrective Action:

-	Contact technical support.


You are not authorized to use this program
Message #962 You are not authorized to use this program

Possible Causes:

-	you are not running an authorized version of the JetForm software

Corrective Action:

-	purchase an authorized version of the software


Error updating 'Section' section of 'INIFILE.INI.
Message #964 Error updating 'Section' Section 'INIFILE.INI'.

Possible Causes:

-	Cannot find INIFILE.INI in the Windows directory.

-	INIFILE.INI is write protected or is on a network drive that is write protected

Corrective Action:

-	Copy INIFILE.INI into the Windows directory.

-	Change file or network attributes.


Error writing to spool file. Print cancelled.
Message #965 Error writing to spool file. Print cancelled.

Possible Causes:

-	Spooler is not working properly with JetForm.

-	Insufficient disk space to write spooler file.

Corrective Action:

-	If disk is full delete unwanted files.

-	Attempt to print again to the spooler. If problem persists, print without the spooler.


No fields on page Pagenumber of this multi-part document.
Message #966 No fields on a page in multi-part document.

Possible Causes:

-	No fields exist on a page in the document.


No fields in this document.  Cannot print in field mode.
Message #967 No fields in this document. Cannot print in field mode.

Possible Causes:

-	No fields at all in the document therefore JetForm cannot print in field merge mode.


Field 'fieldname' - Unknown function call in expression 'expres
Message #971 Field 'fieldname' - Unknown function call in expression 'expression'.

Possible Causes:

-	Function call in the calculation or validation of the specified field was not recognized by JetForm.

Corrective Action:

-	Verify that the syntax of the specified calculation is correct.


Incorrect number of arguments for function
Message #972 Field 'fieldname' - Incorrect number of arguments to function call in expression 'expression'.

Possible Causes:

-	Function call in the calculation or validation of the specified field was not recognized by JetForm.

-	Syntax in calculation/validation of specified fields has too few or too many arguments.

Corrective Action:

-	Verify that the syntax of the specified calculation is correct.


Error accessing database 'database' using index 'index'.
Message #977 Error accessing database 'database' using 'index'.

Possible Causes:

-	Database file path or file name was entered incorrectly in the field calculation.

-	Database file specified cannot be found by JetForm in the JetForm directory.

-	Database file specified cannot be found in the path defined in the field calculation.

-	Database index file path or file name was entered incorrectly in the field calculation.

Corrective Action:

-	Change file and/or path name to point to the directory containing database file and/or index.

-	Copy the database file and/or index into the directory or drive specified in field calculation or validation.


Error opening database 'database'.
Message #978 Error opening database 'database'.

Possible Causes:

-	Database path or file name was entered incorrectly in the field calculation.

-	Database file specified cannot be found by JetForm in the JetForm directory.

-	Database file specified cannot be found in the path defined in the field calculation.

Corrective Action:

-	Change file and/or path name to point to the directory containing database file.

-	Copy the database file into the directory or drive specified in field calculation or validation.


Error opening database index file 'index'.
Message #979 Error opening database index file 'index'.

Possible Causes:

-	Database index file path or file name was entered incorrectly in the field calculation.

-	Database index file specified cannot be found by JetForm in the JetForm directory.

-	Database index file specified cannot be found in the path defined in the field calculation.

-	Database index file has become corrupted.

Corrective Action:

-	Change index file and/or path name to point to the directory containing database index.

-	Copy the database file index into the directory or drive specified in field calculation or validation.

-	Use a backup copy of the index file.


Index value 'index' not found in database 'database'.
Message #980 Index value 'index' not found in database 'database'.

Possible Causes:

-	Index value specified could not be found in the specified database.

Corrective Action:

-	Verify that index value is correctly spelled.

-	Verify that JetForm is accessing the correct database.


Invalid value based on validation rule: Rule.
Message #981 Invalid value based on validation rule: Rule.

Possible Causes:

-	Data entered into field violates the specified validation rule.


Invalid data for numeric field.
Message #982 Invalid data for numeric field.

Possible Causes:

-	This field was specified a numeric field when it was designed and compiled and will only accept numeric data.

Corrective Action:

-	Enter only numeric data into the field.

-	Change field specification in JetForm-Design and recompile the form.


Not enough characters for field.
Message #983 Not enough characters for field.

Possible Causes:

-	The picture attribute for the field specified a specific number of characters when the form was designed and compiled.

Corrective Action:

-	Enter the required number of characters into the field.

-	Change field 'Picture' attribute in JetForm-Design and recompile the form.


Character must be a digit.
Message #984 Character must be a digit.

Possible Causes:

-	The Picture attribute specified when this field was designed and compiled requires that a number be entered in this field.

Corrective Action:

-	Enter only numeric data into the field.

-	Change field Picture attribute in JetForm-Design and recompile the form.


No data entered for mandatory field.
Message #985 Field 'fieldname' is a mandatory field. Some character(s) must be entered.

Possible Causes:

-	This field was specified a mandatory field when the form was designed and compiled. This requires that user enter some character(s).

Corrective Action:

-	Enter some character(s) into the field.

-	Change field specification in JetForm-Design and recompile the form.


Begin overriding the calculation of this field 'fieldname'.
Message #986 Begin overriding the calculation of this field 'fieldname'.

Possible Causes:

-	User is attempting to override a field value calculation. To override the calculation, click on Override. To cancel, click on No.


Continue to override the calculation of this field 'fieldname'.
Message #987 Continue to override the calculation of this field 'fieldname'.

Possible Causes:

-	User is attempting to replace calculated field value.


Unable to load database access library: 'library'.
Message #988 Unable to load database access library: 'library'.

Possible Causes:

-	Database access files could not be found in the JetForm directory.

-	There was insufficient memory available for JetForm to load the database access library.

Corrective Action:

-	Verify that the identified file is in the JetForm directory and if not, copy it into the directory (this may require re-installing JetForm).

-	Close down any unnecessary Windows applications to increase the available memory.


Error initializing database access library: 'library'.
Message #989 Error initializing database access library: 'library'.

Possible Causes:

-	Database access files could not be found in the JetForm directory.

-	There was insufficient memory available for JetForm to load the database access library.

-	SHARE was not loaded.

Corrective Action:

-	Verify that the identified file is in the JetForm directory and if not, copy it into the directory (this may require re-installing JetForm).

-	Close down any unnecessary Windows applications to increase the available memory.

-	Exit Windows, run SHARE.EXE, and restart Windows.


Too many different type of databases in use.  Maximum is 'maxim
Message #990 Too many different types of databases in use. Maximum is 'maximum'.

Possible Causes:

-	User is attempting to use too many different types of databases at once.

Corrective Action:

-	Reduce the number of type of databases used by the form.


Extension must be supplied for 'Other Database'.
Message #991 Extension must be supplied for 'Other Database'.

Possible Causes:

-	No extension has been given for the 'other database'.

Corrective Action:

-	Provide JetForm with the necessary extension for the 'other database'.


Field 'fieldname' has a calculation which contains a circular f
Message #992 Field 'fieldname' has a calculation which contains circular field references.

Possible Causes:

-	Error in field calculation logic where a field refers to itself in its calculation.

-	Error in field calculation logic where two or more fields reference each other within their calculations.

Corrective Action:

-	Change field calculations to correct logic.


Field 'fieldname' is not in the data file.  Field dropped.
Message #993 Field 'fieldname' is not in the data file. Field dropped.

Possible Causes:

-	Identified field is not in the datafile (Note that this will not affect the printing of the of the remainder the form)

Corrective Action:

-	Edit data file to include field call for specified field.


Field name 'fieldname' occurs more than 128 times.  Cannot prom
Message #993 Field name 'fieldname' occurs more than 128 times. Cannot prompt this document.

Possible Causes:

-	JetForm will only allow up to 128 occurrences of the same field on a form when prompting.

Corrective Action:

-	Reduce the number of fields with the same name by changing names or deleting fields.


Occurrence 'occurrencenumber' of field 'fieldname' is not in th
Message #994 Occurrence 'occurrencenumber' of field 'fieldname' is not in the data file. Field dropped.

Possible Causes:

-	Identified field occurrence is not in the datafile (Note that this will not effect the printing of the of the remainder the form)

Corrective Action:

-	Edit data file to include field call for specified field.


First record number must be between firstrecord and lastrecord.
Message #996 First record number must be between firstrecord and lastrecord.

Possible Causes:

-	The specified starting record is outside the available range of records.

-	The specified starting record is after the ending record.

Corrective Action:

-	Enter a starting record that is within the available range.


Last record number must be between firstrecord and lastrecord.
Message #997 Last record number must be between firstrecord and lastrecord.

Possible Causes:

-	The specified ending record is outside the available range of records.

-	The specified ending record is before the starting record.

Corrective Action:

-	Enter an ending record that is within the available range.


There are no records in the current data file.
Message #998 There are no records in the current data file.

Possible Causes:

-	No records have been filled in the currently open data file.


Data file cannot be printed without compiling in Prompt informa
Message #999 A data file cannot be printed without having compiled the prompt information in.

Possible Causes:

-	Form was compiled without including the Prompt information.

Corrective Action:

-	JetForm cannot print from a database unless prompt information has been included in the form. Recompile form and include Prompt information.


Unsigned field contains data
Message #1984 - Unsigned field contains data

Possible Causes:

-	Signature field contains data but the field does not contain any of the internal signature verification information required to validate the signature.

Corrective Action:

-	None. Signature will be treated as invalid. Ensure that the data has not been tampered.


Unable to load printer driver
Message #2015 Unable to load printer driver

Possible Causes:

-	Printer driver could not be found in the JetForm directory.

-	There was insufficient memory available for JetForm to load the printer driver

Corrective Action:

-	Verify that the identified file is in the JetForm directory and if not, copy it into the directory (this may require re-installing JetForm).

-	Close down any unnecessary Windows applications to increase the available memory.


Font not found in .CFG file
Message #2054 Font not found in DRIVER.CFG file

Possible Causes:

-	A typeface configured for the default Windows printer could not be matched in the identified .CFG file. This is only a warning.


Error allocating memory
Message #4001 Error allocating memory

Possible Causes:

-	Windows has run out of available memory.

Corrective Action:

-	Close other windows to free up memory.


Unable to enumerate printer fonts
Message #4008 Unable to enumerate printer fonts.

Possible Causes:

-	Printer font information could not be retrieved from the print driver for the Windows default printer.

Corrective Action:

-	The print driver may be incompatible or out-of-date for the version of Windows. Re-install the printer through the Windows Control Panel.


Operation Failed
Message #6008 Operation Failed

Possible Causes:

-	Operation failed.

Corrective Action:

-	Contact technical support.


Unable to create communication structure
Message #6010 DDE - Unable to create communication structure

Possible Causes:

-	Unable to create communication structure.

Corrective Action:

-	Contact Technical Support.


Advisory already established
Message #6013 DDE - Advisory already established

Possible Causes:

-	Advisory already established.

Corrective Action:

-	Contact technical support.


Unable to load printer font data
Message #968 Error loading font information into memory

Possible Causes:

-	Windows has run out of available memory.

Corrective Action:

-	Close other windows to free up memory.


Cannot extract default Windows printer information
Message #1252 Cannot extract the Windows default printer information

Possible Causes:

-	The required printer information could not be obtained for the default Windows printer.

Corrective Action:

-	Ensure your Windows default printer is correctly configured.

-	Verify your default printer setup with other Windows applications such as Notepad or Write.


Save current changes?
Message #1802 Save current changes?

Possible Causes:

-	Selecting Exit without saving changes made to the currently open object.

Corrective Action:

-	Select Yes to save changes.

-	Select No to exit without saving.


You must enter an object title
Message #1805 You must enter an object title

Possible Causes:

-	The object title has been left blank.

Corrective Action:

-	Enter an object title.


Field already signed
Message #1976 This field has already been signed; you cannot sign it again.

Possible Causes:

-	The signature field is signed.


Field is not signed;cannot unsign it.
Message #1977 This field is not signed; you cannot unsign it.

Possible Causes:

-	You cannot unsign a field that is not signed.


Signature not found
Message #1979 Signature not found

Possible Causes:

-	Signature could not be found in the Signature Verification File.

Corrective Action:

-	Contact the Signature Administrator.


You must enter a new password
Message #1980 You must enter a new password

Possible Causes:

-	A new password was not specified.

Corrective Action:

-	Enter a new password.


The passwords don't match
Message #1981 The passwords do not match

Possible Causes:

-	The new passwords do not match.

Corrective Action:

-	Re-enter the new passwords.


Signature is locked by another signature
Message #1982 Signature is locked by another signature

Possible Causes:

-	Cannot unsign a field that is locked by another signature.

Corrective Action:

-	Field must be unlocked by signatory of locking field.


.CFG file not found for JetForm Driver printing
Message #2053 .CFG file not found for JetForm Driver printing

Possible Causes:

-	The .CFG file which matches your default Windows printer type is not in the JetForm configuration directory.

Corrective Action:

-	Use Printer Setup to choose Windows Configuration, Windows Printing.

-	Install the JetForm Print Driver which corresponds to your default Windows printer. (Run the JetForm SETUP program again, select the printer driver, and switch off Full Install).


Message #8002 Ascii/Merge: Missing form name

Possible Causes

Corrective Action:

Message #8001 Ascii/Merge: Ran out of memory

Possible Causes

Corrective Action:

Message #8003 Ascii/Merge: I/O error

Possible Causes

Corrective Action:

Message #8004 Ascii/Merge: Bad layout in Form File

Possible Causes

Corrective Action:

Message #8005 Ascii/Merge: Unknown field in data file

Possible Causes

Corrective Action:

Message #8007 Ascii/Merge: Invalid parameters

Possible Causes

Corrective Action:

Message #8008 Ascii/Merge: A file open failed

Possible Causes

Corrective Action:


Message #9010 Column number was not selected in rule #1.

Possible Causes

A database select rule is improperly constructed. Its syntax references columns which should be selected in rule #1, however, those columns are not selected in rule #1.

Corrective Action:

Correct the database select rule form design to either add more columns to those being selected in rule #1 or correct the references to rule #1 columns in the subsequent select rules.


ERROR TYPE 0

0  Basic OLE Errors

-1	Relatively catastrophic failure

1	Not implemented

2	Ran out of memory

3	One or more arguments are invalid

4	No such interface supported

5	Invalid pointer

6	Invalid handle

7	Operation aborted

8	Unspecified error

9	General access denied error


ERROR TYPE 1

1  Remote Procedure Call Errors

1	Call was rejected by callee

2	Call was canceld by call - returned by MessagePending this code only occurs if MessagePending return cancel

3	The caller is dispatching an intertask SendMessage call and NOT call out via PostMessage

4	The caller is dispatching an asynchronus call can NOT an outgoing call on behalf of this call

5	The caller is not in a state where an outgoing call can be made is the case if the caller has an outstandig call and incoming call was excepted by HIC; now the caller is allowed to call out again

6	The connection terminated or is in a bogus state can not be used any more. Other connections still valid.

7	The callee (server [not server application]) is not available disappeared; all connections are invalid

8	The caller (client ) disappeared while the callee (server) was a call

9	The data packet with the marshalled parameter data is incorrect

10	The call was not transmitted properly; the message queue full and was not emptied after yielding

11	The client (caller) can not marshall the parameter data unmarshall the return data - low memory etc.

12	The client (caller) can not marshall the parameter data unmarshall the return data - low memory etc.

13	The server (caller) can not unmarshall the parameter data marshall the return data - low memory

14	The server (caller) can not unmarshall the parameter data or marshall the return data - low memory

15	Received data are invalid; can be server or data

16	A particular parameter is invalid and can not be un/marshalled

17	DDE conversation - no second outgoing call on same channel

-1	An internal error occured


ERROR TYPE 2

Dispatch Related Errors

1  UNKNOWNINTERFACE

3  MEMBERNOTFOUND

4  PARAMNOTFOUND

5  TYPEMISMATCH

6  UNKNOWNNAME

7  NONAMEDARGS

8  BADVARTYPE

9  EXCEPTION

10 OVERFLOW

11 BADINDEX

12 UNKNOWNLCID

13 ARRAYISLOCKED

14 BADPARAMCOUNT

15 PARAMNOTOPTIONAL

16 BADCALLEE

17 NOTACOLLECTION

32790  BUFFERTOOSMALL

32792  INVDATAREAD

32793  UNSUPFORMAT

32796  REGISTRYACCESS

32797  LIBNOTREGISTERED

32807  UNDEFINEDTYPE

32808  QUALIFIEDNAMEDISALLOWED

32809  INVALIDSTATE

32810  WRONGTYPEKIND

32811  ELEMENTNOTFOUND

32812  AMBIGUOUSNAME

32813  NAMECONFLICT

32814  UNKNOWNLCID

32815  DLLFUNCTIONNOTFOUN

35005  BADMODULEKIND

35013  SIZETOOBIG

35014  DUPLICATEID

36000  TYPEMISMATCH

36001  OUTOFBOUNDS

36002  IOERROR

36003  CANTCREATETMPFILE

40010  CANTLOADLIBRARY

40067  INCONSISTENTPROPFUNCS

40068  CIRCULARTYPE


ERROR TYPE 3

Storage Errors

DOS storage errors

1  INVALIDFUNCTION

2  FILENOTFOUND

3  PATHNOTFOUND

4  TOOMANYOPENFILES

5  ACCESSDENIED

6  INVALIDHANDLE

8  INSUFFICIENTMEMORY

9  INVALIDPOINTER

18 NOMOREFILES

19 DISKISWRITEPROTECTED

25 SEEKERROR

29 WRITEFAULT

30 READFAULT

32 SHAREVIOLATION

33 LOCKVIOLATION

80 FILEALREADYEXISTS

87 INVALIDPARAMETER

112 MEDIUMFULL

250 ABNORMALAPIEXIT

251 INVALIDHEADER

252 INVALIDNAME

253 UNKNOWN

254 UNIMPLEMENTEDFUNCTION

255 INVALIDFLAG

OLE storage errors

256 INUSE

257 NOTCURRENT

258 REVERTED

259 CANTSAVE

260 OLDFORMAT

261 OLDDLL

262 SHAREREQUIRED

263 NOTFILEBASEDSTORAGE

264 EXTANTMARSHALLINGS


ERROR TYPE 4

Errors Used By OLE

By convention, OLE interfaces divide the range of errors into nonoverlapping subranges.  If an OLE interface returns an error type 4, it must be from the range associated with that interface or from the shared range: 0 - 255.

The error ranges and their associated interfaces are given below.

0 - 255   Generic OLE errors that may be returned by many interfaces

0	Invalid OLEVERB structure

1	Invalid advise flags

2	You can't enuemrate any more, because the associated data is missing

3	This implementation doesn't take advises

4	There is no connection for this connection id

5	Need run the object to perform this operation

6	There is no cache to operate on

7	Uninitialized object

8	Linked object's source class has changed

9	Not able to get the moniker of the object

10	Not able to bind to the source

11	Object is static, operation not allowed

12	User cancelled out of save dialog

13	Invalid rectangle

14	Compobj.dll is too old for the ole2.dll initialized

15	Invalid window handle

16	Object is not in any of the inplace active states

17	Not able to convert the object

18	Not able to perform the operation because object is not given storage yet.

100	Invalid FORMATETC structure

101	Invalid DVTARGETDEVICE structure

102	Invalid STDGMEDIUM structure

103	Invalid STATDATA structure

104	Invalid lindex

105	Invalid tymed

106	Invalid clipboard format

107	Invalid aspect(s)

108	The tdSize paramter of the DVTARGETDEVICE structure is invalid

109	Object doesn't support IViewObject interface

256 - 271 Drag and Drop Interface Errors

256	Trying to revoke a drop target that has not been registered

257	This window has already been registered as a drop target

258	Invalid window handle

272 - 287 Class Factory Interface Errors

272	Class does not support aggregation (or class object is remote)

273	DLL doesn't support that class (returned from DllGetClassObject)

288 - 303 Mashaling Interface Errors

304 - 319 Data Object Interface Errors

320 - 335 View Object Interface Errors

336 - 351 Registration Database Errors

336	Some error reading the registration database

337	Some error reading the registration database

338	Some error reading the registration database

339	Some error reading the registration database

340	Some error reading the registration database

341	Some error reading the registration database

352 - 367 Unknown Errors

368 - 383 Ole Cache Interface Errors

368	No Cache to update

384 - 399 Ole Object Interface Errors

384	No verbs available

385	Invalid verb

400 - 415 Ole Client Site Interface Errors

416 - 431 Visual Editting Interface Errors

416	Undo is not avaiable

417	Space for tools is not available

432 - 447 Enumerator Interface Errors

448 - 463 Storage Conversion Interface Errors

448	OLESTREAM Get method failed

449	OLESTREAM Put method failed

450	Contents of the OLESTREAM not in correct format

451	There was in an error in a Windows GDI call while converting the bitmap a DIB.

452	Contents of the IStorage not in correct format

453	Contents of IStorage is missing one of the standard streams ("\1CompObj", 1Ole", "\2OlePres000").  This may be the storage for a DLL object, or a that does not use the def handler.

454	There was in an error in a Windows GDI call while converting the DIB a bitmap.

464 - 479 Clipboard Interface Errors

464	OpenClipboard Failed

465	EmptyClipboard Failed

466	SetClipboard Failed

467	Data on clipboard is invalid

468	CloseClipboard Failed

480 - 495 Moniker Interface Errors

480	OLE needed to connect to a network device that is not available

481	A time out occurred while establishing a link or retrieving a links

482	Moniker is only available in a generic format

483	The time of last change is unavalable

484	Syntax error in filename.

485	Unable to find a required object

486	Invalid extension.  No Class ID was found and the extension is not in the registration database

487	An object was found but did not support the required interfaces

488	Incomplete moniker supplied for the operation

489	Tried to revoke an object that was not bound

490	Can not open file

491	The operation could not succeed without user intervention

492	Could not retrieve the Relative path of the moniker

493	No storage associated with the given object

494	No common prefix with the given monikers

496 - 511 Component Object API Errors

496	CoInitialize has not been called and must be

497	CoInitialize has already been called and cannot be called again (temporary)

498	Can't determine clsid (e.g., extension not in reg.dat)

499	The string form of the clsid is invalid (including ole1 classes)

500	The string form of the iid is invalid

501	Application not found

502	Application cannot be run more than once

503	Some error in the app program file

504	DLL not found

505	Some error in the dll file

506	App written for other version of OS or other OS altogether

507	Object is not registered

508	Object is already registered

509	Handler is not connected to server

510	App was launched, but didn't registered a class factory

512 >>    Undefined Errors