You could convert over to using the Outlook object model as opposed to direct MAPI. I'm using Outlook automation with no problems.

>I have an email enabled application written in VFP that's been working fine for years. The program uses Active Messaging (via CREATEOBJECT("Mapi.Session")) to send email. Customers that have recently installed Outlook 2000 are now experiencing problems with the application. I found that the new Outlook is changing the current directory to the location of its DLLs on the hard drive and doesn't change back to the original directory. My application is sensitive to sudden environment changes like that. The quick fix, of course, is to save and restore the directory myself, but I'm suprised that Outlook's MAPI object doesn't take care of this anymore. Has anyone ran into this problem? If so, do you know a better solution? Any other new "features" in Outlook 2000 I should watch out for?
>
>Thanks,
>Ron