4.2.1 Identify the Type of Windows 7 Operating System (32-Bit vs.
64-Bit Operating System 32-Bit Operating System If you are not using Windows 7 or are using a 32-bit Windows 7 on the scan PC, see Section 184.108.40.206 Access the OCX V11 Files (for 32-Bit Windows 7 or Previous Versions of Windows).If you have not already ended Kofax services and closed the RSA , see Section 220.127.116.11 Close Kofax and Disable Kofax Services and then return here.Regardless of whether this is a new install of Kofax or a reinstall of the just OCX files, you must download different OCX files for this 64-bit machine.Thanks to Bob, I am now aware that I have somehow not managed to change this vbp property. So in a similar "OCX could not be loaded" situation one possible way of resolution is to start a new project. The difference is a nasty line in my vbp stating "No Control Upgrade=1" which controls the "Upgrade Active X Controls" checkbox in project properties. I am editing my answer in a minute to reflect this finding.Put the control on one of the forms and check the vbp file with notepad to see what version it is expecting. OR A MUCH EASIER SOLUTION: (I have added this section after Bob's valuable comment below) You can open your VBP project file in Notepad and find the nasty line that is preventing VB6 to upgrade the project automatically to 2.1 and remove it: Funny. Then I dug up an old project that uses it and sure enough it has the 2.0 but it loads, compiles, and runs just fine. When you have the check ticked, this line does not appear in vbp and it silently upgrades the OCX to 2.1. Microsoft Data Source Interfaces for Active X Data Binding to do with MSCOMCTL?