Need help on creating ActiveX control in VB 1

[NeedVBHelp]

Hello My name is Thai Vuong, created an ActuveX control using VB6, flatform: Winnt 4.0.<br>
When I post it on the server running Winnt, it work OK, but the client site that are using win 95/98, I have problem.<br>
Error 430, &quot;Class does not support Automation or does not support expected interface&quot;. <br>
What do I need to do to fix the error?<br>
THanks<br>
Thai

 

[DougP]

Which Active X control is it?<br>
What are you doing in the client when you get the error?<br>
What do you want to happen on the client side.<br>
Note:<br>
Most programs that run on a Server need to be &quot;Services&quot; not just programs. <p> DougP<br><a href=mailto: dposton@universal1.com> dposton@universal1.com</a><br><a href= > </a><br>

 

[Irfan24]

I will ask the same questions as DougP but with an addition<br>
Are u configuring DCOM98 at the server running under win9x?<br>
if not, this could be the problem. DCOM98.exe and DCOMcnfg.exe are included in VB 6 CD. Try it.

 

[NeedVBHelp]

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. 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!!