There are essentially three kinds of error messages one may encounter while operating STUREC, with varying degrees of severity.
Internal Errors are almost certainly related to a corrupted index file. The only cure for a corrupted index file is to delete it, then let STUREC build a fresh one from scratch. From the STUREC Main Menu:
Generally speaking, only index files (*.NTX/*.CDX) are subject to corruption, though data files are not exempt. If the error message identifies the corrupted file as being an index, see Internal Errors above for recovery instructions. If the corrupted file has a .DBF or .DBT extention, it means that your data file is corrupted, and you need to restore the file from your most recent backup set.
If the error message gives you the name of the corrupted datafile (i.e. SRSTUX.DBF), then you just need to restore that one file. If you cannot identify the corrupt file, you will need to restore all files.
To restore file(s) from a backup, go to menu:7.4.8. Restore from Backup, and follow the on-screen directions (you may elect to restore all files, or a select few). If that does not fix the problem, then you will need to e-mail the MicroData Systems' help desk. Please include a detailed description of the events leading up to the corruption message, as well as your STUREC© serial number and a telephone number where you can be reached.
PROC: DEVOUT LINE: 0, Print Error
This error message indicates a communication failure between STUREC© and the printer device connected to printer port LPT1. STUREC is usually capable of detecting if your printer is ready or not, but sometimes the MS-Windows® computer operating system interferes with STUREC's ability to reliably test the printer's status. This happens quite frequently with the newer, less expensive, "Windows" (only) printers. NOTE: If you have a Windows-only printer, STUREC will most likely neve able to print to it.
So, what can be done to fix it? Well, unfortunately, there is no one solution that works for everybody. However, many times simply re-starting your computer will do the job. And if that does not work, then you can try printing reports to a file first, and then send the file to the printer. If that does not solve the problem, you may need to have your local computer support personell try and resolve the Windows mis-configuration. At worst, you may need to replace the printer with one that is desig o natively accept DOS print jobs.
STUREC's Error Handling System can detect (and safely recover from) a large number of errors, most of which are related to invalid data or invalid operations on data. While MicroData Systems, Ltd. thoroughly tests new features/enhancements, we cannot test every possible scenario. If you encounter an error message not covered here, or one that does not have an obvious recovery procedure, please submit a Bug Report form. to the STUREC development team.