A
adalton
HI!
(I originally posted this in the wrong group...)
I have been looking for an easy to use control (or code) that works in VB2003 and VB2005
and will allow me to program an automated ftp process into my application.
I have been 'googleing' and have not found any that are under $200.. Most are expecting
you to use a full client but I do not need (or want) thet.
Does anyone know of an inexpensive component that I could purchase?
The Ftp portion of the program is just a small part of the overall program and I just want to
focus more attention to the main application rather than this module.
I need an ftp component with easy to use calls. Sonething like:
ftp.connect("ftp.websiteName.com")
ftp.LoginInfo("username","Password")
ftp.PortNumber(21)
msgbox(ftp.lastresponse) 'show last response as "250 connected" or whatever the codes are.
This is pretty much what I am looking for... The Xceed components are way too complex for
what I want to do, and very expensive to boot. I've tried to understand the Microsoft KB article
but to no avail.
A. Dalton
(I originally posted this in the wrong group...)
I have been looking for an easy to use control (or code) that works in VB2003 and VB2005
and will allow me to program an automated ftp process into my application.
I have been 'googleing' and have not found any that are under $200.. Most are expecting
you to use a full client but I do not need (or want) thet.
Does anyone know of an inexpensive component that I could purchase?
The Ftp portion of the program is just a small part of the overall program and I just want to
focus more attention to the main application rather than this module.
I need an ftp component with easy to use calls. Sonething like:
ftp.connect("ftp.websiteName.com")
ftp.LoginInfo("username","Password")
ftp.PortNumber(21)
msgbox(ftp.lastresponse) 'show last response as "250 connected" or whatever the codes are.
This is pretty much what I am looking for... The Xceed components are way too complex for
what I want to do, and very expensive to boot. I've tried to understand the Microsoft KB article
but to no avail.
A. Dalton