Hi!

Well, I do not know how to avoid dialog boxed in Outlook when it is accessed through COM interface to do not lock the VFP application. Say, you solve this particular locking, but there might be other issues with Outlook and other dialog boxes that will lock application - you cannot predict everything. Try to ask in another, separate question so it will be more clear and you have a better chanse of answering. Let me know if no answer, I have a tremendous time-costly approach that will work for sure, but it uses external process (application).

However, I'm wondered why you use Outlook to access Exchange Server. If Exchange Serevr 5.5 or higher is used, you can use Collaboration Data Objects to access Exchange Server directly to send mail and check for mail, as will as work with Exchange erver folders. Well, if Outlook is used for regular work, mail will be moved to Outlok folders from Exchange Server, so it is depended on what you're going to do.

>It doesn't return an error...it just sets there in some type of wait mode.
>
>>Hi!
>>
>>You can use ON ERROR command to catch the error and see if it happens.
>>
>>>Does anyone know of anyway to check to see, if Outlook can send an e-mail?
>>>
>>>The following code runs:
>>>
>>>loOutlook = CREATEOBJECT('outlook.application')
>>>loNameSpace = loOutlook.GetNameSpace("MAPI")
>>>
>>>*This is where the code fails if the Exchange Server is down. Is there some check I can do before running this code?
>>>loRecipient = loNameSpace.CreateRecipient("Monte Murdock")
>>>
>>>Thank you,
>>>
>>>MOnTe