Thanks, but that's not the issue. Outlook 365 is installed locally on the pc, and I can do many other automation tasks. There only seems to be an issue with setting the oMailItem.SendUsingAccount property. After setting it to a valid mail account object, it still has a null value. Can someone please try it, using the code example in my original post? Again, setting SendUsingAccount used to work. I have two pop3 accounts in Outlook 365. And now for some reason, it seems VFP can't set the SendUsingAccount property. It would help to know if someone else is able to set it, and what version of Outlook you are using. Thanks!

>>I'm copying the code below from an old Blog, but it describes the issue exactly. Setting loItem.SendUsingAccount was working fine until recently. Most likely a recent update to Outlook 365 or 2016 seems to have broke it. Is anyone else able to set loItem.SendUsingAccount property successfully, as in the following example? Or does anyone have a solution to make it work? TIA!
>
>AFAIR you need local installs for COM interfaces to work.
>
>>So, the question is: How to create mail item having the SendUsingAccount
>>property R/W using automation in VFP?
>>
>>Similar code works fine in VB.NET, so it seems to be purely VFP - Outlook
>>interoperability problem.
>
>If my memory from above is correct, .Net working on the same machine as vfp failing points to local install with some problem on the vfp code side...