Rox,

I've always used it this way without trouble. Perhaps your coworker remembers an inaccurate statement from the FoxPro 2.6 help file. There's a KB article that describes the erroneous help entry at http://support.microsoft.com/support/kb/articles/q114/4/79.asp.

Now go home!

>Hey all,
>I'm at work on Saturday < sigh > and I have the following query that seems to produce the correct results:
>
>

>SELECT Audit98.Audit, Audit98.IPN, Audit98.EndDate, ;
>MAX(PrvBeds.EffDateB), PrvBeds.CertifBeds, PrvBeds.MorBeds ;
>FROM Audit98, PrvBeds ;
>INTO CURSOR Latest_Beds ;
>WHERE Audit98.ipn = PrvBeds.ipn ;
>and audit98.enddate >= PrvBeds.EffDateB ;
>GROUP BY 1,2
>

>
>But my coworker seems to think use MAX() in a query in this manner is not correct due to some foxpro glitch. This glitch is new to me, but we're under the gun and I need quick confirmation that this query should be fine. Can anybody confirm or explain a glitch with using MAX() in this manner? TIA!!