>I agree... hence the test for PASV in IE. Keep in mind I am only using the simple MSINET.OCX that should be able to use PASV mode.

Simple MSINET.OCX yes. Is why I suggested sending "PASV" through the execute method. when you are using MSINET for FTP, all what the execute method is doing, is sending commands directly to the FTP server. Such as "GET file1 file2". But if it works with the execute method, I do not know. MSDN doesn't list it as a valid FTP command. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/Inet98/html/vbmthinetexecutemethod.asp

But if you connect to a FTP server through FTP (from command window prompt), and than issue "QUOTE PASV", then passive mode is set if the server supports it. (QUOTE is to send a FTP command directly to the FTP server)

>Of course that object uses WININET.DLL, correct me if I am wrong, which is also used by IE. You will find that the version of WININET.DLL is the same (or close to the same) as IE itself. So... it is safe to say that if WININET.DLL goes to the registry for some settings, it will look to IE. Given that... we have our full circle which could pull the FTPPASV registry setting on behalf of MSINET.OCX. Of course this is still theory until I call my user at 15:00 Alberta time. At that time I will post my findings. In order for the process to fail, both tests must fail. If both are successful, then the test has not yet been proven or dis-proven. I need a user who can not currently submit their data through the application that is currently provided using MSINET.OCX

I wish you good luck and hope it works. Keep us posted.