Hi!

Outlook produces HTML messages, not RTF. And also it splits message, so conten-type for it is multipart for main header, and special for each part.

You can see all headers of message in Outlook by opening message, then select in menu "View/Options...". Then look at "Internet Headers" field.

Yes, I had experiense with MS DHTML control. It is very cool. I downloaded SDK from MS site and started to make a sample VFP form for editing DHTML. Unfortunately, there is no ready sample, and making all toolbars with all tool buttons and functionality for them in VFP was quite a mess and I left this dirty work (because I tried it just for fun).

>Hi Vlad!,
>
>You are right, but I'm doing it correctly, I checked the header fields and they are being filled and are correct.
>The problem is Outlook.
>Interestingly, when creating a RTF message from Outlook, it does not fill those headers!; at least I can't see them.
>I'm going to try going against logic and NOT fill the content type fields. Perhaps it will work :(
>
>Any experience with the M$ DHTML.ocx?
>
>
>>Hi!
>>
>>Email message have a set of textual header fields. There is also a Content Type field. When sending email, your email sending tool should allow change this field value to be able to send RTF or HTML emails. For plain text (default value of this field) it is "text/plain". For RTF you require to set this field value (when sending message) to "text/RTF".
>>
>>HTH.
>>
>>>Hi all,
>>>
>>>I'm revamping and old application and adding some new capacities to it, now I'm working on email. Not all of our users have Outlook, in consequence I'm using EasyMail OCX and it works very well.
>>>As EasyMail is able of sending RTF and HTML messages, I started and finished on Friday a form to allow my users composing RTF messages (I used some code from Solution.app), add attachments, etc.. Everything was great until testing and notice that Outlook does not "recognize" the RTF output from the Rich Text Control. There is no errors in my code, Words renders the OCX's RTF output very well. It is Outlook than apparently has its own "standard".
>>>
>>>Have somebody here encountered and solved this problem? Or, do you know where to find what is
>>>different betw the RTF OCX output and the RTF Outlook recognizes? I don't want to waste one day of work. :)
>>>
>>>Well, as RTF is not really standard, time to work in a HTML composer form, I found a DHTML Editing OCX (DHTMLEd.ocx) SDK, it contains a nice form in VB that looks easy to translate to VFP and I'm going to start doing it right now.
>>>Has somebody worked with DHTMLEd.ocx before? Any input is welcome.
>>>
>>>TIA,
>>>
>>>Max