DON'T USE THE DHTML CONTROL. It's obsolete, has lots of issues. Use the plain Web Browser control with ContentEditable.

That's what I use in Help Builder and its lots more stable than the DHTML control was (although you lose some features)...

+++ Rick ---

>Rick - thanks for the link. Hopefully i'll be able to swap out the webbrowser control for the dhtml control and have the existing formatting controls play nicely with the substitute.
>
>>http://www.west-wind.com/presentations/shellapi/shellapi.asp
>>
>>Basically any Html content element can be made editable by setting it's ContentEditable property.
>>
>>+++ Rick ---
>>
>>
>>>Rick - i just encountered this with some Vista users. Works great on XP machines though. I found that MSFT has a separate download for Vista users so they can install this 'retired' control. But apparently its not the 'safe for scripting' version that i had been using. I guess MSFT is providing the 'not safe' version ;) or there's even more versioning headaches with this.
>>>
>>>Do you have an example of using the Web Browser control that makes the content editable?
>>>
>>>
>>>>I would strongly advise against using this control. It's being removed for IE 7 and Vista... You can

> use the standard Web Browser control and make the content editable

> which provides most (but not all of hte functionality of the DHTML control).
>>>>
>>>>+++ Rick ---
>>>>
>>>>
>>>>>Trying the DHTML edit control. I have a form with a pageframe and have added the DHTML edit control to Page2. Running the form the control shows up as added to the form itself. When selecting Page 2 it shows as expected. How do I prevent it from showing up initially on the form?