S
SDF
Licensing controls for use with VB/A has been a confusing topic for me for
years. I have been told a lot of things, but the common theme is that when
you open VB/A the controls that are on the default toolbox are the only
controls licensed for use with VB/A. However, if you have a licensed copy
of VB6 on the development machine you may use them in VB/A.
The question is what if I have machines that will use the application but do
not have VB6 installed on them? Some controls will come up missing, other
may be throw a license error. How can I license and deploy the individual
controls from VB6? Can I legally do that? One option I was told was to
wrap up the VB6 controls that are
used in a VB/A application into an ActiveX Control. Then deploy the ActiveX
control to the individual machines.
I'm sure this has come up before - I found a few posts while doing a Search
but nothing concrete.
Any info appreciated.
Scott
years. I have been told a lot of things, but the common theme is that when
you open VB/A the controls that are on the default toolbox are the only
controls licensed for use with VB/A. However, if you have a licensed copy
of VB6 on the development machine you may use them in VB/A.
The question is what if I have machines that will use the application but do
not have VB6 installed on them? Some controls will come up missing, other
may be throw a license error. How can I license and deploy the individual
controls from VB6? Can I legally do that? One option I was told was to
wrap up the VB6 controls that are
used in a VB/A application into an ActiveX Control. Then deploy the ActiveX
control to the individual machines.
I'm sure this has come up before - I found a few posts while doing a Search
but nothing concrete.
Any info appreciated.
Scott