Razzak, I found I was using the wrong table. I have that particular report based on a view. Once I changed that, everything works.
Thanks again, Jim -----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.
