RE: SQL Prompts

A good book to get started is "SQL/400 Developer's Guide" by Conte &
Cravitz, 29th Street Press.

You can also use STRSQL at the 400 command line to check syntax.

Phil

> -----Original Message-----
> From: code400-l-admin@midrange.com
> [mailto:code400-l-admin@midrange.com]On Behalf Of Cyndi Bradberry
> Sent: Wednesday, October 17, 2001 2:52 PM
> To: 'code400-l@midrange.com'
> Subject: RE: SQL Prompts
>
>
> Thanks Phil,
> I agree, I adore Code. I have been frustrated because the ATS course uses
> SEU and I am inserting lines and trying to TAB to fields.  I haven't found
> PREPARE yet, Whoops ! Next chapter !
> I haven't tried the OPS NAV yet...maybe this afternoon.
> Cyndi
>
> -----Original Message-----
> From: Phil
> Subject: RE: SQL Prompts
> 1. You're going to find you use a host variable (a string) to
> hold your sql
> statements (so you can build, and then use PREPARE.  This negates
> the value
> of prompting.
>
> 2. SQL isn't overly complicated and you'll probably memorize the
> syntax (in
> time).  When I don't remember, I use iSQL in OpsNav as an aid.
>
> Phil
>
> PS: I think Code **as it is** is better than SEU.
>
> _______________________________________________
> This is the CODE/400 Discussion & Support (CODE400-L) mailing list
> To post a message email: CODE400-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
> or email: CODE400-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/code400-l.
>


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com