Nancy,

SNIP
>
>That's Sergey's comment. My impression of the 7 docs is different. I think it's improved over 6.0. Always room for more. OTOH, I'm not sure how they get as close as they do when the development team is still adding features a month (?) before RTM. But, since I know you'll have a comment on that, please remember I said always room for improvement.
>
>Hm. Why doesn't the community push for interim releases of the docs? Maybe we outta. Is it feasible?

First, I no longer have the VFP6 documentation on my system. I could re-install but feel no overwhelming need to.

I think that simply pushing for interim releases of the docs will not really accomplish much, unless it is accompanied by some easy way to communicate observed errors/omissions/confusions.

What is clearly needed, in my humble opinion, is for someone who is VFP knowledgeable (modern VFP, not FP or VFP3) to proofread and correct the documentation. I am also assuming that it is understood that anyone acting as a proofreader would be attentive to the smallest detail. [that person might also be able to apply the changes outlined in the UT VFP8 wish document < s >] Interim release publication at points during this process would surely be helpful.

A few things, just off the top of my head, that I have found in perusing the new docs so far:
- Repeated in 2 different places that no characters may be coded after a semi-colon of a continuation;
- The naming of a parameter/clause in the body of a discussion that is NOT named in the syntax diagram.
- An example with an extraneous APPEND BLANK, thoroughly confusing the reader.
- The entirely confusing discourse of the FUNCTION Command along with its important omission.
I know that I have found at least 10 more. Too bad that the display mechanism doesn't allow for annotation, 'cuase then I could make notes and they would be easier to (re)find.