Why Base a Relationship on a Query

I am trying to understand why this might be done.

Because it does not honor Referential Integrity is there some advantage to
define this in the relationship window.

Is there some performance gain?

You might have two tables you want to relate but the data was formated
differently so using a calculated field you could then relate them.

Example --
Table_A Table_B
B123 123
C439 439

Fullname FName LName
Smith, Joe Joe Smith

"Harold" wrote:

I am trying to understand why this might be done.

Because it does not honor Referential Integrity is there some advantage to
define this in the relationship window.

Is there some performance gain?

I can do that in the Query Window. I still don't understand the advantage of
doing that in the Relationship Window, especially if Referential Integrity in
not honored.

I must be missing something.

"KARL DEWEY" wrote:

You might have two tables you want to relate but the data was formated
differently so using a calculated field you could then relate them.

Example --
Table_A Table_B
B123 123
C439 439

Fullname FName LName
Smith, Joe Joe Smith

"Harold" wrote:

I am trying to understand why this might be done.

Because it does not honor Referential Integrity is there some advantage to
define this in the relationship window.

Is there some performance gain?

On Fri, 1 May 2009 10:21:01 -0700, Harold
wrote:

I can do that in the Query Window. I still don't understand the advantage of
doing that in the Relationship Window, especially if Referential Integrity in
not honored.

AFAIK the only advantage of such a relationship is that it serves as a default
if you create a query using the objects being related. This can save a couple
of seconds. The performance depends on the indexes on the joined fields, and
the relationship window won't do anything with the indexes unless it's a
relationship with integrity enforced.
--

John W. Vinson [MVP]