|
OK. I tried both suggestions: using *SQL naming, and putting schema and table names in upper case. Now the error I see is: SQL0206 - Column PROD not in specified tables. The SQL below works in iNav's Run SQL Scripts. with TEMP as (select nxkjdt, nxjpt2, sum(NXS7FQ) as tran from VNGDBDTA.DBNXCPP where nxkjdt between 1070301 and 1070307 group by nxkjdt, nxjpt2), TEMP2 as (select dmatdt, dmekcd, sum(dmgzfq) as prod from VNGDBDTA.DBDMREP where dmqwtx = 'SFR' and dmcdcd = ';MRCT' and dmatdt between 1070301 and 1070307 group by dmatdt, dmekcd) select dmatdt, dmekcd, prod, tran, prod - tran as makeup_entry from TEMP2 left outer join TEMP on dmatdt = nxkjdt and dmekcd = nxjpt2 where (prodo - tran) <> 0 order by 1,2 Thanks, Loyd Loyd Goodbar Senior programmer/analyst BorgWarner TS Water Valley 662-473-5713 -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Elvis Budimlic Sent: Friday, March 09, 2007 16:00 To: 'Midrange Systems Technical Discussion' Subject: RE: iSeries and Microsoft Query (Excel) 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.