The error you are getting could be due to either an unknown condition that causes this to happen intermittently with some datasets, but not others, or because you have not printed, then CLEARED the batch status report.

If you have confirmed that the Batch Status report has indeed been cleared, and all other posting journals as well, then for some reason, a file or files are lingering in these datasets to cause CB to think that there is still an outstanding report to be dealt with, so it won't let you continue with the YE procedure. If this is the case, the following instructions should clearup this problem:

To replace a damaged set of Batch control files:

Before you replace the batch control files and remove the corrupt batches, MAKE A BACUKP OF YOUR DATA!!!

1.Print a Batch Status report for your records. When the Batch Status files are replaced, this information will be lost.

2.Once you have a backup, remove the batch and batch control files. This is the list of files, bc represents the Cashbook bank code and XXX represents the data extension:

CBbcBTI1.XXX: Batch Control File 1, index
CBbcBTI2.XXX: Batch Control File 2, index
CBbcBTCR.XXX: Batch Control File, random
CBbcInnn.XXX: Batch File Name, index
CBbcRnnn.XXX: Batch File Name, random

3. Rename the data files for the bank code(s) in question.

4. You must then create a dummy Cashbook using the original bank code.

5. Copy the empty batch control files to the renamed dataset.
6. Delete the dummy dataset.
7. Rename the live data back to the original data extension.
8. Do a data integrity check again to ensure all is well.

Hope this helps!
Regards

[This message has been edited by Softrak Support (edited 11-21-2000).]