You got the right answer because you sorted descending and the first record in the returned recordset will have the latest date. The first record gets assigned to the variable and the rest thrown away.
using max is a much more elegant solution. Dennis McGrath --- Bernard Lis <[EMAIL PROTECTED]> wrote: > Hi Allen, > Now why didn't I think of that, there's another DUH!however when I > started, > I was not aware that there were duplicates. Then I added the order > by (that > was stupid) but I was surprised to see that I got the right answer.. > Thanks for waking me up. > Bernie Lis > ----- Original Message ----- > From: "Alan Wolfe" <[EMAIL PROTECTED]> > To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> > Sent: Friday, August 06, 2004 4:58 PM > Subject: [RBASE-L] - Re: too many rows returned > > > > im not sure but could you select max(eventdt) instead of selecting > them > all > > and sorting descending? > > > > might be a faster lookup too that way > > > > ----- Original Message ----- > > From: "Bernard Lis" <[EMAIL PROTECTED]> > > To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> > > Sent: Friday, August 06, 2004 1:42 PM > > Subject: [RBASE-L] - too many rows returned > > > > > > > Can I count on this happening? > > > > > > set var event date > > > sel eventdt into event from docket where clno=.clnum and eventcd > = 'stc' > > > order by eventdt=d > > > > > > Although it results in the error message "too many rows > returned", I am > > > getting the latest date in the variable event. > > > This is exactly what I want, can I count on this for all cases? > > > > > > Bernie Lis > > > > > > > > >
