× 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.


  • Subject: Re: Who pulled the trigger?
  • From: booth@xxxxxxxxxxxx
  • Date: Mon, 12 Jun 2000 23:55:20 GMT

This isn't the answer you want to hear but I'll say it anyway. 

David has done a remarkable job with the Midrange.com website.  The 
Archives have all of our posts and they are searchable by threads.  I've 
found that looking up answers there is fast and I especially enjoy being 
able to see all the replies, one after another, without waiting for tempus 
to fugit.

_______________________
Booth Martin
booth@martinvt.com
http://www.MartinVT.com
_______________________




Sue Underwood <sueu@alltel.net>
Sent by: owner-rpg400-l@midrange.com
06/12/2000 04:16 PM
Please respond to RPG400-L

 
        To:     "RPG400 (E-mail)" <RPG400-L@midrange.com>
        cc: 
        Subject:        Who pulled the trigger?

This question has been asked on this forum recently, but I didn't have the 
foresight to save the responses. (duh!) 

Can any of you gurus tell me how I can determine what program caused the 
trigger to fire?  Is it even possible? 

Thanks
Sue

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-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 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.