Re: Strange problem when using a class module in VBScript
- From: "Someone" <nobody@xxxxxxx>
- Date: Tue, 13 Sep 2005 21:09:32 -0400
> Looking through the dll project I noticed that the Instance property for
> the class module is missing, could that be the problem?
Change back the project type to ActiveX DLL/EXE/OCX and you will see that
property. When it reappears, VB sets to Private, meaning that it will not be
visible to the outside world. Change it to Multiuse or any other option.
Standard answer follows:
It sounds like that you are not using binary compatibility. You may have to
remove the traces of your controls/DLL's from the registry. See this article
in how to do it:
http://support.microsoft.com/default.aspx?scid=kb;en-us;180525
Even if you don't have multiple copies of the same control name in the
registry, the steps above still apply. They are equivalent to "regsvr32 /u
control.ocx", or "regsvr32 /u <vbide>".
When you run an ActiveX project in the IDE, VB6 creates registry entries and
points them to the following file:
C:\Program Files\Microsoft Visual Studio\VB98\VB6DEBUG.DLL
When you stop the project, the IDE would auto delete these entries, unless
it crashes.
"Ragnar Midtskogen" <ragnar_ng@xxxxxxxxxxxxxx> wrote in message
news:e9Zz9mLuFHA.4080@xxxxxxxxxxxxxxxxxxxxxxx
> Hello,
>
> I have an ActiveX dll created in VB6, which contains a class module.
> I recently updated the class module in it and now when I try to run the
> code from a VBScript I get an error 429 'ActiveX can't create object' for
> the line with the CreateObject call..
>
> The dll is also called from Web pages so I would have to stop IIS to
> replace the dll with the new version, so for debugging purposes I included
> the class module in a VB Standard EXE application. When I compiled the
> debug app I got some kind of message about the class module but I clicked
> OK too fast so I did not read the message. Everything worked fine so I did
> not hink more about it.
> When through debugging I copied the class module back into my dll, and now
> I get this error.
> Looking through the dll project I noticed that the Instance property for
> the class module is missing, could that be the problem?
>
> I am not sure how to restore the property so I am going to try bringing
> the updated class module into the original version of the project by copy
> and paste. Is there a simpler way?
>
> Any help would be appreciated.
>
> Ragnar
>
>
>
.
- References:
- Strange problem when using a class module in VBScript
- From: Ragnar Midtskogen
- Strange problem when using a class module in VBScript
- Prev by Date: Re: Source of EXE Size OT
- Next by Date: Re: Check if a form is loaded
- Previous by thread: Re: Strange problem when using a class module in VBScript
- Next by thread: Re: Strange problem when using a class module in VBScript
- Index(es):
Relevant Pages
|