It should be noted first that you will need to install a licensed version of ComponentWorks on your second machine only if you intend to develop applications on it. If you are planning on just running the applications you develop on one machine with a valid licensed copy of ComponentWorks on another machine then the following information will apply:
In general development environments will embed a license string into the executable automatically upon creation so that controls can be loaded by the application you build in a vendor specified manner. Visual C++ and Visual Basic do this, as should Borland Builder.
Now this generally only applies to controls that are placed in forms at design time and are not created dynamically with something like the CoCreateInstance
function. If you do dynamically load COM objects and expect them to act in a manner consistent with a licensed version, you will have to embed the license string in your code yourself. I'm not sure of how to do this with Borland's tools, but the following link explains how to do it with Microsoft's (note that Borland is not an officially supported environment for ComponentWorks 3.0, although you can generally make it work fine):
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/d671d44f1e5384c386256529007c3672?OpenDocument
Now, by what I have described above you should be able to understand what is required to use ComponentWorks controls on a target machine for your application. Here is another link with some further information about considerations when using ComponentWorks in different environments, just go to the section for Borland:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/4e4a62b3c9a3cda1862569e40082b6ee?OpenDocument
Jason F.
Applica
tions Engineer
National Instruments
www.ni.com/ask
