info@flexad.nl

+31703452044
Regentesselaan 115
2562CR Den Haag

Mail ons nu 
voor meer info
of een demo!

 

Dataflex foutmeldingen

RUNTIME ERROR STATUSES & DIAGNOSIS


 

 

STATUS CLASS OMSCHRIJVING OPERATING SYSTEM ERRORS

 

01 MH DISK FULL.

Oplossing: Disk space used up.

02 MH DISK DIRECTORY FULL.

Oplossing: Directory (number of files) full.

03 MH CANNOT CLOSE CURRENT EXTENT (O/S ERROR)

Oplossing: Nog te traceren.

04 MH SEEK TO UNWRITTEN EXTENT (O/S ERROR)

Oplossing: This status generally indicates problems with the operating system’s directorystructure of the disk drive. Power failure is a common cause of directory corruption. If you have had other media errors, they can show up later as directory problems. Generally the disk should be reformatted and the data recovery techniques used. ( See also Disk Limitations).

05 L / D DIRECTORY OVERFLOW (DISK FULL).

Oplossing: Directory (number of files) full.

06 L / D SEEK PAST END OF DISK (DISK FULL).

Oplossing: Disk space used up.

07 SU / PE TOO MANY LOCKS, USE FILE-MODE-READ- ONLY.

Oplossing: In computers or networks whose operating system is based on MS-DOS or PC-DOS, many DataFlex applications require more files open than is available as a default in the operating system. If this error occurs, you can eliminate it by using the FILE-MODE command to set database files which are not written to READ-ONLY. You can also reduce this problem by using the CLOSE command to close database files which you are done using.

STATUS CLASS. DATAFLEX STATUSES

10 L/M,PE +++OUT OF MEMORY+++

Oplossing: New installation , run Setup. Otherwise out of memory.

11 OP, PE NUMBER TOO LARGE FOR FIELD ALLOCATION.

Oplossing: Number is too large for a data field. Or number doesn’t fit into allocated field; redefine field for a larger value.

12 PE WINDOW NUMBER OUT OF RANGE.

Oplossing: This is usually caused by improper use of window indexing. Recount your windows and/or temporarily print the index value to the screen while the program is running.

13 OP AN ENTRY IS REQUIRED ON THIS WINDOW.

Oplossing: Operator attempted to return past a "REQUIRED" window.

14 OP PLEASE ENTER A NUMBER.

Oplossing: Entry of letters ("O", lower case "L", etc.) in a numeric-typed window.

15 OP INVALID ENTRY FOR THIS WINDOW.

Oplossing: Entry doesn’t conform to CHECK or format specification made in the program. Some means for determining what is acceptable, must be provided for the operator ( Help screen, prompt, custom status message).

16 OP PLEASE ENTER A VALID DATE (MM/DD/YY)

Oplossing: Improper date format or value.

17 OP NUMERIC ENTRY IS OUT OF RANGE.

Oplossing: Entry doesn’t conform to "RANGE" in entry option made in the program. Some means for determining what is acceptable, must be provided for the operator ( Help screen, prompt, custom status message).

18 PE CAN’T OPEN SYSTEM COMMUNICATIONS FILE.

Oplossing: Dataflex cannot establish multi-user operator system communications. Check your installation notes for information relating to your particular operating system.

19 PE MULTI-USER TIME OUT (BUSY TOO LONG)

Oplossing: The system is in a LOCKED state for too long. Check that none of your programs does a LOCK or REREAD without an UNLOCK. On a very busy system it is possible to get this status occasionally through no fault of the program.

20 MH READ ERROR ON INDEX FILE, RE-INDEX FILE

Oplossing: This is caused by a corrupted index file. Re-indexing should be sufficient. If this happens repeatedly, there may be a subtle problem with the operating system or equipment. If you are an multi-user system, make sure that you follow the multi-user checklist below.

21 MH, L/D WRITE ERROR ON INDEX FILE

