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.

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. :)

>>The easiest way to build ftp client is by using MSWINSOCK control. Get the RFC's from ftp://ds.internic.net/rfc and get started with coding your own client. The RFC lists the standard commands found on most FTP servers. Among the standard FTP servers are WU.FTPD from washington university. This is the most used ftp server in the world.
>
>Do you suggest to use socket protocol to redo a FTP protocol instead of using a FTP OCX?