Hi all,

Happy Holidays.

Ran into a new one for us. We are migrating reports to a new system and we ran into an issue where the new system, that uses a JDBC connector is not seeing some of our SQL Views. These all appear to be created in the same way that other views, that the new system recognizes.

Now, I thought I'd take this a step further and tried accessing it from excel using an ODBC driver, and low and behold, I'm having the same issue where the iSeries Access ODBC driver doesn't see those views either!

They are all being created with a CREATE VIEW statement, all authorities and permissions seem to be the same. We were wondering if related to files being referenced in different libraries, and in fact found that one table being referenced is seen in the ODBC driver, but not the JDBC driver.
And since that table can be seen in the ODBC driver, if that was the issue, why wouldn't we be able to see the View using it?
But one thing at a time.


What are we missing that makes these views invisible to both a JDBC and ODBC drivers?

Thanks,
Ken Meade

Ken Meade | Director of Information Technology and Infrastructure
kmeade@xxxxxxxxxxxxxxxxx <mailto:kmeade@xxxxxxxxxxxxxxxxx> | (603) 444-3570
[cid:image001.png@01DB5139.A0104C50]
Littleton Coin Company, Inc.
1309 Mt Eustis Rd, Littleton NH 03561
www.littletoncoin.com<http://www.littletoncoin.com/>



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.