Recovering VB6
I have an app written by a previously and it crashed and took-out/closed the VB6 IDE unexpectedly. When I try to open the IDE, it hangs and won't paint the IDE form. Its all white and never recovers. Tried un-installing and re-installed VB6, but I still get the same behavior.
On the reinstall obviously I did not get all the configs and/or libraries replaced.
Can anyone tell me how or name all the config and library files that need to be removed so that VB6 will work correctly on the re-install ?
Thanks
On the reinstall obviously I did not get all the configs and/or libraries replaced.
Can anyone tell me how or name all the config and library files that need to be removed so that VB6 will work correctly on the re-install ?
Thanks
Martin Liss
Does this happen with a new project?
ASKER
Its when the IDE first starts to load. I never get to the prompt for: new, recent, existing
That's very strange. Just to make sure I understand; you're trying to open VB6 and not an existing project, correct?
Also I note that you included .NET as a topic area for this question. Why is that?
Also I note that you included .NET as a topic area for this question. Why is that?
ASKER
.Net: Just thought I might catch some programmer that knew the answer. A nag screen shows up if you don't choose 3 topics.
I hate to be a nag but…
That's very strange. Just to make sure I understand; you're trying to open VB6 and not an existing project, correct?
ASKER
yes, before I get to the prompt for a new project, it just hangs on start. Nothing in the IDE is available.
Today: I uninstalled VB again, renamed "C:\Program Files\Visual Studio\VB.." folders that the previous install left behind.
Re-installed: Didn't let it use the old stuff even though it found it. Now after about 60s I get an error that the version of the "MsComCtl.ocx" may not be correct. I can get by the error and a few others and finally I get IDE and my app runs.
I need to know what registry keys have been left behind so that I can clear them out.
And then get a really clean install.
Today: I uninstalled VB again, renamed "C:\Program Files\Visual Studio\VB.." folders that the previous install left behind.
Re-installed: Didn't let it use the old stuff even though it found it. Now after about 60s I get an error that the version of the "MsComCtl.ocx" may not be correct. I can get by the error and a few others and finally I get IDE and my app runs.
I need to know what registry keys have been left behind so that I can clear them out.
And then get a really clean install.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
No, just the one version of VB.
I am starting to think that some of the vb lib(s) are corrupt.
I am starting to think that some of the vb lib(s) are corrupt.
ASKER
I would think that the reinstall would delete everything before it installs but maybe not.
How about renaming mscomctl.ocx then doing the uninstall and reinstall?
How about renaming mscomctl.ocx then doing the uninstall and reinstall?
ASKER
I already replaced it. I am thinking that its some reg keys left behind that I need to rename or delete ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I was satisfied with VB starting with a couple of errors. It was like the IDE was having issues with the MScomctl to load and config the IDE. After the errors past, my app appeared to run fine.
Multiple vesions of VB: I was using VB6, but the screen-scrape software that I had loaded was using a runtime version of VBA. And yes probably had conflicting versions of the controls.
The vendor was having a 2nd error that I was not able to recover from. So before I destroyed the maching digging through the reg, I got a fresh image of XP on a new PC from our techs and copied all software and configs.
Looks like it’s working.
Thanks
Multiple vesions of VB: I was using VB6, but the screen-scrape software that I had loaded was using a runtime version of VBA. And yes probably had conflicting versions of the controls.
The vendor was having a 2nd error that I was not able to recover from. So before I destroyed the maching digging through the reg, I got a fresh image of XP on a new PC from our techs and copied all software and configs.
Looks like it’s working.
Thanks
You're welcome and I'm glad I was able to help.
My profile contains links to some articles I've written that may interest you.
Marty - MVP 2009 to 2012
My profile contains links to some articles I've written that may interest you.
Marty - MVP 2009 to 2012