Results 1 to 7 of 7

Thread: what could be?*** solution found

  1. #1

    Thread Starter
    New Member
    Join Date
    Sep 2002
    Location
    gurgaon
    Posts
    13

    Cool what could be?*** solution found

    hi pals,

    an application developed in vb 6

    when executed in another NT machine popped up with an error message like:
    RunTime error: 430

    class does not support automaiton or does not suport expected interface


    the applicaiton is a set up developed with package and tool deployment tool

    what is the reason for this error? and how to solve it

    thanx in advance

    this was my state
    Last edited by vetrikam; Oct 8th, 2002 at 11:11 PM.
    Keep Similing

  2. #2

    Thread Starter
    New Member
    Join Date
    Sep 2002
    Location
    gurgaon
    Posts
    13

    Thumbs up solution found

    hi pals ,

    above is the problem faced,

    when i tried to install the setup in a non vbmachine

    after a gr8 struggle v found the MDAC version was the problem


    it should have the version of 2.5 or higher



    so if future if u see the runtime error 430:


    there is a chance of MDAC ( behind the problem)


    keep working


    Keep Similing

  3. #3
    PowerPoster
    Join Date
    Aug 2000
    Location
    India
    Posts
    2,288
    Error 430 can occur whenever a COM object is not of the required version, especially when a conflict of CLSID & IID is present between different versions.

  4. #4

    Thread Starter
    New Member
    Join Date
    Sep 2002
    Location
    gurgaon
    Posts
    13

    that is also one reason

    can u help me out in realting them both

    so i could catch hold of the root of the problem


    does MDAC has anything to do with this CLIS ID And IID


    could u plz explain me in details


    thanx in advance
    Keep Similing

  5. #5
    PowerPoster
    Join Date
    Aug 2000
    Location
    India
    Posts
    2,288
    All COM Objects, no matter where and how they are created, use the CLSID & IID. Since MDAC also contains COM component(you use ADO through these components in VB), these play a major role.
    What happens is that whenever you compile a COM object, the whole prog gets a unique GUID, throuch which it is known to the OS and other applications. The classes are given CLSID and the interfaces are given IID. Now when you make some changes and your prog version number increases, the Prog GUID doesnot change( when the project is in Binary compatibility mode), but the CLSID and IID might change.
    If you have an exe that uses this prog, it will call the interfaces of your COM prog, which will be broken down by the OS into GUID, CLSID and IID. If there is a change in any of this variable, it becomes a problem. But if its a case of a higher version of your prog, the OS undertsands this and gives you a message box, depending upon the setting. The problem occurs when you have a lower version. The OS then refuses to run the exe because it might break the functionality of the exe.

  6. #6

    Thread Starter
    New Member
    Join Date
    Sep 2002
    Location
    gurgaon
    Posts
    13

    Lightbulb thanx a lot

    ur explanation was really good and useful

    thanx a lot


    Keep Similing

  7. #7
    PowerPoster
    Join Date
    Aug 2000
    Location
    India
    Posts
    2,288

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