|
Check out KB:9951625 & 23391421 in IBM's Software Technical Documents. IBM has a wonderful "feature": any libraries specified in the ODBC connection are added to the END of the default library list. That library list will be carried over to any trigger programs that are called. To override the default library list, you have to use the secret-IBM-decoder ring. Inserting a leading comma before any other library listed in the ODBC connection will cause the ODBC connection to use the library list as specified on the ODBC connection. And yes, the leading comma disappears once you hit enter, but it does work. And yes, it doesn't work on editing an ODBC connection, only when creating a new one. And yes, there would be absolutely no way of knowing any of this from the help provided with Client Access's ODBC driver. And yes, my language after learning of this wonderful feature was quite colorful...... ----Original Message----- From: news.software.ibm.com [mailto:Tom.wheeler@xxxxxxx] Sent: Monday, April 21, 2003 10:25 AM To: midrange-l@xxxxxxxxxxxx Subject: Insert using ODBC/system DSN I am under the gun to get this to work... I have a fileA that has a trigger that calls rpg program. When I insert a record into fileA the trigger calls a rpg program that writes another record to fileB. In the RPG program it does a call to another rpg program in a different library then the trigger program is in. I tried to add the library to the odbc/dsn description library list but that did not work. The user profile the odbc uses calls a initial program the signs itself off so now one can sign in using it adding it there will not work. I do not want to modify the rpg because it is a third party program. ..... Please any help would be appreciated. ******************************************
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.