That would be a great tool for someone to write that takes a list of your queries and figures out if they're used or not by other objects, but that would be a major undertaking, and I'm not building it. LOL

One way to do it is to check if a query returns an error, with the On Error statement.  See picture below.  A query with missing tables would return an error message like "Access cannot find table..."  Trap the error with On Error, and obtain the error number and description as shown below.  Sometimes errors may be unclear ("Incorrect syntax near ';'...").  But it's always useful to discover whatever errors there are in your queries.

Good idea, Kevin. That would be great for finding queries that are MISSING dependencies... but it's going to be a lot more difficult trying to figure out which queries don't have anyone dependent on them.

It's definitely a much tougher task, since you have to search everywhere (VBA modules, SQL statements in record sources, row sources, saved queries, etc.) to find any queries that are no longer referenced anywhere.  Also, even if a query isn't referenced now, it doesn't mean it won't be later.  I have queries that are dynamically switched among themselves, and they aren't all used at the same time.  If the reason to remove unused queries is to clean up the navigation pane, I may suggest letting it be.  In all my years using Access, I've never cleaned it up.  It's better to make the navigation pane more readable with naming conventions and such.  I use ALL CAPS to name queries that are more important than others so they stand out in the navigation pane, for instance.

Good idea.

What do I do is have one query called something like 'usedQuerirsDoNotDeleteQ'. And in this  query, I add all the queries that I use only inside of my VBA.  This way, when I am checking object, dependency for a given query, it will show up.

Richard do you have an actual tool?

Nope

I used to do something similar, though I used to take a query that I thought was no longer needed and just rename it to something like "OkayToDeleteLater20230601" or whatever. Then, I would wait a month or two. If I didn't hit any errors, then that would mean that the query could probably be safely deleted.

If you use a {VCS} tool you could easily search all the exported code and check references of names etc.
Start with some regex and build upon it.

Hello Alex.  How about a Tech help explaining VCS tools.

Theres already a couple of videos
VCS / GitHub
I'm looking to update to the latest version with the new Ribbon.