|
Add the ovrdbf command to the trigger program and then user control the opening of the file. It works but its ugly. Christopher K. Bipes mailto:ChrisB@Cross-Check.com <mailto:ChrisB@Cross-Check.com> Sr. Programmer/Analyst mailto:Chris_Bipes@Yahoo.com <mailto:Chris_Bipes@Yahoo.com> CrossCheck, Inc. http://www.cross-check.com <http://www.cross-check.com/> 6119 State Farm Drive Phone: 707 586-0551 x 1102 Rohnert Park CA 94928 Fax: 707 586-1884 *Note to Recruiters Neither I, nor anyone that I know of, is interested in any new and/or exciting positions. Please do not contact me. -----Original Message----- From: boothm@earth.goddard.edu [mailto:boothm@earth.goddard.edu] Sent: Wednesday, October 27, 1999 2:45 PM To: midrange-l@midrange.com Subject: triggered file list problem This seems easy and I am sure I will be promptly embarrassed but it has me stumped at the moment. I have a file, lets say "FILEMaster", in a Library that is not on the default library list. There is also a file, lets say "FILEMAudit", in the same library. The FILEMaster file has a trigger attached to it and upon any change a new record is written to FILEMAudit. This is all well and good so long as I use a normal application and have the library list correctly include this library. However if I use some program outside of the norm, say DFU or ODBC, and start the job with a qualified name of "Library/FILEMaster" then I get serious troubles. Is there a way in the trigger program where I can use a qualified library name? thanks. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.