Hi Andy

>Agreed, it's a problem. But that rationale becomes a damned good excuse for doing too little too. I think that's where the real problem lies.

I have to disagree. The problem with any documentation for a development tool, as opposed to an application, is that you simply cannot cover all of the things for which the tool might be used. Even if you were to try, there would still be holes because you never can tell what someone will want to try and do.

>AlekseyT has been fantastic is clearing up many things, but if all his efforts remain only here and do not make it to documentation enhancements his relies will really have very minor long-term value.

The best solution is, of course to build your own library of additional information (which is what many people do) by saving off messages that are of interest and adding your own indexes.

By and large the documentation for VFP is of a much higher standard - especially given the complexity of the product - than many other tools (try using the SQL Server docs some time, or Delphi).

The VFP Documentation team do a great job, but they simply cannot cover all the angles and to attribute any perceived shortcomings to laziness on their part seems a little ungracious to say the least.