I have been working on developing an ActiveX control that will be used over an intranet. It uses the Internet Transfer Control, Winsock, SystemMonitor, and a few Database Connections (using Microsoft ActiveX Data Objects 2.6). If I load this control onto our server, and then access it from my computer (the computer I developed the control with) everything loads fine, and the control works as designed.

However, if I run it on a "clean" machine, one without VB, but still win2k (for SysMon), it doesn't work. The ASP page loads, and I get the security warning with my certificate, and I accept (it is marked safe for scripting and initialization also), it downloads the control, then nothing shows up, just a blank box with a little X in it. Right now, I'm referncing it like this, without a .cab:

<OBJECT ID="MasterControl"
CLASSID="CLSID061B421-0E10-404E-BA69-D8779430B4CC"
CODEBASE="MasterProject.ocx#version=2,0,0,18">
<PARAM NAME="_ExtentX" VALUE="6200">
<PARAM NAME="_ExtentY" VALUE="1150">
<PARAM NAME="SQLInfo" VALUE="db;UID=userid;PWD=;">
<PARAM NAME="SQLServerName" VALUE="sqlservername">
<PARAM NAME="WebServerName" VALUE="webservername">
</OBJECT>

Should I include the cab? As far as I understand, the only benefit of the cab is to decrease the download time, is this true? Or do I need it to include my references to winsock, ADODB, and so on?

Any help here would be much appreciated, thanks in advance,

Jacob