User does not have license required to open ActiveX Control

[Sierras]

I made an Access 2000 database which works fine in Access 2000.
But a couple of users with Access 2003 get an error message when they
try to open a report. Everything else (queries and forms) seem to be
working fine.

The message is, that the user does not have the license required to
open the ActiveX Control. This is strange since there is an AcitveX
calendar control on a form which is working fine. But no ActiveX
control on the reports.

What is that and is there a workaround?
The users have Access 2003 version 11.5614.?

Thanks.

 

[Douglas J. Steele]

Go into the VB Editor, and select Tools | References from the tool bar. Is
there any reference there to an ActiveX control that isn't being used? If
so, remove the reference.

 

[Sierras]

I unchecked everything that Access would allow and now only have the
following checked;

Visual Basic for Applications
Microsoft Access 9.0 Object Library

But the user still get the Do not have the license required to use the
ActiveX control message.

Any other ideas as to what this could be?

 

[Sylvain Lafontaine]

If you try a Recompile All from the Debug menu, any particular error
message?

 

[Sierras]

There is no error message when the user compiles the database.

The thing is, I don't have Access 2003 and the users are remote from
me so it's difficult for me to troubleshoot this problem.

There are a couple of things that I don't understand about this
problem:

1) When the user launches the Access Database, they get some Access
security messages about possible virus in Access code and that they
have to install some update to Microsoft Jet 4.

2) When I have them go into the VB editor and check for references,
they have MS Access 11 Object Library. But I made the database with
version 9. Could this be a possible problem?

Also, I've been reading something about about sandbox mode. I had the
user check it in the registry and change it from 3 to 2 which is
supposed to be the default. But that didn't work either. I'm
wondering if I should ask them to turn it off altogether (if this has
anything to do with it..)

The other thing I have asked them to do is to update their versions to
the latest Service Patches. And check their Windows XP installation
as well for any update to that Microsoft Jet error they were getting.
Hopefully this will solve the problem, but if not, I'd appreciate any
other troubleshooting assistance.

Thanks...

 

[Sylvain Lafontaine]

When I said recompiling all modules, I mean doing it from Access 2003. Try
asking one of your user to do so and after that, ask him to repeat the
process after adding a useless reference to make sure that all modules are
really recompiled.

Also, ask them to try with the /decompile option.

It is normal that there is a change for some of the references in going from
A2000 to 2003 but as you don't have A2003, it may be hard to find the error
here. Did you try using the Remote Desktop Connection? Might be a good
time to start fiddling with it.

The message about a possible virus in Access code is a *feature* of A2003
(and a real pain in the a** by the way). Your users will have to lower
their security setting: Tool | Macro | Security -> Low.

(If they have upgraded from a previous version of Access, this option might
be missing from the menu, see http://support.microsoft.com/?kbid=833219 for
how to solve this.)

 

[Sierras]

I did talk to one of the users with Access 2003 and asked to
recompile. But maybe I didn't direct the user to the right toolbar.
I asked to press ALT|F11 and then to go to the Debug menu and press
the re-compile.
But there is only a "Compile" database available. I don't know where
to find the "Recompile all modules" dialog. Was this the correct
procedure that you were talking about? And what do you mean by adding
a useless reference. Is something like "utility" a useless reference.
One more thing - I asked the user to remore all references that they
could - even calendar control. It's funny that the form with calendar
control still worked normally.

Also, I will be asking the user to lower their security to see if that
makes a difference.

Thanks..

 

[Sylvain Lafontaine]

Sorry, my error: with Access 2003, it's only "Compile" and not "Compile
all".

In the References dialog, adding a dummy reference will make sure that all
modules recompiled because each time there is a change in references, all
modules are marked to be recompiled. If there are some incompatibility with
the compilations of the mdb on your system and on their system, the
procedure might uncover it.

It is not necessary to set a reference to the calendar control to create
one or call it; it's depend on the way you are making these creations and
calls. References are only necessary for early bindings, not late bindings.

 

[Sierras]

Just wanted to let you know that the Tool | Macro | Security -> Low
setting worked. Since I don't have Access 2003, I would probably
never have found it.

Thanks for your help.