Keep number of fields low

[Dennis]

Setting up a database on some equipment to reference numbers from different
illustrations to multiple parts of the equipment and I am wondering how to
tie this together so I don't have to use so many fields. Each piece of
equipment will have three sections, each section can have up to 18
illustrations

 

[Steve]

How about the following tables:
TblEquipment
EquipmentID
EquipmentName
<<Other fields that are in a 1:1 relationship with the equipment item>>

TblEquipmentSection
EquipmentSectionID
EquipmentID
SectionDescription
<<Other fields that are in a 1:1 relationship with the equipment section>>

TblSectionIllustration
SectionIllustrationID
EquipmentSectionID
SectionIllustrationDescription
<<Other fields that are in a 1:1 relationship with the section
illustration>>

PC Datasheet
Providing Customers A Resource For Help With Access, Excel And Word
Applications
(e-mail address removed)

 

[John W. Vinson]

Setting up a database on some equipment to reference numbers from different
illustrations to multiple parts of the equipment and I am wondering how to
tie this together so I don't have to use so many fields. Each piece of
equipment will have three sections, each section can have up to 18
illustrations

Any time you find yourself saying "each <x> will have up to some number of
<y>" then you should immediately STOP thinking about fields and start thinking
about adding another Table. You need a table of equipment related one-to-many
to a table of Sections, which is in turn related one to many to a table of
Illustrations.

John W. Vinson [MVP]

 

[Steve]

Isn't that what I suggested, John?

Steve

PC Datasheet
Providing Customers A Resource For Help With Access, Excel And Word
Applications
(e-mail address removed)

 

[John W. Vinson]

Isn't that what I suggested, John?

Steve

Yes, it is. I'd missed your post though it was well before mine.

John W. Vinson [MVP]