Results 1 to 8 of 8

Thread: error ... please help

  1. #1

    Thread Starter
    Addicted Member smh's Avatar
    Join Date
    Oct 2000
    Location
    South Dakota, USA
    Posts
    249
    Other programmers are testing my project today. No one had problems with running the project except one person. When they try to load the project, they get the following error:


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


    I have read all the help articles I can find, but none of them make any sense to me.

    Does anyone know how to fix this?
    Normal is boring...

    smh

  2. #2
    Member
    Join Date
    Jan 2001
    Location
    Washington, USA
    Posts
    61

    I think ...

    ... it sounds like they didn't get all of your code, or are running it improperly.

    What is the code you are running?

    Does it activate another ActiveX that you created?

    Does it use the correct version?

    What is the project you are running, and where does the error activate?

    Samwise Galenorn
    [email protected]

  3. #3
    Fanatic Member
    Join Date
    Aug 2000
    Posts
    736
    If you are using ODBC, you might need to insure the correct version is installed on the client machine.

    I got error 430 when I was developing using ADO 2.5, but one of my client machines was running ADO 2.1.

  4. #4

    Thread Starter
    Addicted Member smh's Avatar
    Join Date
    Oct 2000
    Location
    South Dakota, USA
    Posts
    249
    How do I find out the ado version is running on their computer? I am running 2.5.
    Normal is boring...

    smh

  5. #5

    Thread Starter
    Addicted Member smh's Avatar
    Join Date
    Oct 2000
    Location
    South Dakota, USA
    Posts
    249
    OK, never mind my last question because I have since then figured out that the problem is that I have ADO 2.5 and they have ADO 2.1. I have 2 questions:

    Can I change the version on their computer when the program is installed?

    If so, how?
    Normal is boring...

    smh

  6. #6
    Fanatic Member
    Join Date
    Aug 2000
    Posts
    736
    One option would be to choose the ADO 2.1 reference when you create your executable on the development PC.

  7. #7
    _______ HeSaidJoe's Avatar
    Join Date
    Jun 1999
    Location
    Canada
    Posts
    3,946

    <?>

    I haven't tried this but if you include the ADO 2.5 in your Package and Deployment would the install add it to the user's pc...overwriting the older version.

    AddFile.
    "A myth is not the succession of individual images,
    but an integerated meaningful entity,
    reflecting a distinct aspect of the real world."

    ___ Adolf Jensen

  8. #8
    Fanatic Member
    Join Date
    Aug 2000
    Posts
    736
    That is the other option. Either make a Setup package, or copy the mdac_typ.exe from the development PC to the client PC and run it to update the MDAC.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width