Distributing MSINet

  • Thread starter Thread starter Database Whiz Consulting
  • Start date Start date
D

Database Whiz Consulting

Hey Everybody. Quick question. The native FTP client hangs on mput
periodcally with one of our clients, so I circumvented the problem by using
the MSINET.ocx control. Did not realize there would be a problem distributing
the control for use in another environment. After reading a bit, it seems I
had access to MSINET.ocx because my development machine has VB 6 installed on
it...which we never use. We are Access/SQL Server developers. Is there a way
to have MSINET.ocx work on a computer that doesn't have VB installed?

TIA,


Ray Jefferson
Database Whiz Consulting
Henderson, NV 89074
www.databasewhiz.com
 
You can try the following but I don't know if this will work for you or if
this will work on Vista or on a 64 bit machine. First, download msinet.cab
from:

http://activex.microsoft.com/controls/vb6/msinet.cab

After downloading extract (using WinRar for example or any good archive
program) the msinet.ocx file in "windows\system32" subfolder. To install
the file click on "Start" menu then click on "execute" and type "regsvr32
msinet.ocx" then hit "enter".

Make sure that you won't overwrite another version of msinet.ocx; so you
should check if this file already exist on the system and if it is, if this
is an older version or not (right click | Properties | Version tab).

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)


"Database Whiz Consulting"
 
Thanks Sylvain. Gave that a whirl. No go. Still getting Error 429: ActiveX
Component Cannot Create Object when I attempt to run the code on any machine
other than the development machine. I'm not sure why a control needs to be
licensed for distribution when its included in a development platform.

Thanks for your input though.

RJ
 
Are these machines with the same version of Windows? Did you take the
precaution of rebooting?

In this case, I've forgotten much of VB6 but probably that you could make a
very small project and set up the installation so that MsiNet.ocx will get
copied over. Check also for the possibility of an .INF file in the CAB
file, maybe this file should get copied to the system32 folder, too.

Finally, don't forget that both VB6 and the MsiNet.ocx control are old stuff
who are no longer supported by MS and shouldn't be used anymore wherever
possible.

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)


"Database Whiz Consulting"
 
Back
Top