Unfortunately, Zane doesn't go out of his way to make his controls compliant with VFP as they tend to have multiple interfaces and VFP, of course, only supports one. I used to recommend Mabry a lot until this was pointed out to me on several occasions.


>I found this on another group and thought it might be of interest...
>

*****************************************************************
>I thought this might of interest, so posting here. (I'm not associated with these folks at all and am not using the product, BTW.)
>
>*******************************************************************
>Mabry's new Firewall/X OCX & COM objects make it easy to write custom
>firewall/proxy servers.  Firewall/X provides direct support for the standard
>proxy/firewall types: Telnet, FTP, Finger/Whois, Socks, Pipe, and HTTP.
>Additionally Firewall/X makes it easy to define your own firewall types.
>
>Using Firewall/X you can easily implement client access filters, redirect
>client's requests, log all traffic, and relay requests to 'hidden' hosts.
>Additionally you can easily provide for remote administration by implementing
>custom commands.  If you've ever been frustrated by the configuration problems
>and limitations of the various firewall/proxy servers on the market then you can
>easily create exactly what you need using, for instance, Visual Basic or VC++
>and Firewall/X.
>
>Like all of Mabry's new internet controls Firewall/X comes in both ActiveX
>Control and COM Object versions to make it easy for you to integrate it into
>nearly any Windows programming environment.
>
>See www.mabry.com for complete documentation and fully functional non
>time-limited demo control and sample programs.
>**************************************************************************