Deploying Interop DAO Errors

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Paul Engel
    #1

    Deploying Interop DAO Errors

    I have a VB 2005 program that must use DAO. I have it running on my system
    using Interop. When I deploy it, I get the following message on the local
    PC:

    System.Runtime. InteropServices .COMException (0x80040112): Creating an
    instance of the COM component with CLSID
    {00000010-0000-0010-8000-00AA006D2EA4} from the IClassFactory failed due to
    the following error: 80040112.



    I have done some research on this, and the postings I see suggest installing
    MDAC 2.8 to solve this problem. Trouble is, the PC is WinXP Pro, and when I
    attempt the MDAC 2.8 install, of course, it lets me know that MDAC is not
    necessary since it's functionality is inlcuded in XP.



    Does anyone know another work-around for this error?


    Tags: None
    • Cor Ligthert [MVP]
      #2
      Re: Deploying Interop DAO Errors

      Paul,

      You know that there is a newsgroup
      microsoft.publi c.dotnet.langua ges.vb.data
      Bill Vaughn is active there, I am sure you can get your one of your best
      answer there.,

      Cor

      "Paul Engel" <paul.engel@veb ridge.comschree f in bericht
      news:OvOoYdzwHH A.1852@TK2MSFTN GP04.phx.gbl...
      >I have a VB 2005 program that must use DAO. I have it running on my system
      >using Interop. When I deploy it, I get the following message on the local
      >PC:
      >
      System.Runtime. InteropServices .COMException (0x80040112): Creating an
      instance of the COM component with CLSID
      {00000010-0000-0010-8000-00AA006D2EA4} from the IClassFactory failed due
      to the following error: 80040112.
      >
      >
      >
      I have done some research on this, and the postings I see suggest
      installing MDAC 2.8 to solve this problem. Trouble is, the PC is WinXP
      Pro, and when I attempt the MDAC 2.8 install, of course, it lets me know
      that MDAC is not necessary since it's functionality is inlcuded in XP.
      >
      >
      >
      Does anyone know another work-around for this error?
      >
      >

        Comment

        • Paul Engel
          #3
          Re: Deploying Interop DAO Errors

          Thanks. I'll give it a try.

          "Cor Ligthert [MVP]" <notmyfirstname @planet.nlwrote in message
          news:O%23kr1Q3w HHA.484@TK2MSFT NGP06.phx.gbl.. .
          Paul,
          >
          You know that there is a newsgroup
          microsoft.publi c.dotnet.langua ges.vb.data
          Bill Vaughn is active there, I am sure you can get your one of your best
          answer there.,
          >
          Cor
          >
          "Paul Engel" <paul.engel@veb ridge.comschree f in bericht
          news:OvOoYdzwHH A.1852@TK2MSFTN GP04.phx.gbl...
          >>I have a VB 2005 program that must use DAO. I have it running on my system
          >>using Interop. When I deploy it, I get the following message on the local
          >>PC:
          >>
          >System.Runtime .InteropService s.COMException (0x80040112): Creating an
          >instance of the COM component with CLSID
          >{00000010-0000-0010-8000-00AA006D2EA4} from the IClassFactory failed due
          >to the following error: 80040112.
          >>
          >>
          >>
          >I have done some research on this, and the postings I see suggest
          >installing MDAC 2.8 to solve this problem. Trouble is, the PC is WinXP
          >Pro, and when I attempt the MDAC 2.8 install, of course, it lets me know
          >that MDAC is not necessary since it's functionality is inlcuded in XP.
          >>
          >>
          >>
          >Does anyone know another work-around for this error?
          >>
          >>
          >
          >

            Comment

            Previous template Next
            Working...