>>but does it seem yourself that one can use a thing that works in this way,
>>without a documentation ?
>
>Why not? I never said that one should never use undocumented features, use them on your own risk and always check that they work the same way once you switch to a different version of a tool. There were several occasions when I used undocumented features myself and I too experienced frustration in cases when their behavior was changed. However, I considered it my responsibility to keep track of my assumptions and make sure to check if they are still valid. I am pretty sure that, at the beginning of this thread, neither you, nor James understood how REQUERY for views, referencing other views, works and where the data are actually coming from.

If the documentation writes as REQUERY works
all of us would probably know whether to use it,
without losing days to discover it.

I am pretty sure that many developers don't document
their job for two reasons:
- to make visible to whom manages the project the mediocre level of their job
- to feel themselves superior because they know something that others don't know

Your vision of the software is absolutely not professional,
and the way of proposing you to the clients of the Microsoft it is arrogant
and very often ill-mannered.

I hope only that someone in the MS draws the conclusions.

>
>>The result of a requery depends on the cursor with bigger workarea than it represents
>>a nested view:
>>
>
>This assumption is not accurate, work area numbers are not involved.

Look my code, it is not the work area numbers,
but the work area order involved.