![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| |||
| |||
|
|
In my view, it is still a part of good ralational database design to use join tables. Am I wrong? |
#4
| |||
| |||
|
|
Hi group, I have read in a few places opinions stating that with version 8 there is no need at all for join files. Is this true? If so, what is the way to go for typical situations like many contacts associated with many clients, and viceversa? In FM6 and bellow, I would have a join file to create relationships between contacts and clients, avoiding the need to duplicate contact records and related info. How can this be done in version 8 (or 7, by the way) without the join file? Is it advantageous compared to the "old" style? |
#5
| |||
| |||
|
|
Jens Rasmussen wrote: In my view, it is still a part of good ralational database design to use join tables. Am I wrong? |
#6
| |||
| |||
|
|
In article <7jsij15bj4jc0hdkf3sr31bps1pgkgrip3 (AT) 4ax (DOT) com>, carlosp (AT) nnhotmail (DOT) com says... Hi group, I have read in a few places opinions stating that with version 8 there is no need at all for join files. Is this true? If so, what is the way to go for typical situations like many contacts associated with many clients, and viceversa? In FM6 and bellow, I would have a join file to create relationships between contacts and clients, avoiding the need to duplicate contact records and related info. How can this be done in version 8 (or 7, by the way) without the join file? Is it advantageous compared to the "old" style? You still require join *tables*. You no longer require join files. As you can put multiple tables in a single file. And as someone else commented you can now directly plumb more than on relationship deep through the relationship hierarchy without fiddling with intermediate fields or calculated results. |
![]() |
| Thread Tools | |
| Display Modes | |
| |