- Local time
- Today, 10:28
- Sep 21, 2011
Ah, OK. I am talking about a home outlook setup and I have mine setup for a regular Send and Receive every 30 mins.I'm a bit curious on why you believe this is the case. Given a few seconds of time to be open, why would it not send the email, once the appropriate code to send it has fired?
That way I either manually send and receive (normally the case) or wait until the time period has expired.
That allows me to correct an email if need be, unlike in a coporate environment with Exchange where it disappears as soon as Send is clicked.
Again Bad Memory.
I've just tested with my DB and that is what happens in my environment.
However it raises an issue, if you do not test if it is open or not, how do you decide to set the object to Nothing or not.?
I think that was the reason for fIsOutlookRunning flag originally being used, but I must have been having problems with GetObject() as you mentioned to change the logic.?
Long time ago now, so cannot remember why.