none
Access 2013 mail merge RRS feed

  • Question

  • I have an application in Access 2013, as a .accdb,  which is implemented at a client's site as .accde's. The remainder of my Office suite is 2010.

    The application includes some mailmerges controlled through VBA code. These have worked fine for some time but since some of the user's PCs have upgraded Word they no longer work. Is this related to References?  I have Word 14.0 object library. Is a later one needed and if so how do I get it?

    Thursday, July 26, 2018 2:11 PM

All replies

  • Hi,

    What does "no longer work" means? An app with a 14.0 reference should work fine on a computer with a 15.0 reference. However, it's not the same the other way around.

    To avoid library reference problems, you could consider converting your code to use "late" binding.

    Just my 2 cents...

    Thursday, July 26, 2018 2:49 PM
  • Many thanks for that. I have not come across the concept of early and late binding and will look into it.
    Thursday, July 26, 2018 3:26 PM
  • Hi Bob,

    You're welcome. Here are a couple of links you might find a little helpful.

    Using early binding and late binding in Automation

    and

    Early and Late Binding (Visual Basic)

    Good luck!


    • Edited by .theDBguy Thursday, July 26, 2018 3:55 PM
    • Proposed as answer by Terry Xu - MSFT Monday, July 30, 2018 9:55 AM
    Thursday, July 26, 2018 3:55 PM
  • Many thanks again for your help.
    Friday, July 27, 2018 8:54 AM
  • Hello BobKeightley,

    Has your original issue been resolved? If it has, I would suggest you mark the helpful reply as answer or provide your solution and mark as answer to close this thread. If not, please feel free to let us know your current issue.

    Best Regards,

    Terry


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, July 30, 2018 9:56 AM