CDO in VFP using Office365 1

[bsutton55]

We are due to upgrade our server running SBS2003 to run W2012 using Office 365 hosted exchange. I am told that Collaboration Data Objects (CDO) 1.2.1 is not supported with Outlook 2010 and later versions and am advised to rewrite my VFP CDO code to use Outlook objects.

A couple of questions:
1. If I use Outlook objects in 2010 onwards, does the security nag pop-up (".. another application is trying to send email on your behalf...etc") still need to be negotiated (as this was the main driver behind writing the CDO method in the first place).
2. If there is still an issue with the nag screen in later versions of Outlook, what will be the best way to send email (possibly with attachments) from within VFP when using Office 365?

The main use we have for the CDO routine at present is to batch run several hundred email despatch notifications at time without the need to store them.

Thanks
Barry Sutton.

 

[Nigel Gomm]

see

http://www.dimastr.com/redemption/home.htm

and RDO.

it supports RPC over http and Dmitry is full of help and advice.


hth

n

 

[Olaf Doschke]

A larger customer we have has configured Outlook (2010 and now 2013) Trust Center to not nag about automation, so there is an internal way to turn that off without Redemption.
Also Office365 hosted exchange like older versions of exchange not necessarily mean users only use the web interface outlook.com. I'm Officee365 user myself and we have installed the "classic" full Outlook and other Office applications.

I can instanciate both cdo.configuration and cdo.message on Win8.1 with Outlook 2013, so CDO still is present, that also isn't the problem.
I just don't know how to setup the cdo.configuration object to be able to send. Office365 hosted exchange means different connections than simply via SMTP.

Sending mails via outloookk.application is possible, though and in my configuration does not nag about automation. I can't help you with the Trust Center, that's done administrative, in my case remote to my office, but it's possible to use the outlook object model without the third part redemption add on.

Bye, Olaf.

 

[bsutton55]

Nigel
Thank you - I was kinda hoping to avoid using Redemption as I tried it many moons ago and could not get it to work correctly - entirely my fault I am sure!
Bye
Barry

 

[bsutton55]

Hi Olaf
In your final paragraph when you talk about your own configuration, are you saying that you it is set up with the Trust Center to avoid the nag about automation, but this has been done by the system administrator?
Thanks
Barry.

 

[Olaf Doschke]

In the last paragraph I talk about the outlook configuration in general. And yes, it has been done for me, I didn't set it up to stay quiet, so I can't help you with that, but the hint on the Trust Center plus Goolge should find you something, eg

http://www.slipstick.com/developer/change-programmatic-access-options/

Bye, Olaf.

 

[Olaf Doschke]

Also as far as I can go into trust center settings, in programmatic access the first option "Warn me about suspicious activity when my antivirus software is inactive or out-of-date (recommended)" is set. Below all three options the Antivirus status is Valid, so I don't get a nag dialog when creating a mail item from VFP.

If administrators of a bigger corporation set this to "Always warn me about suspicious activity" you always will get the nag screen, I think.

Bye, Olaf.

 

[bsutton55]

Olaf
Thanks - very helpful.
Barry