Access should have design view for nested queries

[Guest]

It would be nice if you could add a nested query similar to adding an
existing saved query. The drop down menu could include "Create Nested Query"
right below "Show Table". A new window could then open up in design view to
create the nested query. Also, in the main query window, a right click on the
nested query could give options to "Edit Nested Query" or "Delete Nested
Query" similar to "Remove Table" when right clicking on a table header in
design view. The "Edit Nested Query" option could then open the nested query
in design view for further editting.

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...cbb0dc1b84&dg=microsoft.public.access.queries

 

[Jeff Boyce]

If you'll describe what you mean by "nested query", it may be that Access
can already provide a way to do what you mean...

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Van T. Dinh]

I guess Microsoft think that if you know nested queries (subqueries), then
you should be able to handle it in SQLView.

Note that the DesignView is fairly limited even for simple queries (for
example, joins must be of equality type with direct Field names) so it is
always good to be able to handle SQL construction in SQLView.

There are plenty of good books on SQL and in particular, JET SQL. One comes
into mind is "SQL Queries For Mere Mortals" by Hernandez & Viescas.

 

[Guest]

I agree - particularly because my reports often have embedded SQL or
a direct call to a 'report' query, with most of the logic in a source
query. From a report, if you open the data source you get a modal
view, which prevents you from opening the source query.

You have to close the query view, then go to the query page and
find the source query you just saw referenced, but can't remember
the name of, because you just closed the view, so you have to go
back to the report, examine the data source again, find that query,
then open it to see what the source query name is ...

On the other hand, if the only way MS can think of to build a UI
like this is to move the queries into a hidden binary object, then I'd
just as soon not have any new features.

(david)

It would be nice if you could add a nested query similar to adding an
existing saved query. The drop down menu could include "Create Nested Query"
right below "Show Table". A new window could then open up in design view to
create the nested query. Also, in the main query window, a right click on the
nested query could give options to "Edit Nested Query" or "Delete Nested
Query" similar to "Remove Table" when right clicking on a table header in
design view. The "Edit Nested Query" option could then open the nested query
in design view for further editting.

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...cbb0dc1b84&dg=microsoft.public.access.queries

 

[Michel Walsh]

Hi,


I am almost sure Microsoft considers that as a nice feature to add to the
query editor, as the possibility to use something else than equi-joins in
the graphic editor, but they probably consider it as a feature for
"advanced" users. If think you have to bring to the Microsoft attention that
these modifications would greatly enhance the intermediate user 'experience'
using Microsoft Access, if not also the beginner or someone with an Excel
background. Showing that a wide audience could benefit from an easier
interface (than the SQL view) is definitively an insensitive, for Microsoft,
as much as the feature "itself". Otherwise, that may be just one more quite
interesting feature, but that no one use, in Microsoft point of view.


Vanderghast, Access MVP