B
ben h
Hi all,
Full error message is:
"The expression OnClick you entered as the event property setting
produced the following error: License information for this component not
found. You do not have an appropriate license to use this functionality
in the design environment."
I've read through a number of posts in several ngs about this error -
most refer to problems with versions of Visual Basic (i.e. this known
issue: http://support.microsoft.com/default.aspx?scid=kb;EN-US;194751),
or installing older Office products after/over/alongside newer versions.
First thing is the error is appearing on my client's PC while running an
Access 2003 MDE, and not while in the design env on my PC.
Second thing, my client's PC doesn't have VB, nor do I. I have VS.NET
2002 installed however.
Third, the error appears when clicking a form control that attempts to
instantiate Visio via automation.
Finally the error only happens on two client machines so far out of
about a hundred.
I think the error is something to do with the client perhaps installing
an Office XP/2000 product after installing Office 2003 perhaps. Can't be
sure.
Has this happened to you? Has anyone got any other ideas? What can I try
without having free and unrestricted access to my client's PCs?
Cheers!
Ben
Full error message is:
"The expression OnClick you entered as the event property setting
produced the following error: License information for this component not
found. You do not have an appropriate license to use this functionality
in the design environment."
I've read through a number of posts in several ngs about this error -
most refer to problems with versions of Visual Basic (i.e. this known
issue: http://support.microsoft.com/default.aspx?scid=kb;EN-US;194751),
or installing older Office products after/over/alongside newer versions.
First thing is the error is appearing on my client's PC while running an
Access 2003 MDE, and not while in the design env on my PC.
Second thing, my client's PC doesn't have VB, nor do I. I have VS.NET
2002 installed however.
Third, the error appears when clicking a form control that attempts to
instantiate Visio via automation.
Finally the error only happens on two client machines so far out of
about a hundred.
I think the error is something to do with the client perhaps installing
an Office XP/2000 product after installing Office 2003 perhaps. Can't be
sure.
Has this happened to you? Has anyone got any other ideas? What can I try
without having free and unrestricted access to my client's PCs?
Cheers!
Ben