🚀 go-pugleaf

"Tom" <tom@nospam.net> wrote in message
news:454f924b$1@newsgroups.borland.com...

> if I change it so that when the button is clicked a thread is
> spawned and that thread makes the exact same call as above

You can't do that.  The Browser can only be accessed in the context of the
thread that created it.  You cannot access it across thread boundaries
(without manually marshalling the ActiveX interface, which can get ugly).

> IE6 and below function just fine.

I seriously doubt that.  IE's ActiveX objects are Apartment-threaded.
Creating them in the main thread, and then accessing them in a worker
thread, should be causing RPC_E_WRONG_THREAD errors to be reported on all
interface methods that are called.

> The alternate solution would be to use Indy to retrieve the source
> code (which is all I'm doing) but even after setting the UA some sites
> still know it's not a web browser and reject the request.

The UserAgent is the only application-specified identifer available.  If you
set Indy's UserAgent to match IE's, there is no other way a website can
differentiate between the two.


Gambit