M
Martin Wulfe
[thought i'd start at the top, tired of scrolling down...]
Adrian -
Thanks for your message. I did have something of a problem sending
the last post, so i'm not at all surprised it came out gabbled.
And thanks for your suggestion, but I don't think it will work. Here's
why.
Every combination of potential users can be sent any combination of
messages. Repeat messages regarding the same record number to the
same recipient is also a possibility, and would be reasonable.
I'll describe the make-shift system I have put together. the .Net app
creates a file in a shared folder whose filename has the record number
appended to the end. This file is a vbsript that executes the exe
file with a unique record number, which also happens to be the number
at the end of the filename. In the email that recipient gets, the
HTML uses an HREF pointing to the vbscript file, based on the record I
want the recipient(s) to look at..
I'm not sure that makes any sense. But if you can think of an
all-HTML solution to this, I could avoid have an application that will
end up creating, sooner or later, more than 500 vbscript files.
It would also be elegant.
Martin
Adrian -
Thanks for your message. I did have something of a problem sending
the last post, so i'm not at all surprised it came out gabbled.
And thanks for your suggestion, but I don't think it will work. Here's
why.
Every combination of potential users can be sent any combination of
messages. Repeat messages regarding the same record number to the
same recipient is also a possibility, and would be reasonable.
I'll describe the make-shift system I have put together. the .Net app
creates a file in a shared folder whose filename has the record number
appended to the end. This file is a vbsript that executes the exe
file with a unique record number, which also happens to be the number
at the end of the filename. In the email that recipient gets, the
HTML uses an HREF pointing to the vbscript file, based on the record I
want the recipient(s) to look at..
I'm not sure that makes any sense. But if you can think of an
all-HTML solution to this, I could avoid have an application that will
end up creating, sooner or later, more than 500 vbscript files.
It would also be elegant.
Martin