In the table of organisations, you will need fields like these:
- OrgID AutoNumber primary key
- ParentOrgID Number blank if this isn't a member of another org
- OrgName Text

Will there ever be a case where vehicles could be reassigned? If so, you
will need a table identifying what vehicle was assigned to what org and
when:
- VehicleID which vehicle was assigned
- OrgID who the vehicle was assigned to
- AssignDate when this vehicle was assigned to this org.
All 3 of those fields required, and a unique index on the combination of
VehicleID + AssignDate, so you can tell who it's currently assigned to.

Not sure how you do your waivered items, but it may be that the waivered
items depend on the vehicle type. a) If you had 15 instances of the same
kind of vehicle, would they all have the same waivered items? b) Or might
they be really individual (e.g. some have towbars or extras and you need to
handle those)?

If (a), you need a VehicleType table, linked one-to-many to the waivered
items. If (b), I suggest you still have a VehicleType table and a table of
default waivered items for that table, but the actual waivered items will
relate to the specific vehicle.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.


"Ron A." wrote in message
...
I am needing some assistance in creating a solid table structure in
creating
a database that stores vehicle permenant waiver items (items that will not
be
repaired) and produce a report showing waivers for a specific vehicle or
organization. Specifics are as follows:

- 1 organization has a master Org Code
- an organization can have many sub Org Codes (multiple shops in 1 org)
- an organization can have many Vehicle Control Officers (usually 1 per
sub
Org Code)
- Vehicles are assigned to master org code and sub org codes
- One vehicle can have many waivered items

I hope I have explained this well enough.

Thanks,
Ron A.