Can ActiveX Controls be embedded in a VB Application ? 1

[kcoder9]

Hi everyone,

At our company, we are planning to buy few ActiveX controls for enhancing the Graphical Interface of the Applications we develop using VB.

How can we ensure that the user will not be able to use the controls installed with our application for developing new applications?

Are there any methods that can enable us to completely embed an ActiveX control in the Executable (.EXE) file so that the control is not available as a separate entity in the user's PC.

Can someone please help? Thanks!

 

[mattKnight]

Not really, what you want goes against most of what active-x (ocx, dll and exe) tries to achieve.

If you are buying the control and redistributing it aspart of your application isn't it the responsibilyt of the supplier of the control to protect their software? By that I mean, you need to ensure that your licence agreement does not allow further re-distribution of elements of your application.

Likewise, there is development time licencing built in to the active-x model, which means that controls can be require a design time licence, but work in runtime without it.

Take Care

Matt
If at first you don't succeed, skydiving is not for you.

 

[AndyLee100]

Can it be added to the rsource file?

Andy

 

[strongm]

As mattKnight was trying to say, most serious ActiveX controls come with both a design time and a run time licence. When you distribute your application you simply do not distribute the design time licence (most ActiveX developers will actually prohibit such distribution anyway). As a result, the end user gets an ActiveX control that they can use quite happily in the application you distribute, but which they cannot use in the development environment

 

[mattKnight]

As mattKnight was trying to say

Quite - maybe next time i'll be clearer! ;-)

Take Care

Matt
If at first you don't succeed, skydiving is not for you.