aatcbbtccctc
2003-12-14 03:33:16 UTC
Hi folks
I'm considering using BLAT.DLL to add a "mailmerge to email" function
to my primary software product. This would let the users send
customized emails to selected people, without having to type in each
one manually.
But one thing worries me about whether BLAT is really ready
for "prime time". That is, the error handling (or lack thereof!). My
users will need a simple notification of any errors that occur. For
example: "Could not contact mail server"; "Address rejected:
***@blah.com", & so on.
I can't see how to do that, given the limited number of error codes,
& the use of certain codes for multiple (different) error conditions.
(Eg. error 99 means, "the server is down or the address is invalid or
the parameters are incorrect or today is a bank holiday or your
brother's hat is on the wrong peg!")
So here's my question. To people who have integrated BLAT into a
production application: how do you approach the error handling? How
does your calling code determine what has gone wrong, & produce an
accurate message that a non-technical user can understand?
Thanks in anticipation,
TC
------------------------ Yahoo! Groups Sponsor ---------------------~-->
Buy Ink Cartridges or Refill Kits for your HP, Epson, Canon or Lexmark
Printer at MyInks.com. Free s/h on orders $50 or more to the US & Canada.
http://www.c1tracking.com/l.asp?cid=5511
http://us.click.yahoo.com/mOAaAA/3exGAA/qnsNAA/dkFolB/TM
---------------------------------------------------------------------~->
Homepage:
http://www.blat.net
I'm considering using BLAT.DLL to add a "mailmerge to email" function
to my primary software product. This would let the users send
customized emails to selected people, without having to type in each
one manually.
But one thing worries me about whether BLAT is really ready
for "prime time". That is, the error handling (or lack thereof!). My
users will need a simple notification of any errors that occur. For
example: "Could not contact mail server"; "Address rejected:
***@blah.com", & so on.
I can't see how to do that, given the limited number of error codes,
& the use of certain codes for multiple (different) error conditions.
(Eg. error 99 means, "the server is down or the address is invalid or
the parameters are incorrect or today is a bank holiday or your
brother's hat is on the wrong peg!")
So here's my question. To people who have integrated BLAT into a
production application: how do you approach the error handling? How
does your calling code determine what has gone wrong, & produce an
accurate message that a non-technical user can understand?
Thanks in anticipation,
TC
------------------------ Yahoo! Groups Sponsor ---------------------~-->
Buy Ink Cartridges or Refill Kits for your HP, Epson, Canon or Lexmark
Printer at MyInks.com. Free s/h on orders $50 or more to the US & Canada.
http://www.c1tracking.com/l.asp?cid=5511
http://us.click.yahoo.com/mOAaAA/3exGAA/qnsNAA/dkFolB/TM
---------------------------------------------------------------------~->
Homepage:
http://www.blat.net