Is this error occurring when AR is actually performing the YE procedure, or when you are printing a report? It's reference to the report definition not being able to be opened because something already exists suggests a report.

Has anything happened recently on your system (or the Server) that could have affected this?

Have you tried rebooting your PC? I would try this first - then, if this does not resolve it, remove the CRWIN program directory and reinstall Receivables.

Please let us know if this helps.

Regards,

Softrak Support

Glad to hear this problem is resolved!

Although reinstalling the program may seem like overkill to you, often the benefits of doing so far outweigh the time it takes trying to discover 'why' the problem occurred in the first place, if in fact the cause can be found at all!

In most cases, these types of 'cryptic' errors occur only on certain PC's and/or environments where specific conditions exist at a specific point in time (ie memory allocation etc) after performing a certain sequence of operations on that PC.

Because some of the reports are stored in temp files at the time of printing, and selecting certain criteria for that report will generate the report from a specific report file that is created as a result of those options having been selected, it is difficult to answer your questions without knowing exactly what options were selected at the time of printing the Adjustment posting journal.

We have not had any reports of this particular error message before, and I have tried to duplicate it here by renaming any files I could find that had to do with printing an AR report and specifically with the Adjustment PJ - but could not get this error. Not really surprising. It has spurred our curiousity though, so if I can find out more about it, I will post it here at that time. In the meantime, it would be helpful to know what options you had selected for the posting journal prior to printing it:

Was the report sorted by Customer number, Adjustment date or Adjustment number?

What other options on the 'Print Adjustment Posting Journal' did you select?

Did you print the report to the Printer - or to a file, or do you have a 'text only' printer defined in Windows that you select AS a printer, but it actually prints to file?

Other things that would be helpful:
What O/S are you using on this PC?
If Adagio is installed on a Server, what NOS is it using and what version of client do you have running on your PC?
Is the data on the Server as well or on your local drive?
Do you have a virus checker running in the background? If so, is it NAV or McAfee or?
Has this occurred before? Has any other workstation reported this happening with this or any other report?

Thank you. Once we have this information I will pass it on. As I indicated above, if we find out anything further I will post it here - otherwise, since it has been resolved, we will consider this issue closed.

Regards
Softrak Support

[This message has been edited by Softrak Support (edited 09-14-2001).]

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

Thank you for the additional information provided. Coincidentally, while discussing this in our tech support meeting, we were able to duplicate this on one of the R&D PC's. It is a Windows 98 O/S as well. Interestingly enough, when we tried it on two other stations that are running Win98 - same SR it could not be duplicated!

All were using Adagio program installed locally w/local sample data. I could not duplicate on my PC, but I am using W2K.

Because we were able to actually duplicate it on one machine, R&D was able to track the problem - otherwise this would have been much more difficult, as it was not data related.

The end result will be a ptf available to remedy this. The ptf will be available to download from our website. Registered End Users can download this from the End User area, but they must obtain a password to start the installation procedure from their Dealer.

We thank you for your patience and help.

Regards,
Softrak Support