I was sending email through Outlook using automation. I was doing
this with a standard vbmodule and a reference to Outlook. Because of
the security changes in Outlook I decided to move to another method.
I found a dll on the web to send mail and it even had VBA class module
example.
To make a long story short when I create a new instance of this class
and then use it to send mail the form which instanciates the class
object is still active. It's as if the code in the class is running
independently.. . I don't want that behavior. Is there anyway to stop
that or should I just go back to using a standard module?
this with a standard vbmodule and a reference to Outlook. Because of
the security changes in Outlook I decided to move to another method.
I found a dll on the web to send mail and it even had VBA class module
example.
To make a long story short when I create a new instance of this class
and then use it to send mail the form which instanciates the class
object is still active. It's as if the code in the class is running
independently.. . I don't want that behavior. Is there anyway to stop
that or should I just go back to using a standard module?