# filePro Error Messages

Code | Description
001 | File not found You may be trying to reference a file that has never existed, has been renamed or has been deleted from the system. Return to processing table and check the name for typographical errors.
002 | No or invalid map A disk drive error occurred while the program was reading or saving the map file. You may have to rewrite or re-save the file format using Define Files.
003 | Sentence contains too many selection sets. Maximum is 5. You can reference no more than five sets in any one selection sentence.
004 | Group not found in selection set. You mistyped a group or set name, listed a group or set that was never defined or used the restricted words "AND" or "OR" in your group names. Check your group names and list of selection sets using the filePro directory option.
005 | Selection sentence too complex. There are too many groups and sets involved. Simplify your sentence.
006 | Process contains a syntax error at position indicated. This error occurs when running a syntax check or when running a program if you didn't check the syntax of the processing table. The line of processing containing the error will have a caret "^" beneath the point of the error. If there appears to be no error at the point of the "^", check for errors preceding the caret. Another difficult thing to spot is an "undefined" dummy variable. The "^" will point to the undefined variable. The error will also occur when in Inquire,Update,Add and a lookup variable is not found. Example: 1=cust(2) ^ In this case, field 2 in cust was not found. Make sure that you have included a NOT condition to prevent this error when the value cannot be found in the lookup file. Example: If: NOT cust Then: END
007 | Invalid selection set. You have somehow named a set incorrectly or used the wrong selection set name on a command line. Check the list of selection set names using the filePro directory option.
008 | Selection contains self-reference. In the selection sentence. You have typed the name of a set you are currently defining or you have referred to a set that, in turn, refers to this set. Check your selection set names using the filePro directory option.
009 | Error in termcap file. Alert your system administrator. LINUX/UNIX/XENIX versions of filePro: The termcap file (the file that contains information on the types and configuration of the terminals attached to your system) has an error in it. The file /appl/fp/termcap applies. Correct the file or restore from a backup.
010 | Terminal type not found. Alert your system administrator. LINUX/UNIX/ZENIX versions of filePro: The termcap file may be missing an entry for your terminal type. Either add the terminal type or set the terminal type to a different termcap entry that exists in /appl/fp/termcap.
011 | Required terminal feature not available. Alert your system administrator. Either a feature (for example a hardware instruction that clears the screen) or crucial configuration information (for instance - how to position the cursor) is missing. Refer to your system manuals and procedures on how to correct the problem.
012 | Standard i/o has been redirected. You have redirected input or output incorrectly on the command or menu action line. You will not be able to run the filePro program until the redirection problem is resolved.
013 | Too many filePro files open at once. Maximum is 60. You are looking up form or posting to too many files. Rewrite the process. Note that although you can use up to 60 files with filePro, the operating system can impose limitations. Although filePro closes some files when no longer needed, it cannot close all of them so the system limit could be exceeded.
014 | Out of memory. The Central Processing Unit (CPU) doesn't have enough RAM to handle the filePro operation or program. You may need to add more memory to the unit or tune your system. Refer to minimum system and configuration requirements.
015 | Processing tables element too complex. Simplify your processing.
016 | Too many lookups. Maximum is 32 per processing set.
017 | Automatic index too unbalanced. Run Index Maintenance to rebuild the index.
018 | Disk error. This error usually indicates a hardware problem. Refer to your computer's operations manual.
019 | Invalid index. Run Index Maintenance to rebuild the index or delete the invalid index.
020 | Lookup failed. Correct the key field(s) and try again. While processing, the program could not find the record needed for the lookup. Check that you are using the right cross-reference data and that the data is listed in the lookup file. Also make sure that you are trapping for the non-existence of a data value by using a NOT condition following the lookup.
021 | Checksum error: Format has been illegally modified. Either someone has tried to change the format from outside filePro or someone has made a copy of a format under another name and you have accessed the new copy. Re-create the format using the relevant filePro creation program.
022 | Incorrect password. You have typed a password incorrectly for the third time. When you press <RETURN>, you are returned to the menu item from which you came.
023 | Can't do this in automatic processing. Operation at position indicated is allowed in input processing only.
024 | Bad assignment at position indicated. Indicates a mismatch in field assignments. For example, you are trying to post data to a system maintained field or trying to move data from one field to another with a incompatible field type e.g. moving a date from a date field to a decimal field. Correct the processing table.
025 | Invalid screen format. Something is called "screen.n" but is not a valid filePro screen. Try re-saving the screen using Define Screens. If that doesn't correct the problem, delete the invalid screen from the operating system prompt or in Define Screens.
026 | Math overflow. This error occurs when you are attempting to perform math on non-numeric fields or have exceeded the limits of the math functions.
027 | Bad argument on command line You have a logical or typographical error on your command line. The "command line" is the line on which you type program names and parameters (file, selection set names, etc.) when defining user menus or when accessing programs from the operating system prompt.
028 | Invalid field in processing set. The field being used for a lookup doesn't exist. Correct the field number.
029 | Invalid index in processing set. The index being used for a lookup doesn't exist. Either build the index or change the index number/letter in Define Processing to refer to a valid index. Also, the program may have too many open files. Increase the number of files by setting the PFFILES variable.
030 | Lookup without a field. The lookup has been defined without specifying the field to be used. This error occurs in Define Processing. You forgot the key-field number. Use the Define Lookups option key to prevent this type of mistake.
031 | Required index hasn't been specified. You forgot to put your index number/letter in your LOOKUP statement. Use the define lookups key <F5> to avoid this error.
032 | Goto destination not found. You have misspelled or forgot to define the label that a GOTO or GOSUB statement is suppose to access.
033 | Not available. Somebody else is using it; try again later. You have attempted to modify a format while somebody else is using it or somebody else is modifying the same format. This error may also occur if the system is reset, in the middle of modifying a format or when files are open. Refer to UNLOCK procedures.
034 | User edit too complex. The edit is referencing itself or is nested too deeply. (A nested edit is one that refers to a second edit type that refers to a third edit etc.). Correct by simplifying the edit. The nesting limits are 15 for DOS; 20 for LINUX,UNIX,XENIX.
035 | Edit name not found. This error occurs in Define Edits. You have referenced an edit that does not exist. Check the list of global and local edits for the existence of the edit and typographical errors.
036 | Incomplete file. A disk drive error may have occurred while you were changing and/or saving a file. Have you had recent hardware problems? You may have to restore data from backups or rewrite your formats.
037 | Selection sentence contains a syntax error at position indicated. This message occurs when you have a selection set containing a syntax error. Fix the problem at the specified position.
038 | Not a menu. You have attempted to use a corrupted menu or a file that is not a menu.
039 | Field not found. Lookup has not been performed. This error occurs in Inquire,Update,Add or Request Output when the processing table is written in such a way that the program skips the lookup. For example, you may have a GOTO in the wrong place or be using the same destination file name for two separate lookups. The error can also occur when using LOOKUP -N ("don't report an error") without checking to see if the lookup failed.
040 | Edit type not found. This error occurs when defining dummy fields in processing tables and when accessing the file in Inquire,Update,Add. You have listed an edit type that doesn't exist or your PFGLOB variable is set wrong. Update the edit table using Define Edits, change the edit type used for the field in Define Files or correct the PFGLOB variable setting.
041 | File not available. Somebody else is modifying the file; try again later. You cannot run the requested program while someone else is modifying the file. This error occurs when the system is inadvertently shutdown while filePro files are open or a session is not properly closed when in a window. Refer to UNLOCK procedures.
042 | Invalid parameter. A parameter to TOT, MIN, MAX, AVG or MID is bad. The field you are tring to use is alphanumeric when it should be numeric, a date when it should be a decimal number, etc. Since the error appears during syntax checking, you can press <RETURN> to return to the processing table and change the field numbers, operation, etc.
043 | Merge name incompatibility. Word processor or spreadsheet merge has been given two different names. You can't use the same file name more than once on the same processing table. Check for the same merge name being used in 2 different elements on the processing table.
044 | RETURN without a GOSUB. You have a RETURN but no GOSUB. Check your processing to make sure that you haven't used a GOTO instead of a GOSUB or that you are not skipping the GOSUB function.
045 | Too many nested GOSUBs. A "nested GOSUB" is a subroutine that calls another subroutine that call's a third subroutine, etc. The limit is 16. Rewrite your subroutine to reduce the number of nested GOSUBs.
046 | Edit failed. When processing data, you may have copied information from one field that doesn't pass the edit of the second field. Change your processing or change the edit type or method.
047 | Invalid data-capture format. If you are using a filePro data transfer program, this message indicates that the format has been incorrectly defined or can't be used by filePro. Consult the transfer manual for instructions.
048 | Error Reading Text Index.
049 | Error Reading Message File. This error occurs if the "errmsg" file is missing or corrupted. Re-install the filePro software to correct.
050 | Segment lengths do not match. Key and data segments contain differing number of records. This error occurs if there is a disk drive "write" problem or if a file-restructuring fails or is canceled improperly. Use the Expand File option to expand the file by one record to synchronize the key and data segments. If this does not work, restore your files from your most recent backups and start over.
051 | Bad Import Format. Not a valid DIF file. The spreadsheet file from which you want to read data is not recognizable by filePro. Recreate or revise the DIF file and try again.
052 | Merge Conflict. Cannot import and export same file. You have set up an IMPORT statement with the same name as EXPORT statement. Change one of the names.
053 | Attempt to read past end of merge file. When importing data from a DIF file, you have come to the end of the file without telling the program when to end. Add a line to the processing routine that tells the program to move onto something else e.g. if: NOT filename (no more data), then: END or something else.
054 | Function not available for this file type.
055 | Unknown alien file type. Different versions of filePro may support different types of alien file formats. The version you are using cannot access this particular format. Upgrade to the most recent version of filePro.
056 | The tokenization table is too small. Use '-t biggersize' to make it bigger in your user menu or from a system prompt. Refer to FLAGS.
057 | Wrong index type. Re-build the index with the correct Index Maintenance version. The index was built using and older version of filePro than the version of *clerk or *report that you are using. Make sure that you are using the correct version of the Index Maintenance (dxmaint) program.
058 | The processing table is not encoded. Use Define Processing to encode the processing table before using.
059 | Too many locks. On network DOS systems only, the operating system of filePro plus limits the number of files locked at any one time. You have exceeded this number (usually 200); to fix the problem, simply close some of the files used in processing.
060 | Duplicate files found while scanning drives. Occurs if filePro detects more than one copy of the same file name on multiple drives. Set the environment variable PFDSK to limit filePro's view of the multiple drives or remove one of the copies.
061 | Can't Find the Printer. Make sure that your printer destination and mapping is correct.
062 | Reference to a field that doesn't exist. You may have re-defined a file structure when using Define Files and failed to modify your processing to match.
063 | Invalid runtime format. Use correct version of 'rcabe' to re-compile processing table.
064 | Index Is Too Big. Rebuild the index using a smaller key.
065 | Too many users You have exceeded the number of registered user licenses. Limit the use of system calls from processing tables or upgrade your license to add more users.
066 | Too many users You have exceeded the number of registered user licenses. Limit the use of system calls from processing tables or upgrade your license to add more users.
067 | Screen must be at least 80x24. You are attempting to use a screen resolution that is less than 80x24. Update or re-configure hardware.
068 | No such printer. You are attempting to use a printer that is not defined. Refer to Printer Maintenance options.
069 | Can't nest CALL's Remove the CALL from the CALLed processing table.
070 | TOK table exceeds 64K (only for 16 bit systems) Reduce the size of the processing table.
071 | Invalid key-map table. Check the setting of the PFKEYTAB variable.
072 | Invalid language (sort/collate) table. Check the value of the PFLANG variable to make sure that it is a valid table.
073 | Exceeded demo version limits. You are limited to 100 records per file and 200 lines per processing table. Create test files that do not exceed these limits.
074 | Cannot establish connection to license server. Make sure that the license server is running.
075 | lm error: NO LICENSES REGISTERED Contact fP Technologies technical support.
076 | lm error: LICENSE EXPIRED Contact fP Technologies technical support.
077 | lm error: NO LICENSES FOUND FOR THIS PRODUCT Contact fP Technologies technical support.
078 | Lm error: UNKOWN REPLY FROM LICENSE MANAGER Contact fP Technologies technical support.
079 | fileProODBC Error: Cannot open DSN. Use Define Files (High Level ODBC) or Define Processing (Low Level) to set the correct DSN.
080 | fileProODBC Error: Cannot open table. Ensure that the table name is correct and exists in the data source.
081 | Spellcheck error. Contact fP Technologies technical support.
082 | Feature not licensed. You have attempted to use a feature that is not included in your license. Contact fP Technologies sales to purchase the licensed feature.
083 | License error. This error will occur if the license is in the wrong place, improperly named or is corrupted. Check that "licfp.dat" exists in your $PFPROG/fp/lib directory. Use program "licinfo" to check the licence. Contact fP Technologies technical support and provide the results returned by "licinfo".
084 | License manager platform mismatch. The license that you are attempting to use does not match the platform that you are using it on. If you have multiple licenses, make sure that you are using the correct license. Use program "licinfo" to check the license and provide the results of this program to fP Technologies sales to obtain a new license or correct version of filePro.
085 | Generic XML error.
086 | Failed to decrypt record.
087 | Failed to verify encryption key in map.
088 | This file is not licensed to run on this system.
089 | Encrypted file / grace period mismatch.