Thereforeâ„¢ Help

The following are breaking changes as a result of the Thereforeâ„¢ Online v32 release, as well as recommended guidance for dealing with such changes.

Thereforeâ„¢ 64-bit Upgrade
The Thereforeâ„¢ Online v32 release will bring a client side upgrade to 64-bit. With a standard configuration of Thereforeâ„¢, no additional action should be necessary after the upgrade. However, in case of the scenarios listed below, please mind that without following those steps the client may not work after the upgrade.

•Customization projects based on the 32-bit installed API
All customers using customization projects based on the 32-bit installed API should test their integration thoroughly before upgrading their Therefore installation. This includes .net customization projects, as despite .net functioning with both 32-bit and 64-bit modules, whether or not the integration continues to work without change will have to be tested.
It is expected customers may encounter an error message as 'Cannot create instance of <customized class name>'. This may be resolved by re-registering the dll for 64-bit. This can be done by:
-Opening the Command Line
-Navigating to the directory 'C:\Windows\Microsoft.NET\Framework64\v4.x.x\'
-Calling: 'regasm "C:\Path\To\Your\AddIn.dll" /codebase'
In some cases it might be necessary to recompile the dll, it is recommended to recompile customizations such as these for 'AnyCPU'.

•HKLM registry settings are read from the 64-bit part of the registry
As 64-bit applications read all 'HKeyLocalMachine' registry settings from the 64-bit part of the registry, after upgrading from 32-bit to 64-bit, such applications may no longer read such information from the registry. This includes Thereforeâ„¢ settings such as the connection settings, viewing options, Capture client configuration, etc. Most of these Thereforeâ„¢ settings can be configured either to be user specific in 'HKeyCurrentUser' (which is still available after the upgrade), or machine-specific in 'HKeyLocalMachine' (which may be lost as mentioned earlier). Please note that the Thereforeâ„¢ setup copies all such settings from the 32-bit part of 'HKeyLocalMachine' to the 64-bit part. Thus, everything is expected to continue working after the upgrade. However, the setup will not overwrite any existing values. So, if a user had different settings in both parts of the registry, he will use the 64-bit settings after the upgrade and see a different behavior.

•Integrating Thereforeâ„¢ into Tungsten Kofax
As Kofax software is 32-bit, customers have to use the Thereforeâ„¢ 32-bit setup to install either the Capture Client or the Kofax Capture release module in 32-bit.
 
 

•PDF viewing via Adobe Reader in Thereforeâ„¢ Viewer
The 64-bit version of Adobe Reader will be required after the upgrade in case a user has configured this option, as the Thereforeâ„¢ Viewer will now be running in 64-bit.
 
 

•Office Links
When using the Thereforeâ„¢ Office integration, we recommend using the 64-bit version of Microsoft Office. If a user wishes to continue working with the 32-bit version of Microsoft Office, the 32-bit Thereforeâ„¢ API must be installed from the 32-bit legacy setup.
 
 

•SAP Client
Customers using the 32-bit SAP Client will have to install the Thereforeâ„¢ API and Thereforeâ„¢ SAP dll from the 32-bit legacy setup. All users using the 64-bit SAP Client may continue to use it with the new standard Thereforeâ„¢ 64-bit setup without any changes.
 
 

•References to Thereforeâ„¢ Executables
Any references the users have to any of the Thereforeâ„¢ executables may be broken after the 64-bit upgrade. These references, such as shortcuts, will need to be recreated manually after the upgrade.