Fabio

I understand your frustration.

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

That's true but documentation is often out of synch with code and there are always mistakes and omissions. Regardless, Aleksey is right. One does not upgrade without testing and one certainly does not send product to the users without testing. When I gave up views in favor of SPT it was because of realizing how the GROUP BY was returning wrong data. I tried to fix by breaking views into pieces - subviews and a main view. It never occurred to me to let the subviews requery automatically, as I believe I am responsible for ensuring subviews have the right data before requerying the main view. It is logical (to me) to expect they would NOT requery when the main view requeried unless the subviews were not already used. How would one control the order of requeries if one subview depended on another? I control all queries with SPT and things are stable and reliable.

>
>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
>

Nothing Aleksey has said lets me conclude he is such a developer. That is unfair.

>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.

So that he might be reprimanded or fired and the VFP community lose another VFP supporter within Microsoft?