Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Need Help On VB ActiveX Control.

Status
Not open for further replies.

NeedVBHelp

Programmer
Mar 9, 2000
15
US
Let me exlain my problem a little more clearly.<br>
<br>
I have an activeX control that runs on the client machine and is accessed by a web application that my agency is developing. <br>
<br>
I have created a web cab file that is automatically downloaded from the web server running the program. The asp page it accesses references the current code base so that the current version will be installed. <br>
<br>
The control is being installed and updated on the client each time the page is accessed, but when the control loads that is when I get the Error 430, &quot;Class does not support Automation or does not support expected interface&quot;. <br>
<br>
I had created the cab file and compiled the component on an NT 4.0 machine. The OCX worked fine on the web server (NT 4.0) and a WIN 98 client that accessed the page, but the Win 95 client had the problem.<br>
<br>
I tried to recompile the OCX and recreate the cab on a Win 95 machine and I got the same problem. Each time I recompiled the cab I selected to maintain binary compatibility. I tried to create an .exe to install the OCX on the client - same problem.<br>
<br>
I tried to create a new OCX and cab file for a totally different install and I got the same error on the client. Because it worked on the Win 98 machine I had the Win 95 machine upgraded to Win 98 and that didn't work either.<br>
<br>
I even compiled the OCX to not use binary compatiblity and that didn't work.<br>
<br>
I have tried everything I can think of - PLEASE HELP!!
 
Does your activex control rely on a standard windows dll?<br>
<br>
I have had problems (admittedly not with web stuff) running programs on a machine it was not compiled on - usually because of some system dll/ocx that differed between the O/S's<br>
<br>
I'm guessing really.<br>
<br>
Mike<br>
<p>Mike Lacey<br><a href=mailto:Mike_Lacey@Cargill.Com>Mike_Lacey@Cargill.Com</a><br><a href= Cargill's Corporate Web Site</a><br>
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top