New query in place of messy query?

[Guest]

When working with forms and reports, and your data comes from a query, is it
advisable to create a new query based on your original query, when your
original query has multiple tables or is otherwise messy?

 

[david epsom dot com dot au]

It is advisable to have a coding practice and stick to it.

Technically it doesn't matter if you save the query with
a new name, or just save it (hidden) with the name of the
form, as happens when you leave it as a form property.

I find it easier to work with queries if they are saved
with a new name, but that is just personal preference.

(david)

 

[John Vinson]

When working with forms and reports, and your data comes from a query, is it
advisable to create a new query based on your original query, when your
original query has multiple tables or is otherwise messy?

Your new report should be based on whatever query is needed to make it
work. This might be an existing query (often handy if you have
multiple reports using the same kind of information) or a new query,
or a new query based on an existing query. There's nothing "wrong"
about any of these choices, though you'ld probably want to avoid
having lots of queries cluttered with lots of unused and uneeded
joined tables, just for performance and documentation.

John W. Vinson[MVP]