Thanks Charles, we will triple check that. I know I had them side by side looking at permissions, but perhaps another set of eyes.
Ken
From: Charles Wilt <charles.wilt@xxxxxxxxx>
Sent: Wednesday, December 18, 2024 1:35 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Ken Meade <kmeade@xxxxxxxxxxxxxxxxx>
Subject: [ EXTERNAL ]Re: When is a View not a View
"all authorities and permissions seem to be the same"
I'd double check that...the only reason I can think of that the view couldn't be seen/used would be authorities/permissions...
If the table/views are in different libraries, you might look at authorities/permissions for the libraries also.
Charles
On Wed, Dec 18, 2024 at 8:49 AM Ken Meade via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx>> wrote:
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> <mailto: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/><
http://www.littletoncoin.com/>
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related questions.
midrange.com
