>On Message #1102243 you writes
>If it finds cursors for those views it'll use data from them, no REQUERY is done for those cursors.
>Which cursor ?
>
>On Message #1102585 you put an example without an explanation.
>
>Only now we know what cursor VFP use.
>

Actually, if we go back to my first post on this thread, I referred to message #985777. In that message I wrote: "It appears that, if there are opened cursors for the view, SQL SELECT selects data from the last opened cursor and doesn't reexecute the query for the view." So, the answer was there for a long time. The example without explanation was posted to draw attention to this behavior.


>But, this is not documented, therefore VFP could change way of working
>( to use another work area )
>
>Do you explain me which REQUERY() of view1 a developer can do?
>- All ?
>- Close all and USE a new
>
>It is not possible to use a system of this type.
>

I agree, it is extremely difficult to use system of this type. You may not believe me, but I myself was really disappointed to discover that it works this way. If someone asked my advise, I would recommend to find different solution and not use nested views at all, it is very difficult to keep track of all opened work areas and how they affect nested views. It is very easy to get in trouble especially because often it looks like the app is working, whereas in fact it isn't.

What you and others should try to understand is that we simply can't go and fix all strange/"bad"/questionable behaviors in the product. Almost every time we fix a bug in a feature that existed for quite some time, the fix breaks someone's application. This thread is a good example. You won't believe how many people knowingly/unknowingly employ strange/"bad"/questionable behaviors in their code. So, we get our part of frustration too.