none
Run-time error 4601 when trying to open Word from Access RRS feed

  • Question

  • Office 2013 and Windows 10

    Hopefully I'm posting this question in the right place since the issue we are having involves Windows 10, Access & Office 2013 and VB.

    After upgrading few computers to Win10, users gets a "Run-time error 4601 Can't activate application" when they click on a button in Access DB that open/ export info to a Word document.  Its been working prior to the Win10 upgrade and it still works for users who are on Win7 & Win8.  As matter of fact, even thought Win10 users get the error, it still opens Word and exports the data.  It would be nice to figure out how to stop the error popup. Hoping someone has run into similar issue and know the fix.

    Thanks in advance.

     


    Roget Luo

    Saturday, June 11, 2016 12:23 AM

Answers

  • When computers were upgraded was Office also upgraded? If so, on the computers with the problem, open the VBA editor and then select menu item Tools -> References and ensure there are no references shown as missing. If any missing then note what they are and uncheck them and then find the new equivalent reference and check it. However, this does not get rid of the problem altogether and it can return when different version of Office are in use. To remove the problem completely the code needs to access other office applications needs to be written as late binding instead of early binding (Google to find out more about this type of coding.)

    If you can't fix then please post the section of code where the problem is occurring and identify the line that errors.


    Regards, OssieMac

    • Marked as answer by Roget Luo Friday, June 17, 2016 3:58 AM
    Saturday, June 11, 2016 3:57 AM

All replies

  • When computers were upgraded was Office also upgraded? If so, on the computers with the problem, open the VBA editor and then select menu item Tools -> References and ensure there are no references shown as missing. If any missing then note what they are and uncheck them and then find the new equivalent reference and check it. However, this does not get rid of the problem altogether and it can return when different version of Office are in use. To remove the problem completely the code needs to access other office applications needs to be written as late binding instead of early binding (Google to find out more about this type of coding.)

    If you can't fix then please post the section of code where the problem is occurring and identify the line that errors.


    Regards, OssieMac

    • Marked as answer by Roget Luo Friday, June 17, 2016 3:58 AM
    Saturday, June 11, 2016 3:57 AM
  • Turns out it was an issue with PDF add-in in Words.  Once I removed untick the PDF add-in, everything ran smoothly again.  Thanks for your help.

    Roget Luo

    Friday, June 17, 2016 3:58 AM