>>I guess my point is that since Jan. 2002 (or before that I think) the MSDN Library has been in the newer format and no longer uses msdn*.col or .chm.
>
>The last MSDN Library that could be used through VFP as a CHM was the October, 2001 library.
>
>>So I was curious if we could use the new help files without creating a custom menu link.
>
>I opened the File Locations dialog and went to the Help File entry. I chose the Collection option and put "ms-help://MS.MSDNQTR.2002JUL.1033" (without quotes) in the Help collection URL reference. (I install the MSDN Library in the default location and I haven't installed the October version which is sitting here.) When I chose Help from the Help menu I got the latest MSDN Library. When I highlighted a word and used F1 then sometimes I got the MSDN Help and sometimes the VFP Help CHM. The The Help menu Help seems to revert to the VFP CHM after a few uses.
>
>The above works for both VFP7 and VFP8 Beta. I'm still not sure how the Help filter works in this context. If I set the filter and then closed Help, when I reopened it the filter was still on. If I closed my session of VFP and then went back in to VFP and Help the filter was gone.

You can set the filter in the command line with the "/filter" switch.

dexplore /helpcol ms-help://MS.MSDNQTR.2002OCT.1033 /filter "Visual Foxpro 7.0"

What I haven't yet found a way to do is to have the msdn open directly at the VFP start page (or any other start page I might want).

I've been trying to set shortcuts to take me directly to C# help, and VB help etc, and while I can set the filter, the msdn still insists on opening at the default start page.

Alan