What's New in Office Connector 2.04.0082
- Significantly improved the performance of the TSGLAmount financial function. In some cases, refresh will be 800% faster than in previous versions.
- Updated the TSSampleYear function based on current sample data.
- Made various changes to the installer to streamline and improve it.
- Corrected an issue in Office Connector Financials where accounts of type "Suspense" were being treated as income statement accounts. Now, these accounts are handled as balance sheet accounts.
- Resolved an issue where an unexpected error could be reported when a opening a report that was saved with a reference to a Sage 300 CRE data folder that is no longer valid.
- Resolved an issue where the Filter applied to a query range would not be reapplied automatically after refresh.
- Resolved an issue where editing a query via the Query Wizard and adding parameters would result in more parameters being added to the list each time. Now, if the conditions of the query are changed, the existing parameters will be cleared an reset.
- Non Office Connector queries are now ignored by Office Connector.
- With the 18x version of the Sage ODBC Driver, files may remain in use after they are no longer needed. This could cause a problem in Sage applications when a user would attempt to run a task that requires exclusive file access. Per Sage knowledgebase article, implemented a connection setting (KeepFilesOpen=0) that instructs the Sage 300 CRE ODBC Driver to close files when finished. For more information, click here.
- Resolved an issue where an error message could be reported when attempting to import JC Misc Worksheet entries.
- Within the SageDesktopOCTasks utility (which creates Office Connector shortcuts in Sage Desktop), changed branding from "Timberline" to "Sage 300 Construction and Real Estate".
- Previously, if the Pervasive engine was offline, Office Connector would display multiple consecutive message boxes. This has been reduced to one message box.
- Addressed issue caused by Microsoft Update that affected any VB functions that use parameter arrays.