>For the record, the primary reason for this change (defaulting to 8.0 behavior) was that certain query constructs that are permissible in VFP 7.0 and before may return incorrect or indeterminate results. In our view, it was very important that we did not default to 7.0 behavior, which would facilitate leaving "as is" applications that contained SQL statements that potentially return incorrect data.
>
>For those who are certain that their use of these SQL constructs is OK, it is easy enough to switch the behavior to 7.0 via config.fpw. Otherwise, we recommend adopting the new 8.0 SQL behaviors.

Yes, no problem, once I got clear explanations, it made sense to upscale it. I took about 48 hours to adjust about 40 very long SQLs and now the entire application is now ANSI SQL compliant. So, from now on, we rely on that standart for upcoming development.