Hi Dominic,
You have reason.
---
Access language support First(fieldName) grouping clause.
SQL Server not support this extremely useful function ( need useless subquery -> two scan/seek on table).
SQL-92 not support it, but it has been made from the humans, the humans are not perfect, therefore ...
---
This operation is determinist, not ambiguous.
It is ambiguous if I am ambiguos, that I am idiot, and not known what I make.
I leave you the conclusions, to me remains a new problem.
----
SET ENGINEBEHAVIOR 70 it is a mortgage on the future, it is too much generic.
VFP 9.0 have SET ENGINEBEHAVIOR 90|80|70
VFP 10.0 have SET ENGINEBEHAVIOR 100|90|80|70
Fabio
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only