All versions of Quillix prior to and including version 4.4 have been deprecated and are no longer supported. While versions 4.5 and 4.6 are still supported, limited bug fixes are available due to the degradation of Internet Explorer and ActiveX technologies upon which these versions were built. Prevalent recommends updating to Quillix Capture version 5 in order to take advantages of new features and the additional security available using SSL with modern browsers.
The Quillix 5.4 Installer will upgrade any Quillix System from version 4.0 and higher. To ensure a smooth upgrade, please take note of the upgrade prerequisites and special considerations noted below.
As with an upgrade of any software, it is strongly recommended that you back-up your existing Quillix database, as well as any files located in process data stores used by Batch Profiles or Document Types, before running the Installer.
Prerequisites
Before running the Installer to upgrade Quillix Capture, you should have the following:
Performing the Upgrade
Obtain either the 32-bit or 64-bit version of the Quillix Capture Installer, and run on the target computer.
Upgrading to Quillix Capture 5.4 from version 5.x is straightforward and simple. After performing a full system backup, run the Quillix Capture 5.4 installer and follow the on-screen directions.
It is strongly recommended that you back-up your existing Quillix database and installation files, as well as any files located in process data stores used by Batch Profiles or Document Types, before running the Installer.
Prerequisites
Before running the Installer to upgrade Quillix Capture, you should have the following:
Performing the Upgrade
Obtain either the 32-bit or 64-bit version of the Quillix Capture Installer, and run on the target computer.
Note: OLE DB is no longer supported as a database connection method. New ODBC data sources must be created in order to upgrade from a previous version of Quillix Capture to version 5.4.
OLE DB No Longer Supported
Starting in version 5.3, OLE DB is no longer supported as a database connection method. New ODBC data sources must be created in order to upgrade from a previous version of Quillix Capture to version 5.4.
Changing Database Brand
Starting in version 5.3, Quillix Capture supports several new database brands such as MySQL and MariaDB. It is important to note that the Quillix Installer will not migrate and existing Quillix Capture system from one database brand to another. In order to run Quillix Capture 5.3 and higher on a non-SQL Server database, a new installation of Quillix Capture must be performed.
Customizations Made to Web Client Files
The following Web Client files are backed up by the Quillix Installer to preserve any custom code, styles and settings that have been changed. These files will be copied in their original locations with the extension of .bk and replaced with the newer version. After installation, the customizations in these files will need to be manually merged with the newer versions of the files in order for them to be recognized by the Web Client.
Service Errors
See the troubleshooting topic Service Errors for more information.
ASP .NET Errors
See the troubleshooting topic aspx Errors for more information.
Desktop Shortcuts for Older Versions
Old desktop shortcuts (4.6 and older) for Server Manager no longer work. Version 5 installs a new Process Manager executable, which may leave 4.6 and older desktop shortcuts and icons unusable. In this case, delete the old icons/shortcuts.
Web Database Lookups 4.4 and Older
If upgrading from 4.4 or older versions, and the wizard-based database lookup has been used, LookupEncrypt.exe must be run. All lookup connection strings are now stored encrypted. Lookupencrypt.exe can be found in the Support folder where Quillix Capture has been installed. Run this utility ONCE, then activate all Document Types and Batch Profiles as the utility updates the design tables only.
Legacy Web Database Lookups
Any Database Lookups using legacy QWebDBPicklist or QWebLookup modules, or custom lookup or validation modules, need to be changed to use the ProgID of the module rather than the name of the WSDL. For example, QWebLookup.IDataExtension should be used instead of QWebLookup.WSDL and QWebDBPicklist.IDataExtension should be used instead of QWebDBPicklist.WSDL. Each Index Field has these settings under the Lookup/Validation settings category.