where are relationships stored?

[Christopher Glaeser]

My database is separated into FE and BE. All tables are in the BE. I had
been assuming that the relationships were stored with the tables in the BE,
but I just noticed that the FE also has a set of relationships that is
different from the set in the BE. I'm experiencing problems with reports,
and I think this may be the cause. Where should the relationships be
stored? Should I delete all the relationships in the FE? Using Access
2003.

Best,
Christopher

 

[Guest]

The relationship definitions are stored in the db where the tables physically
reside.

That said, you can define/re-define relationships in the front end as well,
and that could be your problem.

One thing to look for is how the relationship dialog shows you the choices
for defining relationships. The options for enforcing referential integrity
in a relationship are greyed out for linked tables.

 

[Christopher Glaeser]

That said, you can define/re-define relationships in the front end as

well,
and that could be your problem.

Thanks. I think I may have accidentally defined a relationship while in the
frontend, thinking it would go in the backend. Is there a way to determine
if any relationships are defined in the frontend? If I delete all links to
tables and then relink, will that ensure there are no relationships in the
frontend?

Best,
Christopher

 

[Guest]

Yes, just be sure you are in the front end when you do it.

This has been a source of frustration to me from time to time as it means
closing the front end, opening the back end, making the changes required in
the relationships, etc.

 

[John Vinson]

Thanks. I think I may have accidentally defined a relationship while in the
frontend, thinking it would go in the backend. Is there a way to determine
if any relationships are defined in the frontend? If I delete all links to
tables and then relink, will that ensure there are no relationships in the
frontend?

Bear in mind that relationships are rather passive - they don't "do"
anything, other than preventing you from adding orphan records.

A relationship defined in a frontend won't even do that, since you
cannot specify that it enforce referential integrity. All a
relationship defined in the frontend does is serve as the default Join
when you create a query using the related tables - and even that join
can be changed.

What specific report problems are you having? I suspect that you may
be on the wrong track!

John W. Vinson[MVP]

 

[Christopher Glaeser]

What specific report problems are you having? I suspect that you may

be on the wrong track!

I suspect you are right. The report wizard generates an error message that
it can not generate a report for one of my queries, and when I design my own
very simple report with only one field, the report preview has empty pages,
and there appears to be an infinite number of pages. When I invoke the
query manually, it generates a one row table that appears to be fine.

Best,
Christopher

 

[Christopher Glaeser]

I suspect that you may be on the wrong track!

You were right. The default printer had been changed to the Dymo Label
Writer, which has an extremely small paper size, thus causing many problems
with reports.

Best,
Christopher

 

[John Vinson]

The default printer had been changed to the Dymo Label
Writer, which has an extremely small paper size, thus causing many problems
with reports.

<snork!!>

Yes... that it would do...

I had to install a Dymo Label Writer for a client last month. Neat
little printer, but *not* one that you want as your default!

John W. Vinson[MVP]