Object library references for Excel VBA to access Access database

Anonymous
2014-12-04T18:59:02+00:00

According to a VBA course I took, to write VBA in Excel to access an Access database, I need to set a reference to "special object libraries".  The course notes say that DAO is for Access 97 to 2003, while ADO is for 2000 to 2007.  Since I use Office 2010, I assume that I use ADO.  At that point, there isn't much more about this particular detail.  Even if there was, that course was taken some time ago, and I'm not sure if it would applyt to my current use of Office 2010 in a 64-bit Windows 7 environment.

I attached a subset of the list of choices when I go to Tools->References from the Excel VBA editor.  Can a kind soul please say what are the proper things to check off?  The subset only includes likely suspects (as assessed by my rather newbie self), so it's possible that the required items aren't in this list.

Thank you.

Microsoft 365 and Office | Install, redeem, activate | For home | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

2 answers

Sort by: Most helpful
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  2. Anonymous
    2014-12-08T18:23:54+00:00

    Thank you, Andreas.  That was very helpful.  I did indeed run into the information about late binding.  Given the diverse environments in which this code may have to run, I decided to use late binding by default.  I don't do my major coding in the VBA editor, so the loss of intellisense is problematic but acceptable.  I can back-annotate the changes to the existing code in order to use conditional defines when I have a chance.  The need to define global constants withe late binding is problematic, but again, not a show stopper.

    Was this answer helpful?

    0 comments No comments