|
John Carr wrote: > looking at the program stack and see what application program was calling the > trigger,etc.) John, Perhaps you can answer a question I've had on triggers regarding the calling program.... Why wasn't this information included in the parameters? This would seem like the obvious place for it, instead of making us jump thru hoops to get this information. Or am I missing an easy way to get this information? Currently, I'm using Send & Receive message API's to get the calling program's name. Is there a better way? -- Nelson Smith Haines City, FL, USA ncsmith@gate.net * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This is the Midrange System Mailing List! To submit a new message, * * send your mail to "MIDRANGE-L@midrange.com". To unsubscribe from * * this list send email to MAJORDOMO@midrange.com and specify * * 'unsubscribe MIDRANGE-L' in the body of your message. 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-2025 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.
midrange.com
