Please make a test to the following link :
http://groups.google.com/group/microsoft.public.fr.scripting/browse_thread/thread/845329491e365fc/a4e92bb90cb6c58f?lnk=st&q=+group%3A*.scripting+author%3AJean+-+JMST&rnum=12#a4e92bb90cb6c58f
Tsakalidis G. Evangelos
Serres / Greece
"mr_unreliable" <kindlyReplyToNewsgroup@notmail.com> wrote in message
news:eHKIHrkaHHA.1508@TK2MSFTNGP06.phx.gbl...
> From-time-to-time one sees quibbles posted in the
> wsh/vbs ng's, concerning various inconveniences and/or
> inadequacies of the "usual suspects" for dialogs, (e.g.,
> msgboxes, showModalDialog, showModelessDialog, etc).
>
> HTA's are generally considered more flexible than the above,
> but using an hta as a dialog is problematical, especially if
> you want to communicate with it. And so, enter the
> _"wshGetHTADocObject"_ utility, which does just that.
>
> The wshGetHTADocObject is an actX object, which does just
> what its name suggests. Once you have the doc object, then
> you can interface with the hta's elements and events. Granted,
> this is no different than interfacing with an instance if
> Internet Explorer, except that you don't have to deal with
> those petty annoyances involved with using IE as a dialog.
>
> The (c++) code for this actX object was provided by KB249232.
> However, I found something much more useful. Eduardo Anthony
> Morcillo, (a.k.a., "Edanmo") converted microsoft's c++ code
> into vb.net, and posted it here:
>
> http://www.mvps.org/emorcillo/en/code/inet/iedom.shtml
>
> I converted Edanmo's code from vb.net to vb5, so that I could
> compile it with microsoft's (free, but subsequently abandoned)
> vb5cce compiler.
>
> The attachment includes the source code, the compiled actX
> object (an ocx), an hta mini app plus an hta child dialog.
> It then occurs that one may also use hta's as dialogs from
> a normal script, so an example of that is included too.
>
> Reqirements: in order to use the ocx, you will have to register
> it. Also, you will need the vb5 runtimes (which I understand
> do not come with winVista, but are still available for
> downloading from msdn). Finally, you will need the oleacc.dll.
> This one is not very familiar, it comes with the "accessability"
> package. My own (ancient) system dates back to the last century,
> and it does have oleacc.dll already installed. But if your own
> system does not, then get out your trusty installation CD, and
> bring up your installer, and look for the "accessability" package.
>
> cheers, jw
>