MS Access 2003

  • Thread starter Thread starter Fritz Anton
  • Start date Start date
F

Fritz Anton

Hi,
I've just updated from Office XP to Office 2003. Everything went smoothly
and appears to work alright. An Access database, which worked without a flaw
under Access XP, suddenly became very stubborn and issues error messages
like this one (translated from German):

"You do not hold the licence necessary to apply this ActiveX-Control
Element.
You have either tried to open a form containing an OLE-Object or an
ActiveX-Control Element, or you you tried to create an ActiveX-Control
Element.
The necessary licence(s) can be obtained from the company distributing the
OLE-Object or ActiveX-Control Element."

The incriminated element is an ordinary macro which checks and sets the
value "Locked" of an ordinary tickbox representing a yes/no datafield.
The last sentence of the error message is a jewel in its own right....

Any suggestions out there?

Fritz
 
Fritz:

I've had exactly the same problem and have been unable to track down the
solution. The funny thing is that, in a few cases, there have been no calls
to any Active X object. One of the oddest instances I've encountered is in
a normal print routine, with no special calls, which returns the "no
license" message.

If I discover a solution, I'll post it here.

jwm
 
Thank you for your response! In the meantime, I have been looking at FAQs,
Knowledge Bases and newsgroups till I got cross-eyed, no remedy found.

Fritz
 
Hi,

I found something which I should not call a solution (because I have no idea
how it works), but a possible "fix":
I created a new empty database in Access 2003 and imported all files
(tables, forms, macros, modules etc) from the silly database. The stupid
error message was gone, I jubilated.
Give it a try and tell me if it worked for you too.

Fritz
 
Hi Fritz,

Typically the problem you experienced is associated with macros that are
using expression that are being blocked by the new Jet sandbox mode that is
available in Jet 4.0 SP8, but in those cases, copying the macro to a new
database should not change the error.

What exactly is the macro that is causing the error doing? You mention
setting the Locked property, are there any conditional expressions being
used to determine when the Locked property is set? Would it be possible for
you to use the Documentor in Access (Tools | Analyze | Documentor) to
output the information about the macro and add it to this thread?

Thanks for your feedback.

--
Regards,
Mike Wachal
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Hi Mike,

The "offending" macro goes like this:
Check
SetValue [LOANTICK].Locked
[ON LOAN]

SetValue [LOANTICK].Enabled
Not [ON LOAN]
...
LOANTICK is a standard tickbox in a form, ON LOAN is a Yes/No field of the
underlying data table - nothing fancy at all. When I added condition "False"
to jump these instructions, the rest of the macro (including several
instances of locking/enabling other control elements) worked fine. Deleting
the tickbox, re-inserting it did not make any difference.
Another infuriating error occurred when the program stubbornly refused to
execute a "DoCmd.ApplyFilter..." or DoCmd.OpenForm..." instruction in VB.
As I happily announced, these problems went away - I worked frantically at
night to reanimate the database and I might misallocate action and result:
Most problems disappeared with importing all elements into a newly created
database, some went away by miracle - now they didn't work, suddenly they
did, almost like a machine running in ... are there any self-healing
capabilities in Access?

Fritz
 
Thanks for the additional information Fritz. There is nothing about the
macro you describe that would be affected by the new expression blocking in
Access 2003. Further more, expression blocking does not affect VBA code, so
those errors just seem to muddy the water.

I'm happy to hear that the errors have gone away, these types of miraculous
recoveries don't make troubleshooting any easier, but it's better to have a
working database than one throwing errors, so I try not to look a gift
horse in the mouth.

One final idea I have if you still have the offending database around and
if it is still not working. Pop into the VBE and take a look at the
references to see if any are missing. It is common to see odd errors with a
missing reference, and those references would not be a problem after
importing to a new database since the new database would have only the
default references.

Just an idea.

--
Regards,
Mike Wachal
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Mike,

The "offending" macro goes like this:
Check
SetValue [LOANTICK].Locked
[ON LOAN]

SetValue [LOANTICK].Enabled
Not [ON LOAN]
...
LOANTICK is a standard tickbox in a form, ON LOAN is a Yes/No field of the
underlying data table - nothing fancy at all. When I added condition "False"
to jump these instructions, the rest of the macro (including several
instances of locking/enabling other control elements) worked fine. Deleting
the tickbox, re-inserting it did not make any difference.
Another infuriating error occurred when the program stubbornly refused to
execute a "DoCmd.ApplyFilter..." or DoCmd.OpenForm..." instruction in VB.
As I happily announced, these problems went away - I worked frantically at
night to reanimate the database and I might misallocate action and result:
Most problems disappeared with importing all elements into a newly created
database, some went away by miracle - now they didn't work, suddenly they
did, almost like a machine running in ... are there any self-healing
capabilities in Access?

Fritz

Mike Wachal said:
Hi Fritz, Would it be possible for
you to use the Documentor in Access (Tools | Analyze | Documentor) to
output the information about the macro and add it to this thread?

Thanks for your feedback.
Click to expand...
Click to expand...
 
Back
Top