This seemed like a good newsletter to revisit common Libra errors, their causes and cures. In relatively new programs, errors may be simple programming bugs that need to be corrected in the program itself. In more established programs the errors usually relate to either data entry errors or corrupted data.


Errors: 53 & 57


These two errors are caused by broken pointer structures within a file. They are most commonly caused by programs ending abnormally. The program is looking for records that are no longer there. In some modules, like Order Entry, these can be fixed by running the Period-End Closing to rebuild the files.


Error: 122


This error relates to an array element out of range. The most common cause is a faulty date. The program may be looking up the name of month 13 for example. Fixing the date will usually correct the report problem. The odd time a report can also cause this error if the selection of data requested returns no results.


Error: 250


This error is caused by one program trying to jump to another that is not at the same level. Occasionally clients employ Libra modules from different versions and that can cause this incompatibility. Bringing both programs up to the save level will usually cure this.


Errors: 704, 714, 720, 721


These errors are caused when Libra encounters problems processing files. The file may not be open or may be at a size different than that expected. Occasionally exiting the program completely will fix the problem otherwise intervention may be required.


Error: 726


This is probably the most common Libra error. It is caused when the program tries to save or display numeric data to a field that is too small to contain the number of digits required, such as a page number over 1000. It can also signify that you have some damaged records in a file and may be serious. Fixing a single data item, restoring and or repairing the file may be required to eliminate the error completely.


Errors: 4148, 4152


4148 is a file sharing violation caused when one user locks a file to prevent other users from accessing it. Usually only backups and closings do this, but it can occur as a server error with no apparent cause. 4152 is a missing file, which may have been deleted accidentally. Getting everyone out and rebooting the server is sometimes required to eliminate these errors.


Error: 4272


This indicates a key not found. When you run a report the program often goes back to the master files to obtain a customer name for example. If the customer no is changed after the data was entered this sort of error can occur. Customer Id changes seldom affect unposted transaction files, requiring manual edits.


Errors: 10015 to 10018


These are Index File errors. Re-Sort Index files via <F8> Utilities & 94. Sort Index Files in all Libra associated modules to commonly correct this.


Errors: 19002, 19042


These are Btrieve File Errors. They commonly occur, like the errors immediately above, when a server crashes while data is being added to the file. When the server comes back up it is worth while shutting it down normally and restarting it, which occasionally fixes these errors. Otherwise the file may require repairing with the Bclean Utility or to be restored from a prior backup copy. Some temporary files, if corrupted, can often just be deleted and recreated.