RE: Download to EXCEL from Relational DB

Scott,

Not that I have any problem with MSQRY as a means to accomplish this, but why 
would this solution be superior to a series of simple views on the iSeries?  
IMO, the views allow IT to better control access to relational data, and takes 
the DB join element out of the hands of the enduser.  For myself, I'd rather 
spend the time to optimize a view and make it available to the "power-users", 
instead of forcing each user to define the joins manually.  If they don't write 
their SQL correctly, they're more apt to clobber the system with their query 
than if they use an optimized static view.  

Perhaps I'm biased, since we have a VERY LARGE user base to support, and I'd 
rather do it just once than hundreds of times....

JMO....

Eric

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Scott Klement
Sent: Wednesday, November 22, 2006 1:51 PM
To: Midrange Systems Technical Discussion
Subject: Re: Download to EXCEL from Relational DB

I have a client that would like to be able to download data from their 
iSeries to an EXCEL file. The problem is that the data files are setup 
in a "relational" manner, not a flat file. Is there any PC product that 
will allow me to define the relationship between the files but have that 
complexity hidden from the end user?

Hmmm... in my copy of Excel, I can click Data / Import External Data /
New Database Query.  It bring up a list of files (or "tables" in 
SQL-speak) and a list of the fields (or "columns") that those files 
contain.  I can choose the fields I want, from more than one field (if I 
need to) and it'll bring them all into my spreadsheet.

Once I have the stuff I want, I can even save the query in a file so I 
don't have to go through the whole process again next time.

As far as I know, the only thing you need to do this (besides Excel, of 
course) is an ODBC driver.  There's one included with i5/OS (OS/400), as a 
free component of iSeries Access.

It surprises me that so many people are referring you to commercial 
packages, when this is something I take for granted as a feature built-in 
to office. I suppose the commercial methods are more powerful or simplify 
part of the process?