Hello,
Everything goes as you want ;)
You do it like this:
1. As they wrote above, in the procedure that sends an email, you must have the content entered as HTMLBody (instead of Body)
2. You have to cram into the directory where you have your Outlook signatures and then "suck" the specific signature with the HTML code
3. The sucked code must be added to the content of the email in the sending procedure
Okay, now the specifics:
ad1.
I think it's simple here
changing .Body to .HTMLBody :P
ad2.
I recommend doing it with Environ (because the signatures are in the directory depending on the username in the system), that is
c:\users\ tutaj_twoja_nazwa_usera \AppData\Roaming\Microsoft\Podpisy\i_tutaj_nazwa_twojego_podpisu.htm
!!!CAUTION!!! check this path at home because I don't remember now why but sometimes instead of the Signatures directory, some have the Signatures directory so then it will be of course:
c:\users\ tutaj_twoja_nazwa_usera \AppData\Roaming\Microsoft\Signatures\i_tutaj_nazwa_twojego_podpisu.htm
Okay, everyone has a different username, so when I do something like this with people on training, we use Environ here. So in the end it would look like this:
sciezka = Environ("USERPROFILE") & "\AppData\Roaming\Microsoft\Podpisy\" & podpisek & ".htm"
Ok, the path to the signature is there, now we're downloading HTMLA from it.
We have several options here, but probably the simplest will be the readall function built into the TextStreem object from the scrrun.dll library (it's cool, it's Windows, so everyone has it, so do you
we can add this biblio through early or late binding (but that's a topic for another post ;)
There may still be problems with images if you have them in the footer (especially when we have several footers and the macro is to decide which one to add to the email when). If you write it like this, I'll be happy to help :)
Regards
Michal Dabrowski
