I think the activeX we use is the one "not safe for scripting", because we don't do any scripting with it. But nevertheless it is incredibly useful as a WYWISYG editor that lets you work with HTML behind the scenes. Particularly useful is the way it gives you a hook to the DOM, which you can then traverse to enable a multitude of helpful HTML-processing functions.

>It does work. However, there are 2 different DHTML controls. One is labelled "safe for scripting", and if i remember correctly the download available for Vista is not the "safe" one. So if you use the "safe" one in your app, the one available for download doesnt help. I recall that being the case, but make sure you verify that.
>
>If you find an example of using the IE control (per Rick's reply) that includes highlighting, fonts, colors, URLs, ... please post here.
>
>
>>Bad news and good news:
>>http://msdn2.microsoft.com/en-us/library/aa663363.aspx
>>
>>We have an app that makes extensive of the DTHMLedit control. According to the article, you can download an MSI only for Vista that will install the modules to restore legacy functionality, so that things will work as before in Vista (at least, that's what the article promises).
>>
>>This is quite a change, nevertheless, because including and ever since IE5, DHTMLedit came along with the browser. No installation / intervention was necessary. It was just there. Now, any app running on a Vista system that trieds to instantiate the DHTMLedit control will encounter failure unless the MSI has been installed.
>>
>>I was just wondering if anybody else has verified that in fact the Vista version of DHTMLedit (once installed) does in fact work with VFP.
>>
>>Thanks very much.