Fabio,
>David, I don't directly use this syntax,
>but the syntax is correct and therefore usable;
>if an usable syntax returns results doesn't conform,
>then it contains a bug, always.
That particular syntax can cause differing results, so if you choose to use it, then you are subject to the the whims of the SQL engine.
>This is the motive for which VFP is full of bugs,
>the most greater part of the developers look for a road
>don't have problems instead of stressing the Team
>to correct the errors
Most of us spend a lot more time actually using the language to get real work done rather than finding obtuse and esoteric things to report as bugs.
>An example:
>a complex program that builds the queries to runtime could assemble
>a union query and to perform it as macro
>putting together pieces of select that has different names.
Macro substitution has nothing at all to do with this topic. You can just as easily build the strings that represent SELECT
2 ... SELECT
N of the union without the misleading column aliasing.
