FEASIBLE ANSWER:
Surely you have one program doing the actual emailing? We
use something
called FaxMaker. Text records get written into _HOLD_, then
records are
copied to the software's inbox directory, from whence they
are emailed.
You can hijack the process at the "copy to inbox" stage.
Instead of
having the _HOLD_ file as the inbox, change this to another
directory.
Have something poll the _HOLD_ file fairly often - when
something is
found, ask your questions, change the data, and perform the
copy.
COMPLETELY IMPLAUSIBLE ANSWER
I don't know the feasibility of this approach, but its an
idea. You
could try hijacking the indexing system for this...
- create an I-type dict item in &HOLD&
(might have to create a dictionary for it) that calls a
program that can
prompt for the changes you want - it will also have to check
that the
extension on the trigger record is PDF.
- add an index to _HOLD_ on that I-type.
- everytime a record is added, removed, etc that index
will be
updated, meaning that program will run. Voila! Your
trigger...
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Charlie Rubeor
Sent: 24 June 2004 02:36
To: [EMAIL PROTECTED]
Subject: RE: [U2] [ud] Trigger on _hold_ file
Thanks for the reply.
-------
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/
