Hi Aleksey,

>I wasn't talking in general, I was talking about capabilities of SQL engine in VFP. In general, it is possible to optimize conditions like that and I am sure there are SQL engines that do.

Is there a chance to document strategies most fitting for *particular* situations/circumstances with VFP's implementation of SQL engine ? While I believe that by now I have a partially subconcious knowledge of when some of the constructs working better, you are definitely in a better position to check on the behaviour in specific situations since I KNOW from my experience that my assumptions are not always correct<g>.

While I often save those tidbits found here ore elsewhere I still have to search them or various blogs. Enhancing the chapters in vfp's help might be an option but I fear the process involved in changing might be detrimental and stifling the amount added. If I could decide on the matter, I'ld prefer more material/topics with possibly sub-optimal wording to fewer points in the official documentation which have to be proof-read a couple of times before each change.

In my opinion it would be best to have a corner where such "tips from the experts" are bundled - a more WIKI like approach where

a paragraph from such a thread like this
or the thread where you showed a way to use UDF's for rushmore
as well as some findings from your work
or tips others send in

can easily be added to the material already gathered.

Such wiki pages *should* be monitored by someone having the knowledge and technical possibility to separate fact from fiction - meaning false assumptions based on witnessing the behaviour of VFP with a specific dataset on specific hardware - which IMHO necessitates "official" MS involvement/checking to be correct and sucessful.

my 0.20 EUR (did think quite a bit about it but found no better proposal <g>)

thomas