Release Date: 13 May 2016
Requirements
- Windows 2003, Vista, Windows 7, Windows 8, Windows 8.1, Windows 10
- Texpress 9.0.01 or later
- TexAPI 6.0.012 or later
- Perl 5.8.8 or later
New Features
Reporting Formats |
New report formats have been added to improve report generation and loading performance. It is now possible to report directly to an Open Database Connectivity (ODBC) data source or to an ActiveX Data Objects (ADO) Recordset object. The new report types are:
Existing Crystal Report and Microsoft (Excel, Power Point and Word) report types that currently connect to an ODBC data source can be changed to use an ADO Recordset. A description of ADO reporting can be found in the ADO Reports documentation: International English | US English |
Unicode Support |
Full support for Unicode has been added, including:
A complete description can be found in the Unicode documentation. Download a Unicode Cheatsheet: International English | US English |
Improvements
Performance Improvements |
Performance improvements have been made to sorting, exact matching, reporting and attachment searches in Vitalware. Some examples of the observed performances improvements are:
|
||||||||||||||||||||||||||||||||||||||||
Record Transmit Improvements |
In order to transmit a record between systems an update to the record being transmitted was required. Records may now be transmitted without any update, thus preserving their state. |
Issues Resolved
Issue | Resolution | |
---|---|---|
When a payment type is incorrectly assigned in the invoices module and reversed out, the resulting invoices ledger entry is assigned to the same till which effects balance reporting. |
The restored invoice entry is no longer assigned to a till, allowing end of day to balance correctly. |
|
A newline may be entered into the POS address field, which causes subsequent address formatting to be incorrect. |
A newline is no longer able to be inserted into the POS address fields. |
|
For systems that were multi-lingual it was possible that an Access Violation occurred when users were trying to login. |
An Access violation no longer occurs when users login. |
|
Certain systems experienced difficulty registering a late registration on 29 Feb 2016. |
Late registration now correctly registers on 29 Feb. |
Upgrade Notes
See Upgrade 2.6 to 3.0 for details.