I realize that the state of the VFP8 beta documentation is also beta.

Nevertheless I believe that this is important and needs to be highlighted to help towards assuring that the final release incorporates resolution of this deficiency.

The "Reference" section for the CursorAdapter Class has a lengthy write-up (20+ time the number of words describing the actual class itself) titled: "Interaction with the TABLEUPDATE( ) Function". This truly is critical information!

However, the description of the TABLEUPDATE() function itself makes ABSOLUTELY NO MENTION of the CursorAdapter class and of the specific considerations inherent in TABLEUPDATE's use with that class!!! Not even in the "See also" list.

Not that inclusion in the "See also" list would be enough - it wouldn't be!
It is imperative that all of the factors relevant to the interaction of TABLEUPDATE() and the CursorAdapter class be included in the description of the TABLEUPDATE() function!!!!!
The reasoning for this is simple and obvious - when a developer is experiencing difficulty with the results obtained for a TABLEUPDATE() function call when using a CursorAdapter, it is the TABLEUPDATE() function reference documentation that will be checked and not the CursorAdapter description.

The documentation seems to be written under the objective of never repeating any information. *IF* that is the case then that objective is not serving the developers! It really doesn't matter to the developer - or help him/her either - to know that "it's in there somewhere" or "there's very little omitted from the VFP documentation". What is helpful to the developer is that relevant information is in the proper place. For most of us, in our day-to-day use, that means under the relevant topic in the (command) reference.

Developers don't really mind if information is repeated in various text entries. That is far more preferable to us than to be subject to some rule regarding non-repetition (which invariably results in critical information being mis-placed).

I hope that this important issue will be addressed in time for release of the VFP8 product. It would be most helpful if all similar occurances could also be fixed.

Thanks