> However if we make a "CAB package" with Package Wizard and install it on
> a twin production machine (where VB6 is NOT installed), we get

>     runtime error 429 ActiveX component can't create object

> We are not aware of which library can be missing, or of what part of our
> code requires ActiveX. We suspect the following snippet of code (before
> we introduced this, the program ran on the production machine just
> ocpying the single .exe file without doing a full install)

>    set fs = CreateObject("Scripting.FileSystemObject")
>    set dc = fs.Drives
>    loop on all elements of dc
>       to verify if there is a drive letter already connected with
>       a particular predefined (remote) share name
>    end loop

> After this is the share is already connected (when running from the
> operator account), program continues. If it is not connected (when it
> runs from administrator or from System via AT), it connects the share as
> drive Z using a "Shell" of the "net use" command.

> (1) is it possible to make the present program run on the target machine
>     copying there one or more libraries ? which ?

> (2) alternately, does a simpler method (without objects) exist to verify
>     a given share is already connected ?

> (3) does a native programmatic call exist to connect a drive,
>     instead of using Shell with a command like
>     net use z: \\host\share passw /user:host\name

> --
> ----------------------------------------------------------------------

> avoid unwanted spam. Any mail returning to this address will be rejected.
> Users can disclose their e-mail address in the article if they wish so.