Re: SQL Statement

[pnelson@xxxxxxxxxx]

Thanks guys, I sent him the link to the redbook. These folks are bound and 
determined to do all their development in the SQL Server world. They don't 
have any RPG talent even though they are running their line of business 
software on an iSeries. I just got silence from this developer when I told 
him that he could get his results faster with an RPG program and some 
logical files. 

Oh well, lead a horse to water and all that.... :-))


Paul Nelson
Arbor Solutions, Inc.
708-670-6978  Cell
pnelson@xxxxxxxxxx





Donald Whittaker <donald_whittaker@xxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
03/22/2005 10:29 AM
Please respond to Midrange Systems Technical Discussion
 
        To:     Midrange Systems Technical Discussion 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Subject:        Re: SQL Statement


   Did they want this to return a result set?  If so,
you might want to look at SG24-6503-01 (the Redbook
"Stored Procedures, Trigger, and User Defined
Functions").  There is a section on returning result
sets from SQL stored procedures.

Also not a guru,
Don 

--- pnelson@xxxxxxxxxx wrote:
> Thanks, but he's not trying to create a new table,
> just retrieve data from 
> the 400.
> 
> 
> Paul Nelson
> Arbor Solutions, Inc.
> 708-670-6978  Cell
> pnelson@xxxxxxxxxx
> 
> 
> 
> 
> 
> "Paul Morgan" <pmorgan@xxxxxxxxxxxxxx>
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 03/22/2005 10:09 AM
> Please respond to Midrange Systems Technical
> Discussion
> 
>         To:     midrange-l@xxxxxxxxxxxx
>         cc: 
>         Subject:        Re: SQL Statement
> 
> 
> Paul,
> 
> Check the SQL reference manual for the SELECT
> statement.  A SELECT 
> statement
> can only be run interactively.  A SELECT INTO
> statement can only be run
> embedded in an application program.  Because the
> SELECT statement is being
> placed into a stored procedure it's not running
> interactively.  You need 
> to
> modify the SELECT to either place it's results into
> variables (using the
> SELECT INTO format the error message refers to) or
> convert it to an INSERT
> statement so that it's results get placed in another
> table.
> 
> Not a guru,
> Paul
> 
> -- 
> Paul Morgan
> Senior Programmer Analyst - Retail
> J. Jill Group
> 100 Birch Pond Drive, PO Box 2009
> Tilton, NH 03276-2009
> Phone: (603) 266-2117
> Fax:   (603) 266-2333
> 
> Paul Nelson wrote
> 
> > Any SQL gurus out there? The statement below
> generates the following
> > message when the user tries to compile it as a
> stored procedure. I'm at 
> a
> > loss
> >
> > MSG ID  SEV  RECORD  TEXT
> > SQL0029  30      65  Position 10 INTO clause
> missing from embedded
> > statement.
> >
> > TIA
> >
> > Paul Nelson
> > Arbor Solutions, Inc.
> > 708-670-6978  Cell
> 
> 
> 
> -- 
> This is the Midrange Systems Technical Discussion
> (MIDRANGE-L) mailing 
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit:
>
http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the
> archives
> at http://archive.midrange.com/midrange-l.
> 
> 
> -- 
> This is the Midrange Systems Technical Discussion
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit:
>
http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the
> archives
> at http://archive.midrange.com/midrange-l.
> 
> 


 
__________________________________ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/ 
-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.