VB6 debugger does not work anymore? (errors 430 and 0x80004002)
Andrei Suvorov
Could someone help me with problem of running very simple debugging case
with VB6 described below?
My OS: WinXP Proffesional Version 2002 Service Pack 3
I have VB6 ActiveX DLL project "Project1" containing "Class1" with only
"get" property "MyName" returning static data.
With no problem, I instantiate this class and read it's property "MyName"
when it's *not* run under VB6 debugger in any way. E.g. from another VB6
project debugged in different VB6 instance, or from ran or debugged VC++ 6.0
code.
But,
A big problem comes when I try to debug my primitive ActiveX DLL in VB6
using "Wait for component to be created" or "Run executable" options!
On attempt to instantiate Project1.Class1 which is running under debugger
I'm getting errors:
- from caller in another VB6 instance - "430 - Class doesn't support
Automation or does not support expected interface"
- from VC++ caller - CoCreateInstance on Project1.Class1 succeeds, but
further QueryInterface for _Class1 returns 0x80004002 (E_NO_INTERFACE),
, though when Project1.Class1 is *not* under VB6 debugger everything passes
OK.
If I further add Class_Initialize and Class_Terminate handlers to
Project1.Class1, I can see that in VB6 debugging failure cases the class is
instantiated, but gets terminated imediately.
Can someone give me ideas how to fix that?
Regards,
Andrei Suvorov.
Ralph
"Andrei Suvorov" <andrei...@gmail.com> wrote in message
news:ukcnD87Z...@TK2MSFTNGP05.phx.gbl...
Not sure what "Project1.Class1 is *not* under VB6 debugger" means - a
compiled component?
I'm probably missing something, but it sounds like you are not using binary
compatibility and/or in some way not referencing what you think you are.
[Also you might check the 'Instancing' property.]
-ralph
Andrei Suvorov
You're absolutely right!
Setting up the binary compatibility in Project1 correctly (there was Project
compatibility before) was helpful and eliminated all problems.
Thank you very much!
Regards,
Andrei Suvorov.
P.S. Yes, by "Project1.Class1 is *not* under VB6 debugger" I meant compiled
component.
"Ralph" <nt_cons...@yahoo.com> wrote in message
news:uic3uK8Z...@TK2MSFTNGP06.phx.gbl...
MikeD
Glad to hear you managed to solve the problem.
For future reference, you CAN cross-post to more than 2 newsgroups. You
posted once to vb.controls and vb.general.discussion and then posted again
(2 minutes later, so it's not like you waited a day or longer with no
replies before re-posting) to vb.bugs and vb.com. You should have included
all 4 in a single post. And then you wouldn't have had to post a follow-up
saying Ralph's advice solved it to the 2nd set of newsgroups.
Just an FYI.
--
Mike