Oplossing: This is caused by a corrupted index file. It can also be caused by a disk full condition. Re-indexing should be sufficient. If this happens repeatedly, there may be a subtle problem with the operating system or equipment. If you are an multi-user system, make sure that you follow the multi-user checklist below.

22 MH INDEX FILE DAMAGED, RE-INDEX FILE

Oplossing: This is caused by a corrupted index file. Re-indexing should be sufficient. If this happens repeatedlOpy, there may be a subtle problem with the operating system or equipment. If you are an multi-user system, make sure that you follow the multi-user checklist below.

23 L/P INDEX FILE FULL, EXCEEDS DEFINED SIZE

Oplossing: In File Definition and Auto-Create you are asked for the maximum number of records that could be in a file. If this number is greatly exceeded, you will get Status 23. To fix this, simply re-enter File Definition and change the maximum number of records. You will then have to rebuild all indexes for the using Re-index.

24 PE CAN’T CHAIN WHILE LOCKS IN EFFECT.

Oplossing: The CHAIN command was executed after a LOCK or a REREAD command without an UNLOCK command’s having first been executed.

25 PE RECORD NOT FOUND

Oplossing: FIND errors—FIND command was unsuccessful. To determine what the problem is, temporarily print the value of the record buffer to the screen directly before FIND. Also be conscious of the record number, which must be part of the key if included in the index for a FIND EQUAL.

26 MH, MU CAN’T CLOSE INDEX FILE

Oplossing: This is caused by a corrupted index file. Re-indexing should be sufficient. If this happens repeatedlOpy, there may be a subtle problem with the operating system or equipment. If you are an multi-user system, make sure that you follow the multi-user checklist below.

28 OP,PE DUPLICATE RECORDS NOT ALLOWED IN FILE.

Oplossing: An attempt was made to enter a record whose entries in (uniquely) indexed fields match the entries of a record already in the file. Or a SAVE was done on a record having a unique key that matches a key already in the database. If unexplainable, try re-indexing the file.

30 PE, MH CAN’T READ CONFIGURATION FILE

Oplossing: Program file is not a compiled DataFlex program or the file is damaged.

31 OP, PE PROGRAM FILE NOT FOUND.

Oplossing: This is caused by an attempt to load a program that doesn’t exist. This can also be caused by an improper menu configuration or an error in a CHAIN command.

32 PE, MH, L/D CAN’T OPEN OUTPUT FILE.

Oplossing: If the OUTFILE or DIRECT-OUTPUT command cannot create the output file, you will get a status 32. This can be caused by disk full or bad file name. Or Disk directory full while trying to open an output file.

33 PE, MH, L/D CAN’T OPEN INTPUT FILE

Oplossing: The device named in a DIRECT-INPUT command is not defined in your system, or the file named is not present in your drive, directory, or search path.

34 PE, SE NOT A VALID DATAFLEX PROGRAM

Oplossing: This error occurs when the DataFlex runtime (DFRUN) is directed to execute a non DataFlex program file. This can occur because of erroneous menu configurations, faulty CHAIN commands, but is most likely to be the result of directory file naming or renaming errors entirely outside of DataFlex. Check your directory for files with .FLX which are not compiled DataFlex program files.

35 SU PROGRAM MUST BE CONVERTED

Oplossing: If you have copied an application from another environment (MS-DOS to Xenix, UNIX to any other UNIX), compiled (.FLX) program files may not be compatible with the new environment. In such a case, you will get this error. The program source code is compatible, and may be made executable in the new environment simply by recompiling it in that environment.

36 PE OUT OF MEMORY FOR WINDOWS AND RESIDENT IMAGES.

Oplossing: Image windows in your program consume memory. Images with the RESIDENT option consume an anmount of memory equal to their actual size in bytes (up to about 2,000 each). If you get this error, you must reduce either the number of windows in your program (consider using CHAIN to another), the number of images using the RESIDENT option, and/or the size of such images. This error is most likely to be reported at compile time.

41 OP FIND PRIOR TO BEGINNING OF FILE

Oplossing: FIND errors—FIND command was unsuccessful. To determine what the problem is, temporarily print the value of the record buffer to the screen directly before FIND.

42 OP FIND PAST END OF FILE

Oplossing: FIND errors—FIND command was unsuccessful. To determine what the problem is,

temporarily print the value of the record buffer to the screen directly before FIND.

43 SU, MU CANNOT OPEN INDEX FILE

Oplossing: The index information is kept in a separate file from the actual data. The indexes have the "ROOT" file name with a ".K#" extension, where "#" is the index number. These files must reside on the same drive as the data file (see Status 75).

46 SU, PE GRAPHICS MODE NOT INITIALIZED

Oplossing: Most of the commands in the GRAPHICS group require the GRAPHIC command to have been executed with its ON option prior to the command. This error is triggered when such a command is used without GRAPHIC ON having first been executed.

47 SU, PE BAD OR MISSING GRAPHICS DRIVER

Oplossing: If the GRAPHIC command with ON is executed, it must either specify a graphics device driver (*DEV) or there must be driver name in the value of System Variable DFGRAPH-DRVR, or a default driver name must be installed through the Setup Utility. Where all these conditions fail, this error will be triggered. Correct any of the three ways of providing the needed driver name. This error will also be triggered in the event the named driver is not present on the disk drive. Check to make sure it is present, and correctly named.

48 PE GRAPHIC COMMANDS NOT ALLOWED

Oplossing: DataFlex supports graphics commands only in certain operating system environments. This error occurs when an attempt is made to execute such commands in an operating system environment in which it is not supported.

50 MH INTERNAL EXPRESSION ERROR

Oplossing: A mathematical expression could not be typed. This problem is most likely to be generated by an improper compilation, and can often be fixed by recompilingthe source code. This error is most likely to occur at compile time.

51 PE BAD FORMAT IN EXPRESSION (OPERAND)

Oplossing: If the expression evaluator runs across an improper argument when it is expecting an argument, you will get a status 51. Most expression statuses are not reported until runtime. Example: (1+*2). If unexplainable, you may have a data consistency error.

52 PE BAD FORMAT OF EXPRESSION (OPERATOR)

Oplossing: If the expression evaluator runs across an improper function (+,-,*,or /) when it is expecting a function, you will get a status 52 at runtime. Example: (1=2).

53 PE UNSUPPORTED FUNCTION FOR THIS O/S

Oplossing: The program contains a command (such as RUNPROGRAM WAIT) which is not supported in the operating system you are running on. For example, the RUNPROGRAM command with the wait option cannot run in TurboDOS, and so generates this error.

54 PE INVALID SYMBOL IN EXPRESSION

Oplossing: If a keyboard entry to a NUMBER variable contains non-nummeric characters, this error will be triggered.

55 PE INVALID DATA TYPE IN EXPRESSION

Oplossing: Certain data types (strings, and windows without parentheses around them, indicators, labels) are not allowed in expressions. This error reports the presence of such terms in expressions. Most errors of this type will be reported first at compile time.

56 PE ATTEMPT TO RUN UNCOMPILED EXPRESSION

Oplossing: The compiler compiles expressions for type. If an expression generates an error at compile time (see Error Statuses 50/54/55/57/58/59) it will not be compiled. If the compiled program is run without correction of the problem and recompilation, the uncompiled expression will generate this error at runtime.

57 PE OUT OF EXPRESSION STACK SPACE

Oplossing: The compiler maintains a "stack" which it uses to type all expressions. Too many terms and/or too many terms of different types in an expression can trigger this error. To overcome this error, "build up" your final expression through two or more actual lines of code (commands). Most errors of this type will be reported first at compile time.

58 PE OVER 25 PARENTHESES 0 IN EXPRESSION

Oplossing: This error is generated when more than 25 pairs of parentheses are used in one expression. To overcome this error, "build up" your final expression through two or more actual lines of code (commands). Most errors of this type will be reported first at compile time.

59 PE FLOATING POINT EXCEPTION ERROR

Oplossing: This error occurs when an expression evaluates to a value outside the range of DataFlex REAL numbers (1 times 10 to the 306 power).

60 SU BAD OR MISSING .DEF FILE

Oplossing: A MAKE-FILE command was executed which used a rootname in its argument for which either no .DEF file was found, or if a .DEF file was found, it was not in the required format for such files.

61 SU ILLEGAL REDEFINITION OF EXISTING FILE

Oplossing: A MAKE-FILE command was executed which had in its argument the number of an existing database file and:

  1. the file rootname in the command argument did not match the one in the definition of the database file whose number was used.
  2. the database file whose number was given has data in it and the lengths, types, or total length of the fields in the definition of that database file do not match those in the .DEF file whose rootname was used in the command.

62 SU TAG FILE ERROR

Oplossing: A MAKE-FILE command was executed which used a rootname in its argument for which either no .TAG file was found, or if a .TAG file was found, it was not in the required format for such files.

63 OP, PE ATTEMPT TO DELETE A PROTECTED RECORD

Oplossing: An attempt was made to delete a file with the READ-ONLY attribute on it. Check the

64 OP, PE ATTEMPT TO FIND A PROTECTED RECORD.

Oplossing: A FIND command was addressed to a file set READ-ONLY by a FILE-MODE command.

65 OP, PE ATTEMPT TO CREATE IN A PROTECTED FILE

Oplossing: An attempt to add a record to an existing file with a read only privilege on was made. Check the code for a FILE-MODE command addressed to the file.

66 OP, PE ATTEMPT TO EDIT A PROTECTED FILE.

Oplossing: An attempt to edit a read-only protected file was made. Check the code for a FILE-MODE command addressed to the file.

70 SU NOT A CURRENT DATA FILE.

Oplossing: Database files created under revisions of DataFlex prior to 2.3 cannot be used under DataFlex 2.3 without conversion by the DFCONVER program. Run DFCONVER on all your database files before attempting to use them under DataFlex 2.3. See your Information Instructions for further information on DFCONVER.

 

71 OP, PE NO RECORD IN MEMORY TO DELETE.

Oplossing: Delete key pressed with no record found. Or if a DELETE command is issued against an INACTIVE record buffer, the DBMS will not know what record to delete and will report status 71. DELETE must be used with a "FOUND" record.

72 SU, MU FILE NOT OPEN.

Oplossing: If a database file is used before it has been OPENed, you will get a status 72. This can also be caused by a file not being on the disk, in which case you should get a status 75 first.

73 PE FIELD NUMBER OUT OF RANGE.

Oplossing: Field number out of range. This is generated by improper use of field indexing. Carefully check the index values and make sure they’re in range. This can also be caused by using an old program with a modified file definition.

74 SU, MU CAN’T OPEN "FILELIST.CFG"

Oplossing: FILELIST.CFG must be present on the logged in disk drive.

75 SU, MU CAN’T OPEN DATA FILE (.DAT)

Oplossing: The data file name contained in FILELIST.CFG can’t be found. The "ROOT NAME" has ".DAT" appended to it for the OPEN. Make sure that the root name in File Definition corresponds with the actual name and drive of the data file as shown in your opening system’s directory.

76 PE FIELD NUMBER OUT OF RANGE.

Oplossing: Field number out of range. This is generated by improper use of field indexing. Carefully check the index values and make sure they’re in range. This can also be caused by using an old program with a modified file definition.

77 PE FIELD NUMBER OUT OF RANGE.

Oplossing: Field number out of range. This is generated by improper use of field indexing. Carefully check the index values and make sure they’re in range. This can also be caused by using an old program with a modified file definition.

78 MH, MU CAN’T UPDATE RECORD ZERO OF DATAFILE.

Oplossing: Directory is damaged. BDOS Error: Bad Sector; I/O Error; Read/Write Error. These errors are returned directly from the operating system, not from DataFlex. The exact wording may vary from system to system. This type of status is caused by an unrecoverable hardware or media error. The first thing to do is to reformat and restore your data from backup. If this happens frequently, your hardware should be examined. If you use floppy disks, you should consider another brand.

79 OP, PE FIELD NOT INDEXED, CAN’T FIND BY THIS.

Oplossing: Field not indexed on FIND. A FIND command has been issued on an inactive index or a non-indexed field.

80 MH, MU CAN’T CLOSE DATA FILE

Oplossing: Directory is damaged. BDOS Error: Bad Sector; I/O Error; Read/Write Error. These errors are returned directly from the operating system, not from DataFlex. The exact wording may vary from system to system. This type of status is caused by an unrecoverable hardware or media error. The first thing to do is to reformat and restore your data from backup. If this happens frequently, your hardware should be examined. If you use floppy disks, you should consider another brand.

81 MH, MU RECORD NUMBER OUT OF RANGE.

Oplossing: If this occurs when saving a record, it indicates a corrupted data file. You should use Reindex on the file.

82 PE EDITED RECORD NOT SAVED.

Oplossing: This status indicates misuse of the database. If an active record is edited (MOVEd to) and not SAVEd, you will get a status 82.

83 PE TYPE CHECK ERROR, ASCII USED AS NUMBER.

Oplossing: Typ check error. This often arises from use of an old program with a database file whose file definition has been modified. Update the program to take into account the revised file structure.

84 PE FIELD OUTSIDE RECORD

Oplossing: When a program addresses the fields of a database file by use of FIELDINDEX (filename.fieldname&) the value of FIELDINDEX can be driven beyond the number of fields in the file definition. This may happen when you run an unchanged program after you have removed fields from a file definition, or it may happen because FIELDINDEX was erroneously driven too high.

86 PE RELATED FIELDS ARE NOT THE SAME LENGTH

Oplossing: Related fields MUST be exactly the same length an type. Check your file definitions for all files involved.

87 OP NO SUPERFIND PATH TO THIS RECORD.

Oplossing: Can’t superfind from this window; main file does not relate to this field.

88 OP INVALID FILE NAME

Oplossing: A badly formatted or too long file name has been entered.

90 OP PLEASE ENTER A VALID RECORD ID

Oplossing: No record is found with a "FINDREQ"; press FIND.

91 MACRO CMD. ATTEMPT TO PUT INTO INTEGER CONSTANT.

Oplossing:

92 OP, SU, PE PROGRAM FILE NOT FOUND.

Oplossing: Operator entered a program file name that is not found on the indicated disk. (also see Status 96). This is usually triggered by a CHAIN or RUNPROGRAM command whose target file cannot be found. Review drive assignments of files concerned and make sure they are correct in the command. This can be caused by incorrect installation order.

93 PE DUPLICATE COMMAND LINE NUMBER

Oplossing:

94 PE PROGRAM LINE NUMBER OUT OF RANGE.

Oplossing:

95 PE ARGUMENT TYPE NOT LEGAL IN ENTRY COMMAND.

Oplossing: Legal types of argument for the ENTRY command are windows, database fields, expressions and options. Where an ENTRY command has a a constant, variable, label, or df-filename as an argument, this error will be triggered. Errors of this kind are most likely to be reported first at compile time.

96 OP, SU, PE CAN’T OPEN PROGRAM FILE

Program file not found. This is usually triggered by a CHAIN or RUNPROGRAM command whose target file cannot be found. Review drive assignments of files concerned and make sure they are correct in the command. This is often occurs in MENU because of incomplete drive designation in action specifications.

97 PE MULTIPLE GOSUBS WITHOUT RETURN.

Oplossing: For every GOSUB or use of a KEYPROC, there must be a RETURN. If not, after 18 GOSUBS, you will get Status 97. Also if your KEYPROC is called from within a subroutine, you must RETURN to within that subroutine.

100 OP OPERATOR ERROR.

Oplossing: The most common error status is a simple mistake by the operator. DataFlex handles many operator errors directly and gives you the capacity for providing additional checks where required. Most of these errors, unlike the other runtime statuses, do not call for any corrections in program code or system setup. The most correction that is likely to be needed is operator instructions in those cases where the status message itself is not sufficient for the purpose.