In my opinion, overkill

Simplicity is genius

I use query numbering in all my databases and also expand to forms and reports, but not tables.  Once the tables are created, then in most cases you will be done with this once the database ages.  But queries will continue as new reporting is needed.

So Q_0001_Name is my first query, Q_0002_Name is 2nd query, etc.  

Where this comes in handy is if you have nested queries that all build on each other.  You might run 5 queries to get the results that you want.  So, Q_0001_a_Name,Q_0001_b_Name, Q_0001_c, etc.

Since everything is listed alphabetically in the window, then you just have to find the query number from the record source of the object.

Works perfect.  As otherwise if you have 200 queries, you are on a mission to find all the ones that work with the underlying object, form, report, etc....

The bottom line is, if it works well for you, that's really all that matters. I don't understand your business or the database that you're building. So without a lot more information, I really can't give you any tips on how to make it more efficient. But you would know what works best for you better than I do. Personally, I would avoid hyphens. And I would not start objects with numbers, because that can cause problems later in VBA. But aside from that, if that's the way you want to do it, great.