David-

>The Problem in 6.0 was that after one installed the product, there was no menu help available (help is greyed out on menu).

Yeah, I recall that there was a deployment bug that resulted in some people not getting the MSDN library. I think it was in International shipments, IIRC. As with most bugs, it was nice that as usual community support systems such as the UT and other newsgroups were there for us.

>Yes, I know that the MSDN could also be installed, with loads of data not relevant to VFP. (I think at the time, it was the aim of Microsoft was to herd all of the VFP users towards Visual Studio’s other products)

There's a difference between trying to answer a technical, practical question with technical and practical suggestions and a discussion of the politics of the situation. FWIW, it made sense to me that we would have had the MSDN library as a default since we were supposed a part of the VS. I was merely grateful that we have the choice to use whatever CHM we want for our help...including, for example, the Hackers Guide CHM which some people do.

>Now that VFP is again freed from Visual Studio, I can’t see why there is not an option/s, during the installation, which asks you if you want to install the VFP help files (the default should be set to Yes), and if so, it does it for you automatically. If you wanted all of MSDN help files, that could be another option.

As I said in my post, it was simply the default help for the post-VS beta, so I don't know that it's an issue at all. Have you had trouble with the Beta 2 help?