Has anyone had any experience of the following error:<br>
<br>
VB 6.0, NT 4,SP4<br>
<br>
A data access project (Standard EXE) using ADO 2.1. with a reference to an ActiveX DLL.<br>
<br>
When the project is run in the IDE or as compiled EXE and DLL on the development machine, everything runs perfectly.<br>
<br>
WHen the application is deployed to another workstation (w95 in this case), the EXE runs and at the point of calling the DLL gives the error:<br>
<br>
Run time error '430': Class does not support Automation or does not support expected interface.<br>
<br>
I have searched the knowledge base and as far as I can tell, I am fine according to the MS articles (i.e. Dll project created cleanly and has never been an EXE project etc).<br>
<br>
TIA<br>
<br>
Andrew<br>
<br>
VB 6.0, NT 4,SP4<br>
<br>
A data access project (Standard EXE) using ADO 2.1. with a reference to an ActiveX DLL.<br>
<br>
When the project is run in the IDE or as compiled EXE and DLL on the development machine, everything runs perfectly.<br>
<br>
WHen the application is deployed to another workstation (w95 in this case), the EXE runs and at the point of calling the DLL gives the error:<br>
<br>
Run time error '430': Class does not support Automation or does not support expected interface.<br>
<br>
I have searched the knowledge base and as far as I can tell, I am fine according to the MS articles (i.e. Dll project created cleanly and has never been an EXE project etc).<br>
<br>
TIA<br>
<br>
Andrew<br>