The major problem with that is that while using a winsock control is very nice for text based protocols like TELNET, and the related ones like POP, SMPT, IRC, etc., it is not as easy to use for FTP, since the actual file is sent over a connection that is seperate to the commands one, and the file must be converted before or while sending to something that is usable on the computer you are working with (since FTP servers have one of many systems they use for files that don't really jive well with MS OS's). I have to agree with Lee about using the inet API for it, since that will automate much of the process, and still give you a great amount of both power and control.

>Hi,
>
>Well I've found that the Winsock is the only control that I like the most and I've now used it in every project that I made. It does a lot of work for me like SMTP, POP, FTP, HYLAFAX, TELNET and every other tcp protocol that comes to my mind. It's the best of the best controls in VB 5.
>
>Hitesh K. Soneji
>
>>>The only ftp OCX I've had experience with is the MS Internet Transfer Control, and it had some serious limitations. Prior to the VB SP2, it only worked with non case-sensitive servers (Can you believe that MS never tested it with FTP servers other than their own? :)), and when you request the download of a file, the function doesn't return until you have the whole file. No oportunity to incorporate a progress bar, or do ANYTHING while the xfer is going on.
>>
>>I agree. I always use 3rd party OCX because I need some which are standards. :)
>>
>>>My preference has been to use the Windows Internet (WinINet) API. It's very easy to use, and gives you a lot more control than the MS Internet Transfer control.. I plan to make a control to "wrap" the WinInet in an even easier to use control soon. :)
>>
>>Keep us inform.