fwiw, I agree with you and Claude. Whats the big deal with putting it in the docs? I read here in some post that KenL was quoted in an article as saying there were roughly 100,000 VFP developers in the world. If they all upgrade only every other year and spend only a few hundred dollars for the upgrade (never mind MSDN subs) thats several million per annum in sales. Surely that covers the costs of some extra docs. Or am I stepping on DenisC's territory here :)



>Hi Claude,
>
>>Let's not dance around this subject. Key technologies should be in the docs, period. No product survives relying on digging up and finding key technologies described in obscure whitepapers on 3rd party web sites that most developers don't even know about. It has to be from the source, namely the product itself.
>
>And this I see as a core point of your argument. Other discussions here have speculated that the percentage of VFP developers that actually use Web resources is likely small. 10%? 20%? How will the others become aware of these technologies other than through the documentation? The Task Pane? I just fired up VFP8, started the Task Pane, and selected Community. After 30 seconds, "An error occured. Click here for details."
>
>FoxCentral News
>Error executing method on Web Service: http://www.foxcentral.net/foxcentral.wsdl - GetItems(DATE() - 5, 0, 0, "ALL")
>
>Good grief. Are these those "valuable resources" we hear about all the time?
>
>Put it in the docs. End of rant.