>Greg,
>
>I'm not familar with how Outlook handles meeting schedule and task management. If there's a way for Outlook to receive this information via standard SMTP based emails, then I would say a cautious yes. There are open standards for exchanging contact info and calendar events, but I'm sure how accurately Outlook supports (if at all) these standards.
>
>If you just want to send email, then Blat is a great tool and I can help you. If you want to Outlook/Exchange integration, then I'm out of my league.
>
>Malcolm

For better or for worst we are well down the path of Outlook/Exchange integration. Outlook is great for the users and power users but it's definitely proving to be a challenge from an automation standpoint. I've already given up on trying to supress the email warning in Outlook XP. Now I just want some stability!

I'm considering taking the code I presented in the first post and putting it in a seperate VFP EXE by itself and calling it through a shell execute in my host VFP app. That way if the email automation EXE and outlook get a death grip on each other the main app will not crash. But I do hate solutions that basically hide the primary problem.

I'm going to look into blat for another possible angle at this solution. Perhaps I can use Blat to send TWO emails. One to the customer and another that copies back to the user in a format that an Outlook rule can use to place the email in the sent items. That would also get rid of that frustrating 'warning' that MS throws up when automating outlook.

Thanks for the help!