[AccessD] relations in which database

Hi Bruce and Charlotte

> "The best arguments for putting relationships in the back end is 1) You
> can create any kind of temporary relationship you want in the front end
> on the fly as you need it.  They don't have to be stored there, and 2)
> If you front end becomes toast, you still have the relationships in the
> back end where they belong."

> AMEN!

I don't get this. Relationships are primarily for defining referential
integrity - a key part of database design - and as such they don't
just "belong to the BE", they simply must exist there.
As such you can retrieve or mirror them into any FE linking to that BE
but that is just display of the relations and for use by the GUI query
designer; it has no further use.

By the way, what is a "temporary relationship"? If a new relationship
is needed you are redesigning the database scheme and that must be
implemented in the BE ...

/gustav