>I think so. I need to perform these connections either on the fly if a certain error is encountered when a method is running. Or with the FTP thing I'm looking to create a software utility to run at night that goes out across the country, via our own private enterprise network, to 7 seven different Unix boxes and transfers files to my database server.

I think the FTP might do the trick. I don't see a need for socket here.

>Wow... that is alot of power. But my data warehousing app isnt a web application.

This is not related.

>Eventually I'll probably do a remote user interface for Intranet use. (or I'll sub that job out while I learn SQL Server) But for now I'm just designing a monster network application for my MIS Department to use. Thank you, you really helped me understand this whole socket deal.

Ok, good luck.