Hi:

To find your previous postings, click on the "search" option at the top of the screen. When the Search screen appears, enter 1019 (your Member number) into the "Search by Registered Member Number" then then click on the Search button. All of your postings will appear.

Your posting was in May 2005 and the title was "A/Rec".

Just to clarify, but there are two places that are checked to detemine if posting journals exist:

1) The ARPOST* files, or the raw posting journal files. In the case of Multi-currency AR, the ARCLE* is appropriate to grab that file.

2) The Company Profile contains the 'next posting sequence' numbers for the different batch types, and also fields called 'purged up to' for the batches. Any sequences between these two values are listed on the print posting journal report screen as the range of sequences to print.

If the ARPOST* files get out of sync with the company profile, this would cause the problems associated with getting a 'nothing to print' message for posting journals when you expect something to print. But how to tell which one is the problem?

- If you try to print the report, but before even getting to the print screen you get a 'nothing to print' message, the profile is OK but the ARPOST* files exist with size > 0. The reports were purged by the program as expected, but for some reason the file was not actually cleared. The solution in this case is to rename the ARPOST* files as you have done.

- If you get to the screen where you see a posting sequence range, but on attempting to print you get a 'nothing to print' message, the problem is likely that the ARPOST* files were removed prior to actually purging the reports. It could also be caused by incorrectly restoring data. Thus the company profile has been put out of sync due to manipulating files. The solution in this case is to post a batch, then print and purge the journal for all sequences as you normally would. This then sets the 'last purged sequence' to where it should be.

I suspect your error this time is due to the second scenario, where the ARPOST* files were prematurely removed. Without restoring data, the only thing you can do is post another batch and purge everything, before you can edit your control account sets. Or get a database repair.

Don't forget the obvious - try running Data Integrity Check and rebuilding errors that are found (make a backup first)

Hi Donna - If you would like us to take a look at this again, please give me a call. I can have our Kamloops consultant come out to your office.

Regards,
Lars Glmhagen