Wow depending on what you are doing in each of those, that looks like a ton of overhead. Also depends on how often you are running that and what event you are using to try and get that done.

We need to know more, including screenshots to be able to help you out.

Meanwhile you might want to take a look at the Dashboards video to possibly gain some tips on what you are trying to do.

I thought i was being clever and adding code to all the forms where you make changes on their onopen event i put a dcm. close form and closed all the forms that displayed changing data. It works great for just me using the database but it occurred to me that as there will be multiple users this could potentially close a form someone is working on?

Thanks Scott, will take a look at the video. Why the wow, is this not a practicable solution? The code was in some close forms command buttons/unload events/close events - not all on one form - was trying to understand why the code wasn't consistent when running. Its probably in at least 6-8 forms where you make changes and updates to the DB tables. The code runs every time you close a form after making changes which can be fairly frequently throughout the day. I'll include a couple of screenshots of the dashboards.

Hi Marc, remove the On Error statement and see if any run-time error(s) prevented any of the form from running Requery.

Marc -
The "WOW" was because I was under the impression that you ran all 9 requeries each time.  For instance each time you went to the Home Form.  
For one person might not be to bad.  But, when you start splitting the db and have multiple users, pulling data over a network, how much data you are working with, etc, depending what those queries are doing, you might be adding substantial processing to your db and causing things to slow very quickly.

You could make the forms modal and requery the calling form in the on close event