>>>I'm sure that is not a VFPT choice, but a C++ "if" bad condition into the VFP engine!
>>>With the time it become a VFP design.
>>>
>>>I do not want to open a discussion,
>>>but when:
>>>- A design is different from almost all other designs
>>>- A design creates more disadvantages than advantages
>>>for me is a bug.
>>
>>You can believe in whatever you want but neither constitute a bug.
>
>Inconsistency, maybe, as other things were done to make internal SQL behave in a TSQL-like manner. So this would be wrong if you have TSQL glasses on - or TSQL was wrong if you have VFP glasses on.
>
>If this was the only difference between the two, I might have put that somewhere on the list of warnings, gotchas and other things that make you waste time and slap forehead more often than normal. But given that there are so many other differences (like the awkward way TSQL deals with date arithmetic, the mandatory =1 when checking whether a logical field is true, but then being unable to calculate with those bits unless casted, and then the huge difference in syntax when it comes to quotation marks, apostrophes and square brackets...), this one doesn't worry me much.

If all other database engines produce the same result and only VFP is different, then it's either bug or a bad design, IMHO.