What do you mean? You don't add a reference if you're using an API call. You just add in some code to your form or a module which allows you to access the API call as if it's a function in your application.<BR><BR>What tutorial are you trying to follow?<BR><BR>Craig.
Apologies. I'll try explain better. I have a DLL on my website. I want to be able to create a WInsock object and access its properties and methods. What reference do I need to check the box<BR>beside?<BR>I'm not looking for the Winsock component as my project is an activeX DLL, I need the library I must reference.
....unfortunately as you said - you can't use the Winsock component. You have to use the Winsock API, which isn't as easy as creating an object and using its properties and methods. Unfortunately.<BR><BR>Unless you look at third-party options, but they're expensive and you would have to distribute them with your system (www.aspin.com).<BR><BR>Have you tried searching around? http://www.google.com/search?hl=en&ie=UTF-8&oe=UTF-8&q=vb+winsock+api<BR>The first hit is "Winsock API with Visual Basic" (http://www.google.com/url?sa=U&start=1&q=http://www.vbip.com/winsock-api/default.asp&e=653). Following it are several other articles which look very useful, describing how to use the Win32 API to connect over the 'net.<BR><BR>Perhaps you should cast an eye over those tutorials and come back if you have a specific problem. However, if you haven't used the API before then you're in for some heavy reading. Try it out - it's not that hard, just different to instantiating an object and calling its methods...<BR><BR>Craig.