>I am not familiar with the internet transfer control (I have always used the API directly, or a tool like wwIPStuff).
>
>But here's an observation with my best assessment of the situation- the ITC handles the required WinInet calls for you- an FTP session involves several calls to WinInet functions, the most important of which in your case is INternetConnect. This is the call that gets you the handle on your FTP session, and this is the call that determines if Passive semantics are to be used throughout the session (INTERNET_FLAG_PASSIVE is the only valid constant for the dwFlag parameter). Since the ITC does all this connecting for you, unless this flag is exposed through the ITC interface (I don't think it is), you don't have access to it.
>
>If you need to be able to use a session with passive semantics, I would take a long hard look at using another control, or better yet look at the sample VFP code suggested to you in another message, and roll your FTP code yourself.

I think I'm heading that way. I hope I can scale to 100% API in little steps. Use WININET's IneternetConnect to toggle passive, and Let ITC with service state response and execute. RA's info really opened my eyes. Thanks.
Terry