I decided to create a new thread because the earlier one is so long that it would be hard for somebody to figure out what is going on.
To begin with I would like to thank MAX187Boucher for the great support. He stayed with me during several attempts and ultimately figured out how to solve the problem. He is rated a "Frenzied Member" and I can see why :)
I am just documenting what I had to do to get VB working again so other people can benefit from it.
Problem:
VB 6.0 program could not load components any more into projects. ( Windows 7, Internet Explorer 10)
Solution:
First step was to unregister the ocx files in both the system32 and the sysWOW64 folder.
To unregister run first cmd.exe in sysWOW64 folder in administrative mode.
In the command window change the directory to c:\windows\sysWOW64. (cd.. and then cd\sysWOW64)
Unregister the ocx file in the sysWOW64 folder (regsvr32.exe /u c:windows\sysWOW64\file.ocx)
Unregister the ocx file in the system32 folder (regsvr32.exe /u c:windows\system32\file.ocx)
Next unregister the ocx file with the cmd.exe in the system32 folder.
Run in administrative mode.
In the command window change directory to system32 folder (cd.. and cd \system32)
Unregister the ocx file in sysWOW64 folder (regsvr32.exe /u c:windows\sysWOW64\file.ocx)
Unregister the ocx file in the system32 folder (regsvr32.exe /u c:windows\system32\file.ocx)
Finally register the ocx file in the sysWOW64 folder.
Run cmd.exe in the sysWOW64 folder in administrative mode.
Change directory to c:\windows\sysWOW64 as follows:
cd ..
cd sysWOW64
then register the file: regsvr32.exe c:\windows\sysWOW\file.ocx.
After all of this the component loaded in Visual Basic. Problem solved.
I don't understand why one has to unregister four times but then the registration process is somewhat of an unknown to me.
What caused the problem?
I suspect that the installation (without my knowledge, it came along with a Flash update) and then the uninstalling of the Chrome Browser on my computer is at the root of the problem.
More anecdotic evidence: I decide to install VB on my wife's laptop just in case I would not be able to fix my computer. VB worked all right. Because the laptop was rather slow I decided to delete some files. One of them was the Chrome toolbar that sat there without her knowledge. I did delete the toolbar and low and behold the VB program on the laptop had the same problem as the one on my computer. It could not load components anymore.
I wish somebody could take a hard look at this. If it can be proven that the Chrome web browser and toolbar can screw up your computer . They should be kept responsible for it.
To begin with I would like to thank MAX187Boucher for the great support. He stayed with me during several attempts and ultimately figured out how to solve the problem. He is rated a "Frenzied Member" and I can see why :)
I am just documenting what I had to do to get VB working again so other people can benefit from it.
Problem:
VB 6.0 program could not load components any more into projects. ( Windows 7, Internet Explorer 10)
Solution:
First step was to unregister the ocx files in both the system32 and the sysWOW64 folder.
To unregister run first cmd.exe in sysWOW64 folder in administrative mode.
In the command window change the directory to c:\windows\sysWOW64. (cd.. and then cd\sysWOW64)
Unregister the ocx file in the sysWOW64 folder (regsvr32.exe /u c:windows\sysWOW64\file.ocx)
Unregister the ocx file in the system32 folder (regsvr32.exe /u c:windows\system32\file.ocx)
Next unregister the ocx file with the cmd.exe in the system32 folder.
Run in administrative mode.
In the command window change directory to system32 folder (cd.. and cd \system32)
Unregister the ocx file in sysWOW64 folder (regsvr32.exe /u c:windows\sysWOW64\file.ocx)
Unregister the ocx file in the system32 folder (regsvr32.exe /u c:windows\system32\file.ocx)
Finally register the ocx file in the sysWOW64 folder.
Run cmd.exe in the sysWOW64 folder in administrative mode.
Change directory to c:\windows\sysWOW64 as follows:
cd ..
cd sysWOW64
then register the file: regsvr32.exe c:\windows\sysWOW\file.ocx.
After all of this the component loaded in Visual Basic. Problem solved.
I don't understand why one has to unregister four times but then the registration process is somewhat of an unknown to me.
What caused the problem?
I suspect that the installation (without my knowledge, it came along with a Flash update) and then the uninstalling of the Chrome Browser on my computer is at the root of the problem.
More anecdotic evidence: I decide to install VB on my wife's laptop just in case I would not be able to fix my computer. VB worked all right. Because the laptop was rather slow I decided to delete some files. One of them was the Chrome toolbar that sat there without her knowledge. I did delete the toolbar and low and behold the VB program on the laptop had the same problem as the one on my computer. It could not load components anymore.
I wish somebody could take a hard look at this. If it can be proven that the Chrome web browser and toolbar can screw up your computer . They should be kept responsible for it.