title: Difference between ADO and DAO
body: <p>This is not a question about which is better, but rather a question regarding why they differ functionally.  The problem I was running into has been handled, but I am curious as to why this behavior is happening.</p>
  
  <p>Background - using Excel vba to pull data from an Access database.  When user clicks a button, a recordset is pulled from Access, and it populates various data to the spreadsheet.  Then, another recordset is pulled from a different query to populate another part of the spreadsheet.</p>
  
  <p>What ADO does - ADO works great for my first recordset.  However, my second recordset goes to the query in Access, runs, and returns no rows.  If I run this query in Access, it does open up (after about 3 to 4 seconds).  This query has multiple joins, computed items, limits, and possibly Union queries (I tried it many different ways, with/without union,etc.).  I tried closing and reopening the ado connection.  I tried changing timeout values, and I even tested using an ADO command to run Make table queries for this data, and then pull from the table instead (this worked by the way, but is not the best-case, since the data changes continually, and I do not want to have to run the make table query everytime someone uses this tool).</p>
  
  <p>So, I changed the second data pull to DAO, and lo and behold, it works.  The first data pull is still ADO (which I generally prefer to use), but am now considering changing it to DAO, because I would rather have one data access method in the code.</p>
  
  <p>So, can someone explain to me why ADO will not pull the data in one case, but DAO will?  Again, this is purely for informational purposes.</p>