jimbrooking
Registered User.
- Local time
- Today, 05:02
- Joined
- Apr 28, 2001
- Messages
- 210
Has anyone found success and happiness in using CDO for Win 2000 to send email? Apparently this is MS's new! improved! way to fire off email from your apps. I copied some code off the MS site at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cdosys/html/_cdosys_about_cdo_for_windows_2000.asp
for testing. (The code is on Messaging>Examples>Creating and Sending a Message.) Had to comment out a line that read
.Item(cdoSMTPServerName) = "myservername"
because I kept getting an undefined variable cdoSMTPServerName.
My references include MS ActiveX 2.5 and MS CDO for Win 2K as MS specifies. That variable name (cdoSMTPServerName) gets NO hits on Google - a first, I think.
With that line commented out, the snip of code from the MS site works OK on my machine w/Access 2000 SR-1, but not on the machine of the person for whom I'm writing the code. She has Access 2000 SR-2, with the nefarious Outlook Security Patch on it.
Has anyone managed to slog through CDO and get it to work in the presence of the Outlook Security Patch?
FWIW I am doing the function (sending email from my Access app) using the Outlook.Application object, which again works fine (but slowly) on MY machine, but issues a slew of "informative" security-related messages for each email that gets sent (even more slowly) through my co-worker's machine with the Outlook Security Patch.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cdosys/html/_cdosys_about_cdo_for_windows_2000.asp
for testing. (The code is on Messaging>Examples>Creating and Sending a Message.) Had to comment out a line that read
.Item(cdoSMTPServerName) = "myservername"
because I kept getting an undefined variable cdoSMTPServerName.
My references include MS ActiveX 2.5 and MS CDO for Win 2K as MS specifies. That variable name (cdoSMTPServerName) gets NO hits on Google - a first, I think.
With that line commented out, the snip of code from the MS site works OK on my machine w/Access 2000 SR-1, but not on the machine of the person for whom I'm writing the code. She has Access 2000 SR-2, with the nefarious Outlook Security Patch on it.
Has anyone managed to slog through CDO and get it to work in the presence of the Outlook Security Patch?
FWIW I am doing the function (sending email from my Access app) using the Outlook.Application object, which again works fine (but slowly) on MY machine, but issues a slew of "informative" security-related messages for each email that gets sent (even more slowly) through my co-worker's machine with the Outlook Security Patch.
