Re: Building a SQL statement...

Disregard my previous post...I found the error. Thanks

Thank you,
 
Antonio Mira
Application Developer
Time Warner Cable www.timewarnercable.com Mid-Ohio Division
1015 Olentangy River Road - 2nd Floor
Columbus, OH 43212
email:  antonio.mira@xxxxxxxxxxx
aim:    antomiratwc
phone: 614 827 7949 
 


-----Original Message-----
From: systemidotnet-bounces@xxxxxxxxxxxx [mailto:systemidotnet-bounces@xxxxxxxxxxxx] On Behalf Of Mira, Antonio
Sent: Thursday, October 30, 2008 3:41 PM
To: .net use with the System i
Subject: Re: [SystemiDotNet] Building a SQL statement...

Walden,

Thanks for your suggestion...I went with it but now I'm getting a different error which I don't know how to solve since the string looks ok to me but yet the execution of the sp complains. Here's the string that the VB program builds right before executing it...

"SELECT CEITM , CESER , CESTC , CESDT , CEHED FROM cohamira.CONVRPF WHERE CENROV = 2 and CEITM in ('SA83HDC')"

This is the error that I'm getting...

Message . . . . : String constant beginning 'S ' not delimited.
Cause . . . . . : The string delimiter is missing in the constant beginning
with 'S '. The string is treated as if it were delimited by the end
of the source file.
Recovery . . . : Delimit the string constant. Check for any missing or
extra quotation marks and apostrophes. These errors are likely to cause
other errors. Some statements may not have been processed as the result of
either missing or extra string delimiters. Precompile the program again.


Thank you,
 
Antonio Mira
Application Developer
Time Warner Cable www.timewarnercable.com Mid-Ohio Division
1015 Olentangy River Road - 2nd Floor
Columbus, OH 43212
email:  antonio.mira@xxxxxxxxxxx
aim:    antomiratwc
phone: 614 827 7949 
 


-----Original Message-----
From: systemidotnet-bounces@xxxxxxxxxxxx [mailto:systemidotnet-bounces@xxxxxxxxxxxx] On Behalf Of Walden H. Leverich
Sent: Thursday, October 30, 2008 2:09 PM
To: .net use with the System i
Subject: Re: [SystemiDotNet] Building a SQL statement...

You can't get there from here... :-)

The problem you have it this, if there's one value you'd want to run:

Select * from myFile where field1 in (parm1)

but if there were two values you'd need:

Select * from myFile where field1 in (parm1, parm2)

and three:

Select * from myFile where field1 in (parm1, parm2, parm3)

A single parm can have only the single value. It's one of the uglier
truths of SQL. BTW, same problem exists in SQLServer. :-)

I would recommend you just build the SQL statement as a text string so
long as you trust the values you're putting in not to be subject to SQL
injection.

-Walden