Jay,

You're right about your comment concerning VFP interface controls being designed for data input - not rich interactive surfaces. With that said, the VFP controls are still a lot better than the simple input controls used on most browser forms.

I like your idea about the list box that tracks the data entry efforts in an edit control. I'm going to have to think on that idea for a bit.

Thanks again for your help and ideas!
Malcolm


>Malcolm,
>
>As we're realizing, the VFP interface controls tend to work for data input, and don't have a rich interactive surface as we've grown to expect in browsers, etc.
>
>I have a couple of ideas:
>
>1. If it's possible to use automation and embed an instance of Word XP in your form to replace edit controls, you could use the smart tag feature as well as allow the user to edit. Of course, there's overhead, and the requirement that folks be current...
>
>2. Alternatively, I'd consider the following. Allow the user to edit in the edit box. Have a list box associated with it, which contains all the special phrases in the edit box, and the 2nd column with the explanation. You can set the tool tip to access the 2nd column and display that when the user selects a specific item. A bit kludgy, but perhaps that will provide some other insight.
>
> Best wishes!
>
> Jay
>
>
>
>>I hear what you're saying about considering a web browser control. This would certainly make sense if I was displaying only read-only content. But IMHO a web browser control is inherently a readonly control as opposed to an edit box or RTF control which I tend to think of as data entry controls. Another drawback to the web browser control is the requirement for users' to have a minimal version of IE installed in order for the web browser control to work. Easier said than done!