CLIPS ActiveX Frequently Asked Questions

Web Page updated April 13, 2005

HomeButton.jpg (17266 bytes)

OCX/ActiveX Licensing, DLL Licensing, DLL Faq's, Service Packs, What Is? Deploying an Application

Service Packs

>What Windows NT Service Packs are needed with the latest version of the OCX/ActiveX?
Service Pack 5 or better is needed for NT systems.

OCX/ActiveX Licensing

>We need to use the OCX for more than one project... do we need more than one license?
No. You only need 1 license per designer seat (Per PC). Runtime distribution is free.

>Does purchase entitle me to future enhancements?
Yes, all enhancements through 1.x will be free, and you get a special upgrade price to 2.x, 3.x etc.

>Does a purchase of the ActiveX Control permit me to develop and sell applications that use it?
Yes!

DLL Licensing

>How is the CLIPS DLL licensed?
The regular CLIPS.DLL (not the COM InProc server version -- CLIPSInProcSvr.DLL) is free to use in your own applications, redistribute it as you wish so long as it is not modified in any way (the binary DLL image).

What Is?

> Is the CLIPS ActiveX/OCX Year 2000 compliant?
Yes. But be careful to make sure that the application you are developing is Year 2000 complaint as well!

>What is the difference between the purchased version and the download version?
The only difference with the purchased version is that you get a License file. The WEB License file allows the ActiveX Control to be used on a web server, as well as in C++, VB, VBA applications only. The Professional License file allows the ActiveX Control to be used in C++, VB, VBA applications only.  The Education License file allows the ActiveX Control to be used in C++, VB, VBA applications but expires after one year.

>Do you ship the code or is it downloaded from your site?
Although we ship you the media the only real thing you need to start using the download version one is the LIC and/or LPK file which can be purchased on the Athena Web Page.

>Please explain the difference between the download products on your Web site.

WebCLIPS is a server side CGI application.

CLIPS.DLL is simply a DLL, (not a COM DLL nor an In-Process-Server). The DLL is unsupported/free.

ActiveX CLIPS can be used directly in VB, VBA, etc.. since it is a COM object. It can also be used in CLIENT SIDE web processing, rather than server side, (a la CGI). The ActiveX version also provides more features than the DLL alone, some functionality that would have to be coded into a DLL application is already wrapped up into the ActiveX control functionality. CLIPS ActiveX is fully supported.

The Professional Editions ActiveX CLIPS can be used directly in VB, VBA, etc.. since it is a COM object. It can also be used in CLIENT SIDE web processing, rather than server side, (a la CGI).

>What is WEB Enabled?
Web enabled means we provide you the License file to allow it to be used on a web server environment as opposed to simply being embedded in a VB/VBA application.

>What is Authenticode?
Authenticode means we provide you one that has been SIGNED, (via a Verisign class 1 certificate), for use in situations where unsigned/unauthenticated ActiveX controls, (via the web only), would not be allowed. Unsigned will still work exactly the same, you just have to set the browser security to LOW.

IIS

>Can we use the Web enabled version of the CLIPS ActiveX for Windows on an IIS Server?
Not presently supported.

DLL Faq's

The DLL is NOT (I repeat NOT) a COM server.

The CLIPS.DLL has only one dependency and that is the MSVCRT.DLL (the C Runtime library). This needs to be version 6.0 or later. Sine this is normally installed with the operating system and upgraded with OS Service packs or other patches, you normally need not worry about it. It wouldn't hurt to check though and make certain you have the right value.

If you are making extensive use of OLE controls, you might want to also be sure the Windows 95 OLE patches are applied.

Some folks missed the release notes update on the latest build of the DLL (which is on the website where you download it). You need to be aware that you will need to regenerate any binary save files which were saved with a previous version of the DLL or with a generic version of CLIPS as the binary file format has changed.

Deploying an Application

The CLIPS OCX has the following dependacies:

1)CLIPSActiveXControl.ocx
2)CLIPSActiveXControl.tlb -- if you used early binding
3)MSVCRT.DLL (version 6.x) -- usually already there*
4)MSVCIRT.DLL (version 6.x) -- usually already there*
5)MFC42.DLL (version 6.x) -- usually already there*
6)CLIPSActiveXControl.lic

-OR-

5)CLIPSActiveXControl.reg -- if you use this then have your installation program apply this script to the registry of the target machine. After that the REG file is no longer needed, nor is the LIC file required as the license information will be picked up from the registry.

When the OCX is installed it must be registered. You can use the auto registration function of the install builder software or launch :

regsvr32 CLIPSActiveXControl.ocx

If the install builder you are using doesn't have the auto registration feature. Regsvr32.exe will reside in the SYSTEM/SYSTEM32 directory of the target machine.

*Older versions of these might be present if the target machine is not on the latest OS service packs or patches. In that case the newer ones MUST be used.