Discussing this with R&D has not proven to be very productive due to the lack of details provided by you in previous posts, however, I would like to suggest that you try this:

- Open the AR sample data with Receivables (X:\Softrak\CRWIN\Samdata, ".sam" extension).
- Create a new adjustment batch and post some entries that would approximate the number of entries in your the adjustment batch that produced the error in the first place.
- Post the batch, then print and clear the posting journal as you did with your own data.

Do you get the same error? If not, this eliminates a "bug" in the program and points to a data related/produced condition.

If you CAN duplicate the problem with sample data, then please answer the following questions in as much detail as possible:

- What are the exact steps you have done leading up to the printing of the posting journal?
- When you print to file, do you use the default filename that Adagio uses (ADAGIO.TXT) or do you use your own filename?
- If you use your own filename, do you just type it in at this prompt (to replace the Adagio.txt) and if so, does this file already exist when you do so? Please give exact details.
- Does the error occur when you click on the Print button, or ...? Please tell us exactly at what point the error occurs. So far, you have not been precise about this. Certain mouse clicks tell the program to do certain things. When dealing with problems such as this, it is very important to be accurate in your descriptions. Thanks.
- What printer emulation is the HP driver using? HP or PCLxx? There are known problems (not just with Adagio) when using a PCLxx emulation. Some versions of this driver do not work properly.

What R&D did recognize was the format of the error message, which actually is generated by Windows, not Adagio - but this error, instead of generating a more useful message, uses the %1 in place of what normally is more descriptive, so they cannot identify it like they otherwise would.

I will say that even with the information to all the questions in hand, we may not be able to find the cause, especially if you cannot produce this with sample data. In this case, we would normally ask for the data involved, however, because you are not a Business Partner, we cannot provide this kind of direct support and you would have to contact your Dealer for more help with this. I am curious now - if you don't mind me asking - who is your Dealer over there?

Thank you for any information you can give. We look forward to receiving the answers to our questions.

Regards,
Softrak Support