I installed the MSDN January 2002 edition and now when I open VB6 or Visual Studio 6.0 and try to access help I get the message "The MSDN collection does not exist. Please reinstall MSDN." How can I rectify this so that my MS apps point the the new MSDN?
I had the same problem. What you have to do is when you click F1, it says, unable to display Help, Click the Help button on that form, it will take you through how to re-link your MSDN. Your other option is to go here:
This link has all the details of how to actually reset it. Though Even though i fixed this I noticed that some days it still looses it's reference and I have to shut down VS, and restart it before I remembers where it hid the link. Craig, mailto:sander@cogeco.ca
"Procrastination is the art of keeping up with yesterday."
This is different. I am actually getting a message box that says "The MSDN collection does not exist. Please reinstall MSDN" with an OK button. That is my only option. I tried going to the link provided and doing what it says, but that did not work.
The new MSDN installs IE 6. I made this mistake too and just got rid of the damned thing--it is so NET-centric that it's useless for VB6 reference (in my disgruntled opinion). The October MSDN was the last "normal" one.
Surely the idiots (MS) are not mixing VB.NOT (sorry) with VBClassic (VB6 and earlier) ?
I won't be going to VB.NET until I have a screaming need.
But sure as heck I would not want the 2 Help files mixed, regardless of which VB (VB.NET or VBClassic) I was using.
I have both installed. You need the Oct 2001 for VB6 and the Jan 2002 for VB.Net. IE 6 has been no problem. At work I have VB.Net but have not yet installed Jan 2002. There is still internal help with VB.Net without MSDN but I like to keep a seprate MSDN open for hopping around. You will need both.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.