>Jim,
>
>So should one surmise that CURSORSETPROP() operates on something totally independent of any tables/views initial property settings as they may be set by DE processing or (manually) elsewhere?
>
>Could I not issue CURSORSETPROP() to set the buffering and expect the MULTILOCKS to already be set properly, assuming that I issued CURSORSETPROP() *after* DE.Init? I know I can try for myself, but my point is to show that the docs may, indeed, be more deficient than you accept.
>
>Jim N

Jim,

You and I disagree on the docs. I believe that they are fine, you think they are abysmal. Let's agree to disagree on this issue.

It is unrealistic to think that every help entry will cover the entire possible scenarios of event sequences and give specific information for each possible sequence. The help states that you MUST set multilocks on in order to use CursorSetProp to set buffering. That is all ther eis to say on the matter. Through lack of comment one cna infer that set multilocks is not necessary when using a DE. A simple quick test proves this.

Since any document of the size of VFP's docs will have unaviodable errors in it, one should test things before depending on them anyway.

The docs are not a training program, they are reference material and as such they should be brief and to the point. I don't want to read a forty page entry for Valid, I want brief information and if I need to know more I will investigate what I need to know.

It appears that making the help system what you are asking for would render it useless to me. It would then be information overflow and confusing to read and understand. Each entry would require that every possible event sequence be discussed even if a sequence did not alter the behavior, because otherwise the docs would be "incomplete". The entry being discussed here is a perfect example of this. You say you want the docs to tell you that the stated requirement for cursorsetprop is not needed for a DE.

Jim, if you want input to MS about VFP, apply for the betas. There you get alot of input. They even have a docs newsgroup for doc enhancement and correction issues. However, it does mean you have to provide some effort into testing the product for them.