I was looking at the ftp_class available in the files section. It has much of the WinInet functions already declared and a good chunk of the code already in place. The only declarations and procedures that it is lacking to do progress bars from what I have been able to find so far is the WinInet FtpGetFileSize and InternetReadFile functions. I think that my easiest path, then, would be to just add these two functions to ftp_class and then use InternetReadFile instead of FtpGetFile per the "HOWTO: Provide Download/Upload Progress Information when Using WinInet" Q234913 article that I found.

As you can see, I determined to have a progress bar <g>.

Thanks for the help.

Ed

>>I have a sinking feeling that this may be a lost cause.
>
>When I wrote the FTP utility for my company, I went through three controls (aka, 2 lost causes) and ended up with Marby's FTPx (which I dunno if it can use the progress bar or not, still something I gotta look at).
>
>I don't like how the Marby control works or how its supported. Plus I get more C5 errors than we can count. But for now its working...
>
>>Can you remember what avenues you were trying in order to grab the bytes that had come in at any given moment?
>
>I remember looking at the File Size on disk, which was usually 0 :-(
>
>>wwIPStuff is Marcus Egar's I believe.
>
>Thats Egger, and nope, wwIPStuff it "West-Wind IPSTuff" so its Rick Strahl's.
>
>>I have a feeling, however, that, as has been the case in the past, I will need to go to the Windows .dll for full functionality. In this case WinInet.dll. I < really > hate to go through this learning curve just for a progress bar.
>
>wwIPStuff's FTP subclass is a wrapper for that DLL, AFAIK. Haven't looked at the code in a while.