Thanks this very helpful - it seems that the only limitation will be my imagination and work effort.

>Terry,
>
>Basically you drop a webbrowser control on a form and when you want to display content, you first navigate to a blank page to get a document object, then you can write whatever kind of content you want:
>

>this.oIE.Navigate2('about:blank')
>this.oIE.Document.Write('This can be any HTML or DHTML content you want')
>

>You can also wrap the webbrowser control in a VFP class and do some interesting things with it. At one time I had what I called a Fox browser. You could set a property on it to give a table name. Then, the Navigate2 method was overridden so that if the url started with fox:// instead of http://, it would look up part of the url in the table and render the contents of a memo field. I think it supported parameters as part of the url that it could feed to method calls or string replacements within the memo. It's been quite a while so my memory is not that crisp about the specifics, but it could handle internal (fox) and external (http) links this way. So, the web page that was stored either in a file or a memo field could have links that would actually trigger VFP code:
>

><a href="fox://object.method/parameter">Click Me!</a>
>

>Or something similar to that.
>
>HTH,
>Chad
>
>>Thanks!
>>Does that mean I could use DHTML and JS to manage the GUI and pass from the web browser control to VFP, the stuff I want VFP to handle?
>>
>>I'll have to check that out - have you seen any "demos" of this kind interface?