Your question begins with a "straw man" that you then try to rationalize.
What limitations are the focus of your question? Queries can be simple or
complex. Creating queries can be as "straightforward" as writing an SQL
statement or using the QBE view in ACCESS -- or they can be more
user-friendly by providing controls on a form that allow the user to set the
filtering conditions and then the form's programming creates the query.
And anything in-between and outside this.

Signature
Ken Snell
<MS ACCESS MVP>
> Despite MS Access limitations, users should still be able to create
> queries
[quoted text clipped - 5 lines]
> restrictions in Access implementation of subqueries and operators. What i
> want to do seems basic to me, but out of reach. Is this typical?
jacob - 26 May 2005 19:16 GMT
Not being able to use DISTINCT with aggregation functions.
Not being able to use UNION in subqueries.
Not being able to do Correlated queries.
I've been able to avoid these by rewriting my queries. But now that they've
been rewritten, they cannot be expanded very much. Thus i have to RUN many
queries one after the other, changing a few IDs, to get the information i
need. This is time consuming.
Not to mention all the work getting around Access particularities.
I can post my queries, but to me, they are not very simple.
Ken Snell [MVP] - 26 May 2005 19:42 GMT
This is a fairly generic list, so I won't try to respond to them here. If
you have a specific example, post it and we'll see what we might suggest for
a different approach.

Signature
Ken Snell
<MS ACCESS MVP>
> Not being able to use DISTINCT with aggregation functions.
> Not being able to use UNION in subqueries.
[quoted text clipped - 10 lines]
>
> I can post my queries, but to me, they are not very simple.
jacob - 26 May 2005 20:33 GMT