× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I think there are probably items in the archive - I think it involves sending 
messages up the call stack. This comes under the general heading of identifying 
what program calls your program, not just in a trigger setting. There is an 
issue with triggers, because your program is not directly called by the one you 
are interested - the database gets in there somewhere.

HTH
Vern

-------------- Original message -------------- 

> 
> 
> 
> Stan Fellers 
> Senior Programmer Analyst 
> Magellan Health Services 
> 314-387-4243 
> 314-387-4270 fax 
> 
> message: 4 
> date: Fri, 2 Sep 2005 10:55:42 -0500 
> from: fkany@xxxxxxxxxxxxxxxxxx 
> subject: pgm that triggered the trigger pgm? 
> 
> 
> Does anyone know how to let a trigger program know which program 
> triggered it? The program status datastructure didn't have that 
> information. 
> 
> Thanks, 
> 
> Frank 
> 
> 
> 
> 
> ------------------------------ 
> Under what circumstance are you setting up a trigger? By definition, a 
> trigger is established on a file to perform some function when a record 
> is added/changed/deleted from that file. 
> 
> If you can give a little background on what you wish to accomplish I may 
> be able to help. 
> 
> -- 
> 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. 
> 

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.