I guess it depends on what you're trying to do. The decimal point breaks the "0N" (unless you do "0N"."0N"). :-)
However, I thought the original poster was trying to prevent a non-numeric warning. A NUM() would catch that, an INT() to lop off the decimal, and a check against a DCOUNT() for sanity would also do the trick. Best, -- John Solie -- Professional Hospital Supply -- 951-296-2600 > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > [EMAIL PROTECTED] > Sent: Thursday, March 10, 2005 9:56 AM > To: [email protected] > Subject: RE: [U2] [UV] "non-numeric" error after passing (ANS > MATCHES '0N' & ANS>0) > > In short they aren't the same... Try this: > > A = "1.1" > PRINT NUM(A) > PRINT A MATCHES "0N" > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of John Solie > Sent: Thursday, March 10, 2005 12:24 PM > To: [email protected] > Subject: RE: [U2] [UV] "non-numeric" error after passing (ANS MATCHES > '0N' & ANS>0) > > I'm wondering why y'all are using a ...MATCHES "0N"... Usually, I'll > use > the NUM() function. The code snippet in one of the first messages in > this > thread would be: > > BEGIN CASE > CASE NUM(ANS) AND ANS > 0 > <more code here> ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
