One-to-one database relationship

[boaz]

Hi,

Would someone tell me why a 1-to-1 db relationship is not a good database
design please?


--

 

[Guest]

Because if there is always one, why bother putting it in a
separate table? If one person always has one address,
don't bother creating an address table. Put the address
element on the person table.

And we don't do homework here.

 

[Nick Mirro]

I disagree. Even Access documentation describes the usefulness of breaking
data into logical (related) chunks. There are many instances when this is
useful. In my experience, however, Access 1:1 relationships can be
problematic when matched with complex queries. I found instances of
non-updateable (is that a word?) recordsets that could only be resolved by
going 1 : many, despite the apparent inappropriateness. I'm no expert here
though.