I have a set of applications that use an ActiveX control. If the users do not have the ActiveX control, can I copy the control files to their computers? Or does this cause a licensing issue? They have a licensed version of the software we are using (Microsoft Access), but the install we used was missing a few files or not allowing them to be included. Will copying from my computer to theirs copy my license info as well? Or is the licensing verified at run time using the license on each person’s computer?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Can I copy an ActiveX control to another computer?
- Thread starter sedrisco
- Start date
Sedrisco,
this is a good question. Everything I have read insists that ActiveX controls are self-registering, and the app using them only needs the file name and location, and calls DLLRegisterServer() using the path and filename. The OCX only gets registered at this point, not before. If this is true then it should not matter since it does not get registered anyway until runtime.
As far as licensing info, I can't help with that.
I would caution though that if the installation would not allow the OCXs to be installed, it's probably for a good reason - such as the dependencies do not exist on the target system. So probably the OCX needs some minimum version of some system DLL and the DLL is either not there or not the right version.
this is a good question. Everything I have read insists that ActiveX controls are self-registering, and the app using them only needs the file name and location, and calls DLLRegisterServer() using the path and filename. The OCX only gets registered at this point, not before. If this is true then it should not matter since it does not get registered anyway until runtime.
As far as licensing info, I can't help with that.
I would caution though that if the installation would not allow the OCXs to be installed, it's probably for a good reason - such as the dependencies do not exist on the target system. So probably the OCX needs some minimum version of some system DLL and the DLL is either not there or not the right version.
- Status
Similar threads
