×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

ActiveX Dll Error 430: Object does not support automation

ActiveX Dll Error 430: Object does not support automation

ActiveX Dll Error 430: Object does not support automation

(OP)
Has anyone had any experience of the following error:

VB 6.0, NT 4,SP4

A data access project (Standard EXE) using ADO 2.1. with a reference to an ActiveX DLL.

When the project is run in the IDE or as compiled EXE and DLL on the development machine, everything runs perfectly.

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:

Run time error '430': Class does not support Automation or does not support expected interface.

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

TIA

Andrew

RE: ActiveX Dll Error 430: Object does not support automation

I have had problems in the past compiling an EXE on an NT 4 machine and then deploying it on a 95 machine. Strange bugs popping up in seemingly unrelated modules. I have found that re-compiling the EXE on a 95 machine usually fixes it.

Hope that helps! (BTW, when I spoke with an MS Cust. Service Rep, they denied strenuously that I should have this problem moving between their OSs, so I'm not surprised you found no documentation on it.)

RE: ActiveX Dll Error 430: Object does not support automation

(OP)
Thanks for the reply.

In this instance it turned out to be the fact the the default interface for ADO appears to be 2.0 not 2.1. Therefore if you reference 2.1 in the project and use the Package and Deployment wizard (that packages the default 2.0), there is an obvious mismatch once deployment takes place. No problem if 2.1 is installed on the destination client, but behaves as per original post otherwise.

Andrew

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login


Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close