object or class does not support the set of events

  • Thread starter Thread starter Daniel Polak
  • Start date Start date
D

Daniel Polak

I have a form in a MDE that works fine on pc's with Access 2000 (or just
the 2000 runtime).
When I use that same form in the same MDE on a pc that has Office XP
installed (even with Access 2000 runtime installed as well) I get the
error "object or class does not support the set of events" when I close
the form or when the mouse moves over a the DBITech ctMDay ActiveX
control that I use.

The MDE has these references on Access 2000:
VBA: C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6\VBE6.DLL
(6.0.89.67)
Access: C:\Program Files\Microsoft Office\Office\MSACC9.OLB (9.0.0.2719)
stdole: C:\WINDOWS\system32\stdole2.tlb (3.50.5014.0)
ADODB: C:\Program Files\Common Files\System\ado\msado21.tlb (2.81.1117.0)
DAO: C:\Program Files\Common Files\Microsoft Shared\DAO\dao360.dll
(3.60.8618.0)
CTDEDITLib: C:\DBITech\SolPIM3\Components\ctDEdit.ocx (5.0.0.1)
MULTIDAYLib: C:\DBITech\SolPIM3\Components\ctMDay.ocx (5.0.0.4)

On the pc with Office XP VBE6.DLL is a later version the rest of the
files are the same version as on the pc with Access 2000.

Any clue why the form is giving an error on one pc but not on the other?

Daniel
 
Maybe try registering the Multiday OCX on the XP PC?
regsvr32 "C:\DBITech\SolPIM3\Components\ctMDay.ocx"
 
==== Original message from B_A_R_T_M_A_N at 17-3-2007 0:56
Maybe try registering the Multiday OCX on the XP PC?
regsvr32 "C:\DBITech\SolPIM3\Components\ctMDay.ocx"
Click to expand...
I've done that (several times) and Access sees it but it's still not
working.
 
Do the makers of this control claim that version is compatible with
2002 (XP)?
If so, perhaps they could determine the source of the error.
 
==== Original message from storrboy at 17-3-2007 15:04
Do the makers of this control claim that version is compatible with
2002 (XP)?
If so, perhaps they could determine the source of the error.
Click to expand...
It should to be compatible and they were unable to find a solution.

Regards,

Daniel
 
Do circumstances allow you to make a XP MDE without relying on the
2000 runtime?
If that worked, then I'd have to suspect a version conflict between
2000 and XP.
 
==== Original message from storrboy at 17-3-2007 15:37
Do circumstances allow you to make a XP MDE without relying on the
2000 runtime?
If that worked, then I'd have to suspect a version conflict between
2000 and XP.
Click to expand...
I initially ran it with the full Access XP that didn't work. I then
tried running it on the same machine with Access 2000 runtime and that
didn't work either.
 
==== Original message from storrboy at 17-3-2007 15:37


I initially ran it with the full Access XP that didn't work. I then
tried running it on the same machine with Access 2000 runtime and that
didn't work either.
Click to expand...


I mean as an actual 2002 file format with 2002 (Access10) references.
The only reason I can think of for this to happen as you describe is
broken/invalid or conflicting references. Otherwise I'm afraid its
beyond my experience. Sorry.
 
==== Original message from storrboy at 17-3-2007 19:29
I mean as an actual 2002 file format with 2002 (Access10) references.
The only reason I can think of for this to happen as you describe is
broken/invalid or conflicting references. Otherwise I'm afraid its
beyond my experience. Sorry.
Click to expand...
No reason to be sorry, thank you for your help!

It looks like I will have to try making an Office XP MDE or do a fresh
of install of Windows with Access Runtime and then see what happens if I
add Office XP.

Daniel
 
Back
Top