ActiveX Licence Issue

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Dave K - 01 Mar 2007 13:10 GMT

Hi all,

I work for a large corporation in the UK where we use a mix of win2k systems
and XP. When trying to add an activex control(common dialog for example) to a
form on any of the Win2k machines it works fine, on every XP machine we get
an error stating that we do not have the licence required to use this
ActiveX/OCX and to contact the supplier of the control. This of course being
Microsoft in this instance but i can not find any documentation relating to
this issue on the web and has got the whole of our systems team stumped.
It is the same fully licensed version of Access as we use on both Win2K and
XP. We have also tried installing every version of access we have (97 - 02)

I have found some reference to group policies with XP and visual studios but
the solutions would not help with access.

We can not see any issues with our group policy but wondered if anyway has
heard or seen anything like this before?

Your help on this matter is as always greatly appreciated!

Many thanks & regards,
Dave K

Reply to this Message

Alex Dybenko - 01 Mar 2007 14:11 GMT

Hi,
for common dialog I suggest to use API, this will work on both:
http://www.mvps.org/access/api/api0001.htm

Signature

Best regards,
___________
Alex Dybenko (MVP)
http://alexdyb.blogspot.com
http://www.PointLtd.com

> Hi all,
>
[quoted text clipped - 26 lines]
> Many thanks & regards,
> Dave K

Reply to this Message

Dave K - 01 Mar 2007 14:33 GMT

Many thanks Alex.

I have already been using this code to get round the issue as a temp measure
but the licence issue doesn't just affect the common dialog, i was just using
it as an example. Its quite a few of the MS ActiveX controls but not all of
them.

I have read another thread called "Rich Textbox Control 6.0", there is
mention of changing the registry as this is the cause of the problem in XP
for that ActiveX control. I think it must be something very similar along
those lines.

Any more adivse would be greatfully received!
Many thanks,
Dave K

> Hi,
> for common dialog I suggest to use API, this will work on both:
[quoted text clipped - 30 lines]
> > Many thanks & regards,
> > Dave K

Reply to this Message

Alex Dybenko - 01 Mar 2007 20:55 GMT

Hi,
some of MS ActiveX controls require a design license in order to insert
control on a form. for some controls this license comes with office
developer, for some - with visual studio 6. but once inserted - it should
work on any PC, where this control is registered correctly.

Signature

Best regards,
___________
Alex Dybenko (MVP)
http://alexdyb.blogspot.com
http://www.PointLtd.com

> Many thanks Alex.
>
[quoted text clipped - 54 lines]
>> > Many thanks & regards,
>> > Dave K

Reply to this Message

Dave K - 02 Mar 2007 11:47 GMT

Great, i didnt think to try my laptop with VS installed, it works great.
What a simple answer, strange how it works on Win2k though even thought its
exactly the same version of access and without any dev tools installed.

Anyways, many thanks Alex!
Dave

> Hi,
> some of MS ActiveX controls require a design license in order to insert
[quoted text clipped - 60 lines]
> >> > Many thanks & regards,
> >> > Dave K

Reply to this Message

Tony Toews [MVP] - 02 Mar 2007 22:58 GMT

>I have already been using this code to get round the issue as a temp measure
>but the licence issue doesn't just affect the common dialog, i was just using
>it as an example. Its quite a few of the MS ActiveX controls but not all of
>them.

Agreed. But given the distribution and version problems I do my
absolute hardest to stay away from controls.

How do you get rid of troublesome ActiveX Controls/references?
http://www.granite.ab.ca/access/referencetroubles.htm

Tony

Signature

Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

Reply to this Message