×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




You could make use of the same trick trigger programs do to see who caused
the trigger to be fired.

Send a message back up the call stack and then receive it.

Should find plenty of examples in the archive.

HTH,
Charles


> -----Original Message-----
> From: jlowary@xxxxxxxxxxxxx [mailto:jlowary@xxxxxxxxxxxxx]
> Sent: Tuesday, July 27, 2004 10:52 AM
> To: midrange-l@xxxxxxxxxxxx
> Subject: Procedures in Service Program
> 
> 
> When you call a procedure in a service program, does that 
> procedure have 
> anyway of knowing who called it?  (Other than passing it a 
> parm to tell 
> it)
> 
> Thanks,
> 
> -- Jim Lowary
> ToastMaster/Salton, Inc.
> --
> 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-2026 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.