W
whodat
Is there ever a time when you would NOT use the Access Relationships
design window to establish relationships between tables? The
alternative would be to program relationships into each query design.
In what other circumstances might this be true? Would this be the
case, for example, if the relationships between tables may vary
depending on the query/report?
I realize it is horribly redundant and error-prone to set up
relationships for each query as opposed to doing it once for all, but
I seem to recall a seasoned programmer suggesting it to be the
appropriate approach in some cases.
Thanks,
An "unseasoned" programmer
design window to establish relationships between tables? The
alternative would be to program relationships into each query design.
In what other circumstances might this be true? Would this be the
case, for example, if the relationships between tables may vary
depending on the query/report?
I realize it is horribly redundant and error-prone to set up
relationships for each query as opposed to doing it once for all, but
I seem to recall a seasoned programmer suggesting it to be the
appropriate approach in some cases.
Thanks,
An "unseasoned" programmer