More explicityly.
I assume that the best way to search for a file name, programatically, from within Vee, on the root directory is to use some default ActiveX control. First is this true?
Second if it is true (i.e. use ActiveX) then which ActiveX automation add-in must I include?
Many Thanks
Tom Silchia
Agilent Technologies, Inc.
Tom_silchia@agilent.com
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to
"owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
I assume that the best way to search for a file name, programatically, from within Vee, on the root directory is to use some default ActiveX control. First is this true?
Second if it is true (i.e. use ActiveX) then which ActiveX automation add-in must I include?
Many Thanks
Tom Silchia
Agilent Technologies, Inc.
Tom_silchia@agilent.com
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to
"owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
</span></span>
Simplicity itself. Follow directions from Microsoft - those other people are
talking giberish. Create autorun.ini in the root, add an [autorun] section
header and put open=veerun.exe myprog.vxe in there.
A real menu is not difficult at all to create, and you already know that
everybody has IE. Launching programs is child's play from VBS or JS, though
most installations have those IE options turned off (or at least they're set
to prompt). You can get around that by writing a simple VB menu program.
Autorun that, and launch from there.
It can look as impressive as you want, but please consult a graphic designer.
It takes skill to make something that doesn't look like ... ah, dookie but
almost everybody can tell excellence from - dookie.
> One little disadvantage of running
> of a CD (I think) is if the program
> needs some ActiveX or other of that
> fancy stuff.
Advantage API: no libraries necessary, other than those that are already
there. Most of the Automation libraries are nothing more than lightweight
wrappers around API functions. As we saw just the other day even callback
functions can be implemented with VEE.
> Or maybe there will be a way to
> "automatically" register the ActiveX
> temporarily and unregister after the
> demo.
No problem at all. For any ProgID you do need, attempt to open the key
HKCR<ProgID> (like SubCls.Subclass for instance). If the open fails then
extract the binary from a container, write it and register it (search for
WriteAndReg). Always unregister and delete any custom libraries. Similar
techniques work for .NET.
The entire process can be carried out silently or you can use regular
installers. I feel that silent is a far better option. People want to insert a
CD and watch a demo. They don't want to be interrogated about where to install
what.
-SHAWN-
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to
"owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".