dcsimg
Results 1 to 8 of 8
  1. #1

    Thread Starter
    Lively Member
    Join Date
    Dec 2005
    Location
    Birmingham, England.
    Posts
    115

    Resolved [RESOLVED] ADO problem on Windows 7 due to missing OCX

    Hi,

    I have a VB6 app that uses ADO db connections to a MS Access db that works fine on XP and Vista. I am trying to install on Windows 7 machine. I keep getting an error

    msadodc.ocx is not registered or is missing when i hit the first ADO connect. I have run the same files on the Windows 7 machine as i have on the XP machines like .net framework install, madc_typ.exe to install all the runtimes.

    I have tried to use regsvr32 msadodc.ocx but it does not register the .ocx file.

    Any help appreciated.

    Thanks.

  2. #2

    Thread Starter
    Lively Member
    Join Date
    Dec 2005
    Location
    Birmingham, England.
    Posts
    115

    Re: ADO problem on Windows 7 due to missing OCX

    Just to add, I had a similar issue on Windows Vista about 6 months ago which was resolved when i manually registered this .ocx

    is there a new version of this file specifically for Windows 7?

  3. #3
    Frenzied Member
    Join Date
    Mar 2008
    Posts
    1,137

    Re: ADO problem on Windows 7 due to missing OCX


  4. #4
    New Member
    Join Date
    Jan 2012
    Posts
    7

    Re: ADO problem on Windows 7 due to missing OCX

    install your application run as administrator.

    or try
    Use Microsoft ActiveX Data Objects 6.0 BackCompat


    http://support.microsoft.com/kb/2517589

  5. #5
    PowerPoster
    Join Date
    Feb 2006
    Posts
    18,857

    Re: ADO problem on Windows 7 due to missing OCX

    No, this isn't an ADO issue at all and the "back compat" typelib doesn't apply.

    You have failed to properly deploy the ADODC, that's all. Just use the PDW to create a setup package and you won't have these woes. Manually registering these components is a sign you are doing things wrong. The same thing would be seen on a clean XP system.

    MDAC_TYP has not applied to most systems since Win2K SP3 or so, and the ADODC isn't an MDAC component anyway but a VB6 control you are required to deploy. .Net's class libraries don't apply at all.

  6. #6

    Thread Starter
    Lively Member
    Join Date
    Dec 2005
    Location
    Birmingham, England.
    Posts
    115

    Re: ADO problem on Windows 7 due to missing OCX

    ok will try the PDW tonight and update the post. thanks.

  7. #7

    Thread Starter
    Lively Member
    Join Date
    Dec 2005
    Location
    Birmingham, England.
    Posts
    115

    Re: [RESOLVED] ADO problem on Windows 7 due to missing OCX

    PDW resolved the issue - thanks Dilettante

  8. #8
    PowerPoster
    Join Date
    Feb 2006
    Posts
    18,857

    Re: [RESOLVED] ADO problem on Windows 7 due to missing OCX

    Whew!

    Glad to hear it!

Posting Permissions

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



Featured


Click Here to Expand Forum to Full Width


×
We have made updates to our Privacy Policy to reflect the implementation of the General Data Protection Regulation.