I'm glad to help, Ravi.

There were already negative implications to putting fields in a SELECT statement, and not having those fields in the GROUP by clause. VFP grabs the data from the last record in the group, which may or may not be the data you want. In your example, the name of only one the patients for a given time slot is returned in the query. Since you don't care which patient is shown, it is not a problem for you.

Using SET ENGINEBEHAVIOR simply forces you to be aware that there is *potentially* a problem with a given SELECT statement (and that the problem potentially existed in previous versions). That is why I suggested that you turn it on and off, only for certain SELECT statements.

I'll restate it this way: using SET ENGINEBEHAVIOR in VFP8 is not any more dangerous than using that same SELECT statement in another version of VFP.

Do you understand the situation?

>Thanks Steve. I think, this makes more sense. However, at a macroscopic level, will using Set EngineBehavior have negative implications down the road.