Depending on what you want to offer them you could use the hidden MSysObjects or just create a new Table that lists the Objects you want to give them access too

You could then use a Table/QueryDef to list the fields in a ListBox, double click to move them into a chosen ListBox.

Create a Query based on chosen.
Could have some way of allowing WHERE clause, etc.

Report Builder is likely to be a little more difficult but possible, although not sure how much effort you'd want to go to, probably easier just to give someone an Admin version and let them build it in Access instead of re-inventing the wheel.

Interesting...Thanks for the suggestions, Alex.

Jennifer Neighbors My Query Builder (shown below) adds the selected fields from the selected table to build the SQL statement. Click the button to create the Query.

Kevin, if the user selects a foreign key field like SalesRepID, does the query bring in the sales rep's name by joining the other table? Does your builder allow the user to set a parameter like a date range? How about the ability to sort on a field? I'm curious.

No, it's very basic. You can only add one table (for now). I have added the ability to add an ORDER BY. It can sort Ascending. Will be adding Descending soon. This is just a side project I started last night after reading your post that I'm doing just for fun. I plan to add more features when I get the chance.

I haven't locked the SQL Text Box so you can edit the SQL if needed.

I'd be interested to see what you do if you get further with this. Please keep in mind that my users have no insight into databases or Access, although they are familiar with the information and want to see it in new ways. They are unlikely to be able to edit an SQL statement meaningfully or even understand it. However, seeing it helps me understand the results being generated by your builder. I'm very interested in what you may develop along these lines. So cool that you did this!

Yeah Kevin's solution is very elegant. I have found when it comes to giving database capabilities to users who don't know much about the database that AI can play a good role in this. For example, that's one of the reasons I built the AI Query Builder. The end-user can literally just say something like 'Show me all the customers from Florida who have orders over $1000' and the AI can then generate the SQL and show the results. Whereas building something like that by hand could be quite tedious.