![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| |||
| |||
|
|
Furthermore for all text fields in MS access, since they are a variable length, the empty fields don't take up really any significant additional space at all when you don't enter data into them. |
|
If none of the data is repeating at all, then I think you should put the fields in the one main table. While a good normalize databae saves you time and makes the application more flexibility, it does often require the developer to put little bit more effort in terms of building sub forms, and writing reports that are little more difficult to build. The slight additional effort does result in an application that is far more flexible, and far more appropriate for the end user. However, in your case since there's no obvious need to put these fields in additional tables, and the additional design work, development work, and additional workload you'll have when you build reports, forms etc is likely to be of no benefit to you or your users in this case. Furthermore for all text fields in MS access, since they are a variable length, the empty fields don't take up really any significant additional space at all when you don't enter data into them. -- Albert D. Kallal (Access MVP) Edmonton, Alberta Canada pleaseNOOSpamKallal (AT) msn (DOT) com |
![]() |
| Thread Tools | |
| Display Modes | |
| |