Instead of using control, u can use Winsock APIs. Here u did not need any
interface...
for example,
Declare Function Connect Lib "wsock32.dll" Alias "connect" (ByVal s As Long,
addr As sockaddr, ByVal namelen As Long) As Long

Declare Function setsockopt Lib "wsock32.dll" (ByVal s As Long, ByVal Level
As Long, ByVal optname As Long, optval As Any, ByVal optlen As Long) As Long

U can use this things....if u know the Apis there are lots of winsock apis.

Shailesh
----- Original Message -----
From: "Jaco Lubbe" <WGJLUBBE@I...>
To: "professional vb" <pro_vb@p...>
Sent: Monday, November 26, 2001 3:29 PM
Subject: [pro_vb] Creating a instance of a ocx without a container(form)


Background:
I currently have a program running fine on a live server.
The problam with the program is that its a vb app. and when the machine
restrats the app. need to restart also. (Ok I know u can put an entry in the
registry - starting a app. but the app needs to start without a person
logging on)
So I have decided to make to app a services so that it dinamicaly restarts.
I'm dropping all GUI's to allow the app to function as a services.

Problem:
I'm using the winsock ocx control the control needs a container(form) to be
placed on. I've found a article on the web:
http://www.catalyst.com/support/tips/tip06.html witch explain how to
referance a control without a container.
But when I do this i loose my events for example: the connect event doesn't
fire, or I don't know how to referance it.

Anay suggestion will help
Thanks
Jaco Lubbe