There's a new KB article addressing this very issue - Q214560 . It gives a more permanent solution to the problem than the one below. - Andrew Coates
You've just installed the latest and greatest version of the MSDN library and, all of a sudden, the F1 key has stopped working in the VFP development environment.
There are a couple of things that need to be done.
- Check that the VFP registry entry for the help file location is pointing to the right file
- Run the MSDN Collection Settings application to make sure MSDN is using the right collection
Check the VFP Help File Location Registry Entry
- In VFP, choose Options from the Tools menu. Click the File Locations tab.
- Double-click the Help File list item and make sure that the entry is pointing to the MSDN000.COL file in the correct branch of the MSDN tree. In my case, the location of the file is g:\msdn\2000jan\1033\msdn000.col
- Make sure the Use Help File check box is checked in this dialog as well.
- Save the changes by clicking OK in the locate file dialog and then click Set As Default to commit the changes to the registry
Run the MSDN Collection Settings Application
Your help file should now work
- Choose Start|Programs|Microsoft Developer Network|MSDN Library - Collection Settings. Note that if you are running Win98 or Win 2 K, you may need to get the menu to display all the entries, rather than just the recently used ones.
- Choose the appropriate language and collection - you need to at least drop down one of the combos to enable the apply button
- Click the apply button
FWIW, I point help inside VFP just to foxhelp.chm if I want the full MSDN I use the shortcut on the Visual Studio Start menu.
Contributors Andrew Coates
( Topic last updated: 2000.02.27 08:16:07 PM )