Results 1 to 6 of 6
  1. #1
    SteveDurham is offline Novice
    Windows 7 64bit Access 2010 32bit
    Join Date
    Jul 2011
    Posts
    8

    Runtime 2010 ADODB Connection failure

    I have a routine which connects to MySQL database with ADODB connection. This worked in 2003 and 2007 runtime but throws a 430 error on 2010 runtime.



    Error 430: Class does not support Automation or does not support expected interface

    It works in full access 2010. Has there been a change of policy to restrict this type of connection in the 2010 runtime?

    If I use a linked ODBC table instead of ADODB the runtime fails with "Runtime Error". It still works in full access.

    Any ideas would be gratefully accepted.

  2. #2
    boblarson is offline --------
    Windows 7 64bit Access 2010 32bit
    Join Date
    Jun 2011
    Posts
    1,272
    It may have to do with the Windows 7 SP1 or Office 2010 SP1. ADO keys changed and so it has to be compiled on a machine with the applicable OS and Office installation. So in other words, if you compile on a machine with either of those SP1's then try to run it on say a Windows XP or Windows Vista machine that doesn't have Office 2010 SP1, then it will fail unless you compile on that machine.

    So does any of that apply to you?

  3. #3
    SteveDurham is offline Novice
    Windows 7 64bit Access 2010 32bit
    Join Date
    Jul 2011
    Posts
    8
    Hello Bob,

    Things are going from bad to worse. Runtime now tells me to delete the VBA Project because it cannot read it. This worked fine before! Both systems have the latest updates. One is Windows 7 and the Machine with runtime is XP. The runtime will run accdb but not accde.

  4. #4
    rpeare is offline VIP
    Windows XP Access 2003
    Join Date
    Jul 2011
    Posts
    5,442
    I'm assuming you're building an installation package with your run time version? Are you identifying all the references that are needed in your installation package? They do not automatically inherit the references that your original database has you have to specifically tell it which ones you want.

  5. #5
    boblarson is offline --------
    Windows 7 64bit Access 2010 32bit
    Join Date
    Jun 2011
    Posts
    1,272
    Quote Originally Posted by SteveDurham View Post
    Hello Bob,

    Things are going from bad to worse. Runtime now tells me to delete the VBA Project because it cannot read it. This worked fine before! Both systems have the latest updates. One is Windows 7 and the Machine with runtime is XP. The runtime will run accdb but not accde.
    The problem again is that you can't compile it on Windows 7 with SP1 and expect it to work in the runtime on XP. You will need to either use Windows 7 withOUT SP1 or you will need to use an Access installation on WinXP to compile for the runtime on XP.

  6. #6
    rpeare is offline VIP
    Windows XP Access 2003
    Join Date
    Jul 2011
    Posts
    5,442
    I feel like a fool I totally read over the windows 7. screw the details full speed ahead!

Please reply to this thread with any new information or opinions.

Similar Threads

  1. Replies: 7
    Last Post: 02-19-2012, 04:40 PM
  2. 2010 Runtime ADODB Connection Failure
    By SteveDurham in forum Access
    Replies: 2
    Last Post: 10-04-2011, 03:31 PM
  3. Hide Access 2010 runtime window
    By cevatyildiz in forum Programming
    Replies: 4
    Last Post: 03-28-2011, 07:28 AM
  4. access runtime for 2010
    By wthoffman in forum Access
    Replies: 1
    Last Post: 01-28-2011, 07:28 PM
  5. Duplicate record failure
    By bugchaser in forum Access
    Replies: 5
    Last Post: 05-21-2009, 08:38 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Other Forums: Microsoft Office Forums