1. Custom size statement
========================
If you set the paper size to 'default' in the actual statement specification, then you should change your Windows printer properties so that it is 'custom' and give it the correct dimensions of the statement. There is no reason why you should worry about not being able to change the paper size if you are always using the same size statement form. When it comes time, you will be able to modify the specification to use another size.

If other people use this printer (ie it is on a Network Server), then this method is not suitable, as all your other paperwork would print incorrectly.

If this is the case, then you should go into Windows - Control Panel - Printers, and create/add a 'new' Printer that uses the HP 6P, and define this one for the custom size required. After doing this, go into Receivables and select File - Options, and set the 'Specification' printer to be this new printer.

Note also that your specification must have the correct sizes defined in each 'section'. Also, when you are in the specification, make sure there are no other 'sections' below the 'End of page' section. To do this, left click and HOLD the left mouse button down on the down-arrow on the right-hand scroll bar until it reaches the very end of the specification. If you do not see any other sections, then SAVE your specification as it is. This will not be the cause then.

2. Error...Can't open report definition
=======================================
I do not know what has ocurred to cause this, however, re-installing Receivables should correct it, as this will restore damaged or otherwise unstable files.

If you upgraded from an earlier version, and Adagio is installed on a Network Server, your local PC must also be upgraded by performing the workstation setup for this newer version on your PC. Your Dealer should be able to assist you with this, if it has not already been done.

It would be helpful to know if a workstation setup was done at the time of the original upgrade. (Of course, if Adagio was originally installed only on your PC (ie for your use only), then you would not have to perform the workstation setup, nor should you).

Please let us know, would you?

Hope this helps

Regards,
Softrak Technical Support

I am just posting a followup message to your post regarding the AR Adjustment Posting Journal.

Perhaps mrushton's suggestion helped you in this respect?

I would like to suggest that both of 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 real adjustment batches
- Post the batch, then print and clear the posting journal ...

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:

- Are you printing to a printer or a file, or a 'print to file' setup in Windows as a printer?
- What are the exact steps you have done leading up to the printing of the posting journal?
- Does the error occur when you click on the Print button, or ...? Please tell us exactly at what point the error occurs.
- What Windows O/S version are you using?
- 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.

Thank you. We look forward to receiving the answers to our questions.

Softrak Support

Just to update you on this, I have included my post to mrushton for your perusal...

"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 - 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 from their Dealer to engage the executable ptf file."

As you can see, this was hard to track as it does not occur on all machines!

Regards
Softrak Support