Relationships - specify in front-end or back-end

When I started my database, I had everything in one access file (.mdb)
then I read here that it is a good idea to split the tables from the
queries and the forms into a back-end (tables only) and a front-end
(forms, queries etc).

Now I notice that I have a Tools - Relationship diagram in both the
front-end and the back end. Which one does Access use? Can I safely
delete one? I don't really think it is correct that this information
should be in two places at the same time.

Thanks.

Hi Mike,

Here's a pasted answer from John Vinson in another forum recently:
________________________________________________
The relationships can only exist and be enforced in the backend; that's where
the tables are. Relationships established in a DIFFERENT database (a frontend)
would have no way of being enforced, since someone could open the backend
directly, or from a different frontend.

So: relationships are *only* in the backend. Anything in the frontend is just
for documentation or information, not for controlling the data.
_________________________________________________


HTH. If it does, give me credit. If it doesn't, blame John
CW

"MikeB" wrote:

When I started my database, I had everything in one access file (.mdb)
then I read here that it is a good idea to split the tables from the
queries and the forms into a back-end (tables only) and a front-end
(forms, queries etc).

Now I notice that I have a Tools - Relationship diagram in both the
front-end and the back end. Which one does Access use? Can I safely
delete one? I don't really think it is correct that this information
should be in two places at the same time.

Thanks.

Cheese_whiz wrote:

HTH. If it does, give me credit. If it doesn't, blame John

Both you and John are correct.

Always ignore the relationships diagram in the front end.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

On Mon, 27 Oct 2008 11:13:01 -0700, Cheese_whiz
wrote:

Hi Mike,

Here's a pasted answer from John Vinson in another forum recently:
_______________________________________________ _
The relationships can only exist and be enforced in the backend; that's where
the tables are. Relationships established in a DIFFERENT database (a frontend)
would have no way of being enforced, since someone could open the backend
directly, or from a different frontend.

So: relationships are *only* in the backend. Anything in the frontend is just
for documentation or information, not for controlling the data.
_______________________________________________ __


HTH. If it does, give me credit. If it doesn't, blame John

g Thanks Cheese_whiz.

Just an additional note - relationships in the frontend are generally
"inherited" from the "real" relationships in the backend. They're not totally
useless, in that when you create a new Query involving two tables, the join in
the query will be defined based on the stored relationship.
--

John W. Vinson [MVP]