Although I have not been able to find the posts in this forum (I guess I'm not using the right words), this new release specifically addresses several issues raised with Version 6.8A. In this upgrade:

• Documents are moved directly to history on dayend processing to allow easier reporting. You may elect to keep them in both current and history for a specific period of time. Now you can design all your reports on the history file, as all document can be found there.
• Custom reports created with Crystal Report for Adagio can be attached to directly to the reports menu.
• Faxing a document can set the "print" status - removing the need to physically print an invoice.
• Multiple instance of Adagio OrderEntry can be launched, allowing an operator to interrupt processing of one order to work on another.
  

There are more improvements, but I know that several regular viewers of this forum had been looking for these improvements.

If there is a program feature, or change in behaviour that you would like to see in an Adagio module, please post the suggestion here, or send me an e-mail directly.

Hi AlanC,

No table change was necessary for Adagio OrderEntry 68B as the data structure remained the same as version 6.8A. This is why the table name continues to be 68A. Nothing to worry about here.

I was not able to duplicate the problem you reported using Quik Reports for Windows and the tables shipped with Adagio OrderEntry. A report I created on the Order Details file, using the fields 'Tax by Jurisdiction[1]' and 'Tax by Jurisdiction[2]' printed the correct and different tax values.

To better answer this question, I'd need to know which table, data file and fields you are using in your report to print the tax values.

If possible, could you post your responses under a new topic? Thanks.