Missing sub data sheet in table view

[Steve]

I have 7 sets of 3 tables. In the relationship view i have joined the 3
tables together, all are exactly the same.

The join between two of the tables is not on a primary key but the field is
set as an indexed item.

In the table view, one set works fine with the "+" symbol appearing against
each line in all 3 tables, for all the rest the "+" symbol is missing between
one of the tables (the one no pointed via primary key).

Why? Please help.

Steve

 

[Tim Ferguson]

I have 7 sets of 3 tables. In the relationship view i have joined the
3 tables together, all are exactly the same.

This sounds terribly like a Design Problem. Why are there repeated
patterns of tables? Why not just three tables with appropriate fields?

The join between two of the tables is not on a primary key but the
field is set as an indexed item.

It may be legal, but it's really pretty rare to point foreign keys at a
non-primary key. What gives?

In the table view, one set works fine with the "+" symbol appearing
against each line in all 3 tables, for all the rest the "+" symbol is
missing between one of the tables (the one no pointed via primary
key).

To most people round here, the appearance of the table sheets is pretty
uninteresting. Developers use them for debugging and designing; users
should never see them; and the "subtables" misfeature generally just gets
switched off because it is useless at best and at worst gets in the way.

Sorry if that sounds a bit negative -- but if I were you I would be
thinking much harder about the basic schema design than the vagaries of
Access's GUI.

Best wishes


Tim F

 

[Steve]

To be honest i agree, i never liked the sub data view, just gets in the way,
if i want to look at a table i'll look at it, if i want to see more i'll
write a query, unfortunatly some departments seem hooked on them and if in
boubt ask me. I couldnt find a solution and it just bothered me my it didnt
work.

Why the bad design, because the 'analyst' is used to our old COBOL systems
which is the source of where our info comes from and they seem hooked on
keeping the old design flaws in the db, sad but i known where there comming
from.

Thanks for the feed back, confirmed my thought, just dont like access
beating me thats all.

Steve

 

[Tim Ferguson]

Thanks for the feed back, confirmed my thought, just dont like access
beating me thats all.

Don't think Access is beating you, any more than my car would beat me if I
wanted to cook my dinner with it... Access is a desktop database platform,
not an end-user application, and most definitely not a spreadsheet. Try
pointing your users at Excel, which will do everything they want and more.
And they'll be less dangerous. And leave you alone. Everyone wins!

Best wishes


Tim F