>You must list each field in the GROUP BY:
>
>GROUP BY b.Name, a.id_no, a.name, b.account... etc.

This is only a hypothetical question so far, Craig, as I haven't encountered any problems with vfp8 as of yet - but does this GROUP BY necessity have the capacity to cause performance hits, say on large data w/ many fields using GROUP BY, do you know? At first glance, it appears possible...

For example, we have some real slow apps (not mine) that use Sybase/Oracle with fairly small record #s, many fields, and the indexing seems proper. I've viewed some of the SQLs they use in these apps - and there are a great many fields in the GROUP clause as your code example above, except many more in these SQLs I'm referring to (example, 25 GROUP BY fields). May just be coincidence, and something else is causing the hits, of course.

Just curious if this might crop up as an issue for vfp?