Mayayana
2/26/2011 2:54:00 PM
>
Wow, looks very complete. But I am not sure whether my Provider does
support use of this. Thanks
>
Provider? You don't need to use VBS or an HTA.
It was just meant to be a sample of what you
need to do in terms of the IE object model. Using
the WB.Document is exactly
the same thing as using the Document object in
webpage scripting. The only difference is that
when you reference mshtml.tlb in VB you get
an object model that's strongly typed .... sort of.
For instance, a TABLE is not just an Object. It's
an HTMLTable.
I was assuming that you're working in VB with
a WB control. If this is something like ASP server
side then you should ask in an ASP group. If you
don't find what you want in terms of webpage code
then you can write to me if you like. (The email
address is in the download, but email must be
sent from a real email address. Webmail from
gmail, hotmail, facebook, yahoo, live.com is auto-
deleted from the server.) I do a lot with
the IE object model, HTML, CSS, etc. But my own
site is on Unix. What little I know about server-side
operations is limited to things like PHP includes. I
don't know anything about the ASP equivalent.
Also, if you're actually serving this page to any
browser from server-side then you'll need to test
the specific HTML. You might have to build the HTML
differently for different browsers because IE will
often render differently from other browsers. And
different versions of IE are incompatible. The closest
I've been able to come to a universal fit is to have
2 page versions: One for IE in quirks mode, and one
for all other browsers. I don't support non-quirks IE
at all. It would require a different page for every version
of IE.