I am going this route because I need to end up with a query on my contact history table that excludes any contacts made in the last 30 days for follow up.  so I need to determine on a contact by contact basis the last date anthing was done and exclude those less than 30 days old from my list.  I want to end up displaying in Excel all those others (and thier history) so she can easily go down the line and call and write notes

Use DAO instead of ADO. Much better between Office apps, and you won't need a reference to ADO.

I've actually got a TechHelp video on this topic on my list - how to get values from an Access database and put them into an Excel sheet. Stay tuned. I'll bump it up the list for you. Much easier to explain in a video.

Good idea, the Microsoft learning docs mention DAO expressly, but I was reluctant to use that thinking they werre old.

It's a funny story. DAO used to be the standard back in the 90s / early 2000s. But then MS switched everything to ADO which is more compatible with online databases, but lacks a lot of functionality that you can do between just Office apps, so then they switched back to DAO. Super pain in the ass at the time. But now, I recommend if you're just using Office apps, stick with DAO. It's much more flexible. Use ADO for talking to anything online.

I have been using DAO and it is working fine, until now.  I have two subs, one pulls all the contact history from a query.  This ran beautiflly many many times.  i then wrote another sub which takes new follow up data from the user and inserts it into contact history table.  Thjs also runs fine.

The problem is when I went back to check out the original sub it won't run and I get an error message.  I rebooted my machine , succeeded in running the second update query, this time closing the currentdb connection and the first sub still gives me that error.  I have submitte the code.

Too Few Parameters

Gentlemen,  never mind, the problem was the underlying query being called.  Everyhting is good