Relationships for queries

MikeB wrote in

m:

Usually, when I design a query (and most often when I design a
query based on other queries) , I can drag a field from one table
to another to define a relationship between the tables.

I have just noticed that I can include queries in the Tools -
Relationships diagram.

If I do this, am I hard-coding relationships between queries? Is
there an advantage/disadvantage to doing so?

Thanks

Coding relationships on queries can save time and effort if you
repeatedly use those relationships in new queries.

The relation appears automatically when you add the queries into the
query builder. You can delete the join without affecting the
relationship, if necessary.

I often need to query my company's ERP system's part master table. All
attribute data for the parts is stored in the parts table as a long
integer, and all the attribute definitions (things like unit of
measure, Item Group, Make/Buy, etc) is in a second table. By making
permanent queries on this second table, I just call up the aplicable
query and have it related to the parts master without actually having
to link the relation fields and set the appropriate filter.

But there is no inherent advantage such as enforced integrity as
Albert Kallal and Tom Wickerath have pointed to you in their replies.

--
Bob Quintal