LogicNP Software Knowledge Base And FAQ

[Support]

An application which uses FileView ActiveX Control should distribute the file filev012.ocx along with the dependencies listed above. No other information or files is necessary for distribution. The developer should make sure that the control is registered in the system registry on the end-users' machines. Registration of the control is done automatically by many installation builders during installation of your program, or you can do the registration yourself during the installation of your program. The redistributable file regsvr32.exe can be used for control registration. This registration is required for every ActiveX control to run on a machine.

Note that the above registration is different from 'registering the control', that is entering the registration codes ( username and code ) after you have purchased the control. This registration should only be done on the developers' machines after you have purchased the licenses for the control. Under no circumstances should the developer make available to the end-user or their systems, the sensitive registration and licensing information ( username and codes ) either explicitly or implicitly. Please read the License Agreement for further information. The FileView ActiveX Control handles registration and licensing by embedding the developer's license information in the application. When this application is run, this information is automatically retrieved and verified if the control is licensed.

The end-users of my program get one of the following error messages when they run the program :
"Runtime error 429: you don't have the appropriate license to use this functionality"
"Run-time error '13': Type mismatch"

This problem can occur if your program uses FileView v4.3 or earlier, because all these versions of FileView had the same GUID and a filename of fileview.ocx. The problem occurs because the different versions of FileView are not binary compatible with each other. Your program might be compiled with one version of FileView and the end-user might have a different version. This can happen if the end-user installs another program which uses a different versions of FileView. In this case, the version of FileView that comes with the other program will replace the one that your program uses.

Till version 4.3, all versions of FileView had the same GUID and a filename of fileview.ocx. However, starting with version 5.0, each version has a different GUID and filename ( e.g. v5.0 has a filename of filevw50.ocx ). This ensures that multiple versions of FileView can coexist on the same machine.

Therefore, if your program uses FileView v5.0 or above, then you wont have this problem. However, if your program uses earlier versions, then the only way to solve the problem on the end-user's machine is to make sure that his machine has only one version of FileView installed and that version is the same version that your program uses. To ensure that the end-user has the correct version he should search all his hard disks for fileview.ocx and filevw*.ocx and unregister ( using regsvr32.exe ) and remove all such instances. Then he should reinstall your program.