"object or class does not support the set of events"

  • Thread starter Thread starter Kevin
  • Start date Start date
K

Kevin

I KNEW I should never have upgraded (clean install, after "upgrade"
killed my machine) W2k to XP!

After the install I have only Office 2003 on my machine (previously had
Office XP, after the upgrade that's gone, since I - apparently stupidly
- only installed Office 2003). I'm now getting the above message on
code which has worked fine previously, and works fine on a client
machine with Win/XP and Access/XP. Obviously MS hath taken away again!
The code that breaks (at least the code that breaks that I've found so
far) is

Me.Parent!fPeopleCategories.Form.RecordSource = tSQL

(The fPeopleCategories subform has an MSComm32.ocx on it, and I've just
had to get a copy of that and register it to make it work. (I
previously had Visual Studio 6, which included it, and now only have
..NET, which doesn't.) In another form the comm control appears to work
fine. I mention this because Google has turned up answers to the error
above which reference ActiveX control problems.)

Help would be appreciated. My pile of rocks to throw at people who live
in Redmond gets higher and higher.

Kevin
 
Probably a different version of MSComm32.ocx you have now and before. try to
recreate fPeopleCategories, first inserting MSComm32.ocx, then copy/paste
other controls/code
 
Finally got it resolved. I had to run regsvr32 on MSComm32 as well as
register it in Access. Why it would cause this error message is a mystery.

Thanks,

Kevin
------------------------------------------------------
Probably a different version of MSComm32.ocx you have now and before.
try to
recreate fPeopleCategories, first inserting MSComm32.ocx, then copy/paste
other controls/code
-- Alex Dybenko (MVP) http://Alex.Dybenko.com http://www.PointLtd.com
 
I think I've finally found the "ultimate answer" to this, at least if
you're having this problem for the same reason I did.

If you've developed Access projects with some version of VB6 on your
computer, and now have only Visual Studio .NET, and used ActiveX
controls from VB6 in your Access projects (like MSComm32 or the Common
Dialog Control) which are no longer included in VS .NET), there is an
answer.

Double-Click on VB6Controls.reg on the Visual Studios.net 2003 disk 2
\extras folder to have VB 6 activex controls licensed. You may also have
to find the .ocx controls you were using, copy them to ..System32 and
run regsvr32 on them before doing this... I haven't gone through all the
permutations and combinations. If you only copy the missing .ocxs to
...System32 and run Regsvr32 on them, you may be told you don't have a
license to use them.

Why the lack of, or lack of "licensing" of, VB6 controls causes the
error messages above is a mystery I'd rather not examine. I already
have my own opinion of the MS designers. And that's far better than my
opinion of the guy who's responsible for the KB.

Hope this saves someone the 8-odd hours it cost me to find the answer.

Kevin
 
Hi Kevin

I am currently developing an interface betwen MS ACCESS2003 and a device
connected via a comm port. I came across your messages and thaought to ask
you the following.

I don't have VB6 but .NET. How do I get MSCOMM32.OCX or where would it be
..NET REference library.

Aprreciate your help

Regards
Kassam
 
Back
Top