As I understand it, each consumer may be associated with several pieces of
equipment, and each piece of equipment may be associated with several
consumers. Therefore there is a many-to-many relationship between equipment
and consumers.
tblConsumer
ConsumerID (primary key, or PK)
FirstName
etc.
tblEquipment
EquipmentID (PK)
EquipDescription
SerialNum
etc.
tblEvent
EventID (PK)
ConsumerID (foreign key, or FK)
EquipmentID (FK)
DateIssued
DateReturned
Create a relationship between the PK fields in tblConsumer and tblEquipment
and their namesake fields in tblEvent. Click Enforce Referential Integrity.
Create a form based on tblConsumer, and a subform based on tblEvent. The
subform on tblEvent has a combo box bound to EquipmentID, with tblEquipment
as its row source. EquipmentID will be the first column of the row source
query, and EquipDescription the second column. Set the combo box column
count to 2, its bound column to 1, and its column widths to 0";1.5" (or
whatever works for the second column). Add other columns such as SN as
needed, but the bound column will be 1 in any case.
This is a thumbnail description, but the approach should give you what you
need. Experiment on a small scale, with just a few fields from each table
and simple forms. Extra fields can be added as needed.
You could also build a form based on tblEquipment, with a subform based on
tblEvent. The combo box on the subform would be based on tblConsumer. It
depends on how you want to manage the data. In any case, with this
structure you can look at equipment per consumer or vice versa, as you
choose.