RE: Query/SQL/Excel

["DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx>]

The Query/400 product does not store its definition criteria in a source 
member.  It creates an object of type *QRYDFN (Attr: QRY) which holds all of 
the definition attributes.  This object can be "converted" to SQL source using 
the RTVQMQRY and the ALWQRYDFN(*YES) option...  This conversion is not always 
correct, so use with caution...

hth,
Eric

-----Original Message-----
From: midrange-l-bounces+edelong=sallybeauty.com@xxxxxxxxxxxx
[mailto:midrange-l-bounces+edelong=sallybeauty.com@xxxxxxxxxxxx]On
Behalf Of John Candidi
Sent: Tuesday, July 03, 2007 12:22 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Query/SQL/Excel 


Dumb question. When I create a query using WRKQRY, is there a source file
automatically created somewhere? Let's say I create INV1 query in mylib,
where is the source file and what is it called?

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Campin
Sent: Tuesday, July 03, 2007 12:55 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Query/SQL/Excel 

<snip>
So the question is what SQL 'editor' can I use to sit between an ODBC
connection to the iSeries and Excel? I realise this is not necessarily
an
iSeries specific question, but I can't be the only person here who wants
to
do this,
</snip>

You can have the best of both worlds. 

Create a query using WRKQRY and then do a:

RTVQMQRY QMQRY(YOURQRY)          
         SRCFILE(MYLIB/QSRCF)    
         ALWQRYDFN(*YES)         
                                 
This retrieves the sql for a given query. 

The other better solution to anything that accesses the AS/400 from the
PC is use a stored procedure. Encapsulate all the processing in the
stored procedure (RPG or SQL language) and just call if from Excel.
Excel just gets the results.