Re: Early Binding Fails
- From: "Someone" <nobody@xxxxxxx>
- Date: Thu, 6 Oct 2005 00:09:16 -0400
You probably have problems with your ActiveX registry entries. Please delete
the keys mentioned in the following article:
PRB: DCOMCNFG Reports Multiple Copies of DCOM Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;180525
Even if you don't have multiple copies of the same ActiveX in the registry,
the steps above still apply. They are equivalent to "regsvr32 /u
control.ocx", or "regsvr32 /u <vbide>".
A registry cleaner utility might do this for you if you delete your ActiveX
file, but I am not sure.
Note that the article refers to using DCOMCNFG.EXE in Windows 9x. You can
see the same list of objects by going to Project|References. In newer
versions of Windows, you can see the list of objects in Control
Panel|Administrative Tools|Component Services|Computers|My Computer|DCOM
Config. Typing "DCOMCNFG.EXE" will open "Component Services". You might see
some warnings that some AppID's are not recorded, choose No.
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. When you compile your ActiveX project, VB6 auto create the
registry entries for them and point them to your compiled file. VB6 never
delete these entries, otherwise you can't use your component.
Also, in NT, you have to be a member of Power Users or Administrators in
order to develop and test ActiveX projects. That's because only Power Users
and Administrators can write to HKEY_LOCAL_MACHINE.
INFO: Registry Entries Made by an ActiveX Component
http://support.microsoft.com/default.aspx?scid=kb;en-us;183771
"Jiju Joseph" <JijuJoseph@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2C3A609D-5C3C-4E0C-B106-B6792EE05278@xxxxxxxxxxxxxxxx
> Hi Douglas,
>
> The issue, If I use Early Binding, the COM throws an Error "Error in
> loading DLL", And I did cross verify the DLL's on the working box &
> problem
> box, same version, same size, same creation date.
>
> I even copied the Dll from the working box, still the same issue.
>
> Regards
> Jiju Joseph
>
>
> "Douglas Marquardt" wrote:
>
>> Hi Jiju:
>>
>> You need to be more specific -- exactly what is the error?
>>
>> In any case, because you can create the object but early
>> binding it fails, I suspect that the dll on the problem machine
>> is either not the latest version, or not physically the same one as
>> on the machine the works?
>>
>> Doug.
>>
>>
>> "Jiju Joseph" <JijuJoseph@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:39C6381C-8F5A-4E9A-8E03-FB510239F96F@xxxxxxxxxxxxxxxx
>> > Hi,
>> >
>> > I have a Piece of code as following,
>> > Dim oF As prjFunction.clsFun
>> > Set oF = CreateObject("prjFunction.clsFun")
>> >
>> > Which bombs when running on one machine, If I Declare oF as
>> > Object,
>> > it works fine, (Don't tell me its because of wrong Reference, I am 100%
>> > sure
>> > that the Reference are correct - Because the DLL's deployed on another
>> > machine is working fine.)
>> >
>> > Can anyone tell me whether this is dependent on some windows
>> > files??
>> > What is the reason that the machine is not supporting Early Binding.
>> >
>> > Thanks in Advance
>> > Jiju Joseph
>>
>>
>>
.
- References:
- Re: Early Binding Fails
- From: Douglas Marquardt
- Re: Early Binding Fails
- Prev by Date: Re: Early Binding Fails
- Next by Date: Registry Key
- Previous by thread: Re: Early Binding Fails
- Next by thread: Re: Early Binding Fails
- Index(es):
Relevant Pages
|
