>Thanks Rick. How does one instantiate an instance of a WYSIWYG HTML editor embedded in a VFP form by using just the IE DOM? I thought that the very purpose of the DHTMLedit activeX was to provide such functionality.

You just use the plain old Web browser control.

http://www.west-wind.com/presentations/shellapi/shellapi.asp

It's toward the bottom of this long article. You can turn designmode on on the entire document or make individual sections editable with element.ContentEditable.

+++ Rick ---

>
>>Yes it still works. However you should think about not using that control because in general it's very badly behaved. Most of the functionality provided by the control is available directly on the IE DOM via the ContentEditable attribute...
>>
>>+++ Rick ---
>>
>>>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.