Improvements in Monarch 9.01

Monarch 9.01 includes a number of enhancements and bug fixes as shown below.

Monarch 9.01 Network Upgrade

For previous Monarch network updates, it has only been necessary to upgrade the server. However, for V9.01 it is necessary to not only update the Server, but also individual workstations. This is required because Monarch's new Excel functionality requires each workstation to register the ExcelLiv.dll. We apologize for any inconvenience this may cause.

Please note that this two step installation process only refers to Network versions of Monarch. Standalone/single user versions of Monarch continue to need only one step to update. If you are unsure whether or not you have a network version of Monarch, please ask your System admin or click on the add/remove programs icon in your control panel. If you have a network version of Monarch, it will say so in your list of programs. If the listing for Monarch does not contain the word "network", you have a standalone/single user version. If you do have a network version of Monarch, your system admin will need to install the Server Admin portion of the update before you can install the User Workstation update.

Enhancements:

• Alternate Trap Characters Option
  
  • The template editor can now use the Standard or the new Alternate trap characters according to the setting in Input Options.
    
    The Alternate trap characters have been chosen to help compatibility with different languages, so that characters that are commonly used in the language are not chosen as wildcard trap characters. In addition, it may sometimes be useful to use the pipe character as a trap. The characters used in the new Alternate trap set are all low ANSI, (i.e. lower than character code 128) so they will be consistent across all codepages.
• Comments in Project Exports
  
  • The Export Wizard - General page now has a "Comment..." button. This comment works like the comments for linked objects and becomes a part of the description. These comments are only saved in a Project file.
• Ability to save credentials when opening files from SharePoint or FTP locations
  
  • The Options|Security dialog has been updated to allow the storage of a default username and password when using files from SharePoint (HTTP) and FTP locations. These are usually accessed from My Network Places and require the user to respond to an authentication prompt. These credentials can be stored in the registry, by checking the "Make these the default settings" option. These credentials can also be automatically stored in Projects, by selecting the "Save credentials in Projects" checkbox.
• Text export format (fixed-length or delimited) can now be specified
  
  • Prior to 9.00, the text export format was completely determined by the file extension of the export file itself. An extension of "txt" implied fixed-length format, any other extension (except those already having specific meaning such as "mdb", "xls", etc.) implied delimited format. Now the specific text export format may be specified on the File page of the Export Wizard. For example, a fixed-length text export to a file extension of .rpt is now possible, where previously it would have forced an export to a delimited format.
    
    When creating a new export job or modifying a non-text export job, the default text export format is still fixed-length for "txt" extensions and delimited for other extensions. This assures backward compatibility with old projects. Once the text export format has been specified for a particular Project Export job, it gets recorded in the project and honored ever thereafter.
• Enhanced ODBC import performance and filter support
  
  • 9.01 implements more performance enhancements for importing and performing external lookups from ODBC data sources, and implements the enhanced database filtering capabilities introduced in Monarch 9.00 for major OLE DB sources for all ODBC sources.
    
    A new option has been added to the Open Database and External Lookup pages. This has two settings, "Optimize for performance" and "Optimize for compatibility". The Performance setting is not compatible with some ODBC sources, and will attempt to fall back to Compatibility mode if problems are detected. However, in some cases it is not possible to detect problems, so forcing Compatibility mode is the best option if you are encountering issues when opening an ODBC source in Performance mode. The value of this setting is recorded in the Project when opening a Database and in the model when performing an External Lookup.

Bug Fixes:

• Various Excel Export bugs fixed
• Importing DB / DBF fixed
• PDF Import improvements
• XLSX files can now be rendered by Excel Services Web View and are available to Microsoft Office SharePoint Server 2007 KPI views
• Printing individual pages and page ranges past approx 50,000 fixed
• Total Pages header/footer option is now correctly calculated for PDF exports
• Miscellaneous bug fixes

Back to Downloads Page