Hi Walter

Certainly you know what I mean. With EngineBehavior set to 70, this query will run:

SELECT CUSTOMER.COMPANY_NAME,CUSTOMER.CUSTOMER_ID,ORDERS.ORDER_ID,MIN(ORDERS.ORDER_DATE) FROM CUSTOMER INNER JOIN ORDERS ON CUSTOMER.CUSTOMER_ID = ORDERS.CUSTOMER_ID GROUP BY CUSTOMER.customer_ID

Looking at the orders for Customer_id "ALFKI ", you'll see the minimum order date is 08/21/1992 and the order id for that date is 63.

The results in the query show the correct date, but the order id is 953. VFP arbitrarily grabs order id from the last physical record in the set of orders for that customer. I'm aware it is doing that, but I've been bitten by relying on the order id. VFP did what I told it to do, but the value of order id is dangerous.

>Mike,
>
>>Actually, you should not use enginebehavior 70. Some results may not be trusted.
>
>Could you expand on this issue ? Why could results be incorrect ?
>
>Walter,
>
>
>>>Thanks at alls.
>>>
>>>I resolved my trouble using the comand set enginebehavior 70.
>>>
>>>Aditional to this I could see that if I use this comand, I can make my views like I be in VFP 7 environment.
>>>
>>>Thanks at alls again.
>>>
>>>I allways get answer in this great site.