W
Wayne
A long time ago I wrote an application in VBA for an end user using Excel
2003. Part of that application uses a VB6 OCX. This has worked fine for 8
years until they installed Office 2007 SP2. Now Excel pops up amessage sayind
"License information for this component is not found. You do not have an
appropriate license to use this functionality in the design environment."
The message is right and wrong at the same time. The user does not have a
design-time license for the ActiveX control and never has. They are only
running the VBA Add-In. A design time license should not be necessary for
run-time use.
It seems to me the latest service pack has broken something here. I can't
imagine copyright owners of ActiveX controls wanting to give end users design
time licenses just to "fix" their applications.
So is this broken behavior by design or an unintended side effect that now
itself needs a patch?
2003. Part of that application uses a VB6 OCX. This has worked fine for 8
years until they installed Office 2007 SP2. Now Excel pops up amessage sayind
"License information for this component is not found. You do not have an
appropriate license to use this functionality in the design environment."
The message is right and wrong at the same time. The user does not have a
design-time license for the ActiveX control and never has. They are only
running the VBA Add-In. A design time license should not be necessary for
run-time use.
It seems to me the latest service pack has broken something here. I can't
imagine copyright owners of ActiveX controls wanting to give end users design
time licenses just to "fix" their applications.
So is this broken behavior by design or an unintended side effect that now
itself needs a patch?