I'm happy I could provide a new insight for you! I never hard-code filenames for the same reason: Set var vFile = 'C:\blahblahblah' Out &vfile Etc
This keeps my RSTYLE.CAS file clean. Dennis McGrath -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Rachael Malberg Sent: Friday, February 05, 2010 3:16 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Interesting Error message cool! I tell you what, I learn something new every day! ----- Original Message ----- From: "Dennis McGrath" <[email protected]> To: "RBASE-L Mailing List" <[email protected]> Sent: Friday, February 05, 2010 1:51 PM Subject: [RBASE-L] - Re: Interesting Error message Also, I have standardized on using quoted text values in my IN clauses because then RSTYLE will not pick them up as new words and will not change them in any way. RSTYLE basically takes a hands off approach to quoted text and numbers. Dennis McGrath -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of A. Razzak Memon Sent: Friday, February 05, 2010 1:11 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Interesting Error message At 01:40 PM 2/5/2010, Rachael Malberg wrote: >actually I bet it doesn't like your "in" string. >try...('020402ga','020411ne','020416ks') No. The "IN" string should not be a problem. To test and understand how R:BASE intelligently parses the "IN" string, try the following two examples: -- Example 01: CONNECT RRBYW16 PRINT INVOICE WHERE CustID IN (100,105,127) OPTION SCREEN -- Examnple 02: CONNECT RRBYW16 PRINT EmployeeList WHERE EmpLName IN (Wilson,Smith,Hernandez) OPTION SCREEN Notice that in both examples, with INTEGER and TEXT items in "IN" clause, the WHERE parameters are evaluated accordingly. That is your tip of the day! Very Best R:egards, Razzak.
