RE: iSeries and Microsoft Query (Excel)

["Elvis Budimlic" <ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx>]

Sounds like a Microsoft problem... perhaps they assume SQL naming when using
this interface.

That's strange since I occasionaly use Microsoft Query to test certain
things. I do go directly to it's Office folder path, rather than going
through Excel, i.e.:

"C:\Program Files\Microsoft Office\Office10\MSQRY32.EXE"

Then I click File->Execute SQL, pick a data source with *SYS naming and all
works.

Perhaps OP can use IBM's data transfer utility instead?  
It would show as "Transfer data from iSeries..." under the Data menu option
in Excel.
That always worked for me.

Elvis

Celebrating 10-Years of SQL Performance Excellence


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Friday, March 09, 2007 2:19 PM
To: Midrange Systems Technical Discussion
Subject: Re: iSeries and Microsoft Query (Excel)


Hello,

> When I enter the SQL, I get the error message "SQL Query can't be 
> represented graphically." I OK this non-error. However, the next error 
> is "Could not add the table 'vngdbdta/dbnxcpp'. One of the table 
> selects is vngdbdta/dbnxcpp. I verified my ODBC connection uses *SYS 
> naming; the library list shouldn't matter as I'm qualifying the table 
> name.

I receive the same error anytime I try to use *SYS naming.  (Even though 
I have the ODBC driver configured for *SYS).   When I change my SQL 
statement to use *SQL naming (i.e., replace the slash with a dot) I have 
no problem.