Re: ODBC ADministration

Buck, the strange thing is, one of the objects works but all others do not.
They all did at one time. The serious problem I am facing is if I have to
modify an existing Crystal report that is linked to the ibm i, via previous
ODBC object, I can add in the OBDC one that works, add in my new logical
for instance, and the program works locally but not when I publish it to
the Crystal Server. So it means having to recode an entire program using
the new ODBC object. The one that works I define as
in ODBC Administrator, SQL Naming convention with no SQL default library,
use odbc access mode, and a lib list. this works. the exact same params on
the others does not work. all they do is show QGPL. Since I made some
changes to this, maybe it needs a system IPL?
packages tab are both QGPL and use/add. other tabs are the same.




On Tue, Jul 19, 2016 at 10:21 AM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 7/18/2016 10:45 PM, Hoteltravelfundotcom wrote:

The issue is, I am having odbc for all my odbc data source administrator
it's not showing me the libraries I added on the server tab/library list.

Only shows QGPL. WHy is that happening?

Read up on the difference between System naming and SQL naming. If that
isn't helpful, please explain the steps you took in enough detail that a
reader can re-create the same situation.

--
--buck

Visit wiki.midrange.com and register for an account. Edit a page that
helps you, and because it's public, you'll help someone else, too!

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.