• Type Mismatch in sEmailReply function

    By Rob Breault 2 decades ago

    When replying to baddly formated email from a Yahoo.com user (with over 20 Body fields), the function bombs out on line 58:



    Set org_rtitem = currdoc.GetFirstItem("Body")"



    This can be handled a few different ways… First to test to see if we have the original RT item and if so process as normal, otherwise force the "WithHistory" flag to be false or process the old RT differently (maybe check field type or do some fancy MIME handling) or just throw up a msgbox stating the issue..



    Thoughts?

    • Catching up...

      By Dave Leigh 2 decades ago

      The problem occurs with badly formatted email… does this happen often?



      I'm of the opinion that the copy should be turned off. Rather than a msgbox, perhaps the problem should be noted in the body instead of the uncopiable email, perhaps with a link to the document that couldn't be imported?