>>>Is it me or this MAPI stuff is really annoying me?
>>>
>>>I've played with MAPI 2 years ago and found that is was not doing a good job. Since then, I've been using MailX and Mabry controls, which are good controls and standard to the Internet.
>>>
>>>Now, I am in a situation where an application for a client need to use Microsoft product and all I hear since I'm hear is MAPI, MAPI and MAPI. I tried again to use that control and it is still annoying me.
>>>
>>>First of all, is there any reason why there is, in the list of controls, one for session and one for message when we only need to use session? At least, this is what I saw when looking in the MAPI sample from the Files section. There is only one CREATEOBJECT() and it is the session one. Then, from that object, there is a reference to the message feature without having to create an object for the message.
>>>
>>>Secondaly, everytime I put the session and message controls on a form, I will get "OLE lDispath exception code 0 from MAPISession: Property is write-only" when I will try to click on one of those controls after having opened the form.
>>>
>>>Is there any better Microsoft control to handle Internet email instead of MAPI?
>>
>>Michel,
>>
>>I've mentioned the Crescent Internet Toolpak a couple of times in various threads. It comes with an Internet email control. This, however, isn't one of the controls that I've had a chance to play with (we use ccMail 6 and if you think MAPI is bad, try VIM). Anyway, as I've mentioned before, the controls I've worked with seem to do the job,
>
>> but support for VFP is non-existent. In other words, if you need support, better translate the problem into VB before contacting their support personnel.
>
>That is not true. I contacted MicroSoft twice about problems getting the MAPI controls going and they were VERY helpful. Right now, I have an executable at work that reads a text file downloaded from our website, processes registrations, and automatically emails the registrants a confirmation of registration. There are a couple of bugs in the control, but there are ways
around them. Call and ask and you will get help.

Are you willing to post that on the KB or perhaps E-mail steps and
code.