Hi Arto,

>Actually it was only an example to survey what you can do with the internet (or webbrowser) object.

It is no silver bullet, but I still think it is great to be able to automate IE.

>I'v tried couples of things (and followed some other threads about above) and found out that you can't access its full document object model (if you can, preventing popups should be easy).

Are you talking about cross-frame security here ? If so, there is an article in MSDN showing a way through COM - haven't tried it in "pure vfp" yet.

Also, there are not only popups started by "regular" HTML, there is also scripting to think of as well. Real "Filtering" would probably best be done before the downloaded content gets into MSHTML. The approach of "loading the URL into a file, cleaning it and then navigate2 to it" will only work on very few (simple) sites - AFAIK you'd have to write a pluggable protocol to get it to work for certain. But I believe, that this would be the case if you are programming in c++ or vb as well, this is "no fault" of VFP or WebBrowser.

>Also using it is more clumsy in VFP than VB (f.ex. event binding).
Yup. But believe me, it is faaaar better now than before! And I've tried my hand on IE4 and the interfaces of IE3, and very often left the fox for quick excursions into vb or sometimes c++. It's not so bad anymore...

>P.S. Hope someone can prove I'm wrong and show "How to".
specifics ?

my 0.02 EUR

thomas