INFORMATION PROVIDED IN THIS DOCUMENT AND ANY SOFTWARE THAT MAY ACCOMPANY THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR PURPOSE.
The user assumes the entire risk as to the accuracy and the use of the information supplied. This information may be copied and distributed subject to the following conditions: 1)All text must be copied without modification and all pages must be included; 2)If software is included, all files on the disk(s) must be copied without modification; 3)All software included and documentation must be distributed together; and 4)This information may not be distributed for profit.
Copyright © 1996 Platinum Software Corporation. All Rights Reserved.
Platinum ia a registered trademark of Platinum Software Corporation.
All other trademarks contained herein are acknowledged.
ERROR 5
Error 5’s are very inconclusive. These error messages may be problems within the program where a particular field within a record is incorrectly defined. It may also indicate that the data file is corrupt where a field on a specific record is corrupted.
Determining if the program or data file is the source of the problem can be challenging.
Steps to see if problem is program vs data as follows:
Try the same procedure in a different company. If you get the error 5, it's probably programs in which case reinstalling that module will should correct the problem. If you don't get the same error, the problem lies within a data file. Try recover the files that may be affected by the process you were trying to run. ie: Printing checks apselect, apclass, apvendh, aptran etc...
If after recovering, the same error occurs, first backup or copy the file to a new name, and initialize the file and reenter the records manually(use judgment on whether this is possible. ie: if the file is aptranh it would not be advisable to initialize this because of the volume of lost data). If initialize doesn't correct, it's probably another data file that is causing the problem.
The last and most arduous task to find the file would be to copy file by file to another company until the error occurs. ie: copy into either demo or a newly initialized company, apone and try the same procedure, if ok, then copy apparams and try procedure again, if ok continue copying one file at a time, trying the procedure between each copy until the error occurs.
When the error finally occurs, the new problem is finding the bad record or part of that file that is causing the error. First try the recovery process. If this doesn't work, see if there is anything awkward with it's setup. If the file is apone, look in all the system default screens to see if one of the settings is incorrect or missing. Again this is going to take alot of patience on the part of the user, especially if the problematic file is a large data file such as aplinh or aptranh. (A good tool to use would be a third part application, such as Xtrieve, that reads Btrieve files to view any corruption in a file).
In versions previous to version 4.02 error 5 message may also occur if there are files named FE*.* in the company directory. Names such as FEB95.XLS will incorrectly trigger Foriegn Currency processing and often result in error 5’s.
Also check for the presence of *.BLD and *.SAV files, if present , rename and try running the process again.
