Why do it in a few lines of code when you can do it in 30 ?? ;-) Nah. I just made the procedure as a framework (for code reuse) that would return 1 or 0 cause you can make the IN list to be anything you want (you could change the procedure to accept the IN list as a parameter without much tinkering) and in the app I created it, the SP is called dozens of times.
----- Original Message ----- From: "Mike Willochell" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> Sent: Wednesday, September 24, 2003 8:58 PM Subject: [RBASE-L] - Re: Convert Text to Currency > At 11:03 AM 9/24/2003 -0500, you wrote: > >Yeah, but these things will always crap out on you if you don't to some > >checking to see if the entry > >is a valid numeric to start. > > Mike; > > You bring up a very good point. I use a much simpler technique for screening > this criteria using error variables: > > -----Begin Code Snippet----- > > LABEL tryagain > SET VAR vkcriteria TEXT = NULL > RHIDE > DIALOG 'Enter KENO:'=20 vkcriteria=10 vend 1 CAPTION 'Criteria' AT + > CENTER CENTER > IF vkcriteria <> '[ESC]' AND vkcriteria IS NOT NULL THEN > SET ERROR VARIABLE verrvar > SET VAR vkcriteria INTEGER = .vkcriteria > IF verrvar <> 0 THEN > CLS > RHIDE > PAUSE 2 USING 'Please Enter A Valid INTEGER Value!' CAPTION > 'Message' + > AT CENTER CENTER > GOTO tryagain > ENDIF > SET ERROR VARIABLE OFF > ENDIF > > -----End Code Snippet----- > > A little less elegant, but it gets the job done just the same. > > Mike > >
