Re: Multiple references to same component in reference dialog
- From: "Ralph" <nt_consulting64@xxxxxxxxx>
- Date: Wed, 31 Jan 2007 06:21:03 -0600
"Ken Halter" <Ken_Halter@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:OwTVA1KRHHA.3812@xxxxxxxxxxxxxxxxxxxxxxx
"Steve" <sredmyer@xxxxxxxxxx> wrote in messagedoc.
news:1170185825.245451.196630@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
My expperience is that if I compile a project with or without binary
compatability it will be registered and an entry will be created in
the References dialog box. If I then delete the compiled file without
Since ActiveX relies almost entirely on the registry, that makes perfect
sense.
unregistering it, the entry will still be in the registry and in the
References dialog. This entry will be an orphaned entry in that it no
longer points to a valid file. Furthermore, since the file no longer
Again... perfect sense.
exists, you can not unregister it...hence there will be no way of
getting rid of the entry.
"No way" isn't correct <g> There are a lot of ways. RegClean uses one of
them. You can also get rid of them "manually" by reading the following
fine.
INFO: Registry Entries Made by an ActiveX Component
http://support.microsoft.com/kb/183771/en-us
You can also use this excellent utility to get rid of them...
COM Explorer - Explore, Manage and Repair ActiveX Controls, DLL & EXE
Servers
http://www.4developers.com/com/index.htm
As I said in my original post I used to use RegClean to clean these
issues up but it is not working now. In an attempt to find out why it
is not working I found an article from M$ that states that the utility
does not work on XP.
Well, post a link to that article because it's surely wrong. It works
It's not "supported" on XP... that I can believe. You may have specificof
software that complains after using it... I've heard of that. I have none
that software though, so I use it when ever I get the urge <g>and
Since deleting a file without unregistering first seems to be your main
issue, the doctor says "don't do that any more". You should have Regsvr32
associated with activex components so you can right-click any DLL or OCX
register/unregister them at any time.
To add to the pile, another Gotcha when dealing with registered components
comes from deleting components using the Shell (Explorer). A deletion
actually just moves the component from the current folder to the Recycle
folder. In this case the O/S will often quite kindly update the Registry
entry to point to its new location.
Thus you many think it is gone - but subsquent runs of your application is
not using a 'new' dll, but one that is sitting in the Recycle folder. This
can be quite bewildering the first time you run across it.
-ralph
.
- References:
- Multiple references to same component in reference dialog
- From: Steve
- Re: Multiple references to same component in reference dialog
- From: Ken Halter
- Re: Multiple references to same component in reference dialog
- From: Steve
- Re: Multiple references to same component in reference dialog
- From: Ken Halter
- Multiple references to same component in reference dialog
- Prev by Date: Re: how can make link with vb form and access table to save data in access table
- Next by Date: Re: Dependencies in vb6 project
- Previous by thread: Re: Multiple references to same component in reference dialog
- Next by thread: VB6 project loses reference to EXE component
- Index(es):
Relevant Pages
|