Installs the AdagioPDF printer driver. All reports and printouts from Adagio can be printed to the AdagioPDF printer to create a PDF document in the data folder.
Supports the features in Adagio ePrint. When ePrint is installed you can print reports to PDF files in configurable folders determined by the Report Type (General or Transaction). Fields can be embedded to establish the file and folder names (User, Session Date, System Date, Time). Click the ePrint button (red "EP" icon) on any report dialog to print the report to PDF. The Paperless Reports option forces all reports to be printed to PDF. Reports can be printed to PDF and attached to an email (MAPI) with a single button click.
Report Favorites allow saving Reports with specific options chosen. Click the Favorite button (a star icon) on any report dialog to create a Favorite. Favorites for a report can be accessed from the report dialog in a drop-down field. Private Favorites are yellow, Public Favorites are blue. Added Favorite Reports and Print/Delete Favorites functions to the Reports menu. Multiple favorites can be defined for the same report. Favorites can be private to the Adagio user or public for use by all users.
Report Sets allow the grouping of Report Favorites and Online Inquiry summary and detail reports into a single print job that will run unattended. Report Sets may be printed to printer or PDF files. Report Sets may be launched from a command file or a scheduled Windows task by running SalesAnalysis.exe with the parameter /R followed by the Report Set (ex. /RMonEnd). A progress dialog lists the reports in the Report Set, the printing status of each, the destination folder, filename and conflict strategy. A log is generated that records the printing status of each report in the set. Use Report Sets to automate the printing of all your daily or month end reports.
On the Open database dialog you can now use Alt-B to open the browse and Alt-F (for Favorites) to open the previously opened list. In previous versions you had to use the mouse to select the folder buttons.
Alt-X now selects the Excel Direct button on grids where it is available. In previous versions you had to use the mouse to select Excel Direct.
You can now exceed the 168 character limit in an Online Inquiry when it is being used to ExcelDirect the results, as there is no width limit in Excel. A warning is issued you try to print a report and the fields will wrap to an extra line.
The vitalEsafe upload progress dialog has been improved and the progress bar now accurately shows the percentage. It is no longer necessary to install the vitalEsafe patch.
Problems Fixed
The Retrieve Sales Data and Scan Sales Data functions in SalesAnalysis 9.0A trimmed leading spaces from the Item Number of multi-segment items. There was no problem for items that did not have a space as the fist character of the Item Number.
The Online Inquiry report bar charts had incorrect values for Territory.
In SalesAnalysis 9.0A, the Item Description showed as asterisks in the On-line Inquiry summary when it should not have if the 'Use desc from SRTRANS' option was on in the Company Profile. In 9.0B, the Item Description from the 1st transaction detail for this item is displayed in the summarized view.
In the Edit Sales Data function in SalesAnalysis 9.0A, if you changed a record and clicked the Next button instead of the OK button, after receiving the prompt asking if you wanted to save the changes an error message was displayed and the next record was deleted.
There was a problem in SalesAnalysis 9.0A sending data to Excel Direct. After, if Pivot Tables in Excel 2007 or 2010 were used to summarize, the resulting values displayed as a ‘1’.
If you exported more the 65,535 transactions to an Excel file the progress bar displayed a percent higher than 100, although if you exported to a .xlxs the file was complete (.xls files for Excel 2003 and earlier are limited to 65,535 rows in any case).
When converting data to 9.0A the message "Error adding record to Adagio Sales Analysis 9.0 Transactions, record already exists." was encountered in rare cases where transactions had a blank dates from some earlier problem with the database. The conversion now handles and corrects these bad records.
For filters based on a range of a right-justified field (such as customer number, single segment item number, etc.), additional records were selected that should not have been. For example, if the range is from 1 to 2, then not only would records 1 and 2 be selected, but also 10, 11, 100, 101 etc. You will need to edit and save any such existing filters to correct them.
The Find did not work correctly for selecting a customer with a leading zero in the Name field, such as for a numbered company.
SalesAnalysis displayed the error "2018 Error field number invalid" in some cases when you started the program if you use Adagio Invoices 9.0A but do not have Adagio Inventory installed.
When installing Adagio to a computer or server where no Adagio modules had previously been installed, if you installed an Adagio module that does not use the Crystal print engine first (such as Lanpak or GridView), when you installed SalesAnalysis you received the error "Adagio has been established on destination folder: [x:\SOFTRAK]. Yet the install cannot detect the corresponding Reports Tables..." and were unable to proceed. If the first module installed uses the Crystal print engine there was no problem.
The updated version of vitalEsafe no longer triggers a workstation install if it has already been installed by the workstation install for another Adagio module. This is also the case when installing Adagio for use with Remote Desktop Services (Terminal Services in Windows Server 2008 and previous versions).
When running any Adagio module that installs vitalEsafe (or WebSafe as it was previously known as) on a Windows 7 (or Vista) station, in some cases the auto-workstation install ran every time you started the application, even if you had done a workstation install. This happened if the user was not an Administrator on their own machine (the default for a new computer) but rather a Standard user, and User Account Control (UAC) was on, and you had not installed any module with a release date of October 2011 or later and done a workstation install for it on the station. This has been resolved. To resolve this problem for ALL other modules, install any module with a release date of October 2011 or later and do a workstation install for it on the station.