OK - So what you want is the ability to store the unit number and name, and
the serial number (is that the same as the tail number?) of the airplane.
And you don't need to store information about any personnel assigned to a
unit.
Also, you're not maintaining a table of parts, but we can still capture
information about the part that is being repaired for the database.
Then, I would modify the table structure that I'd proposed just a bit:
tblUnits
UnitID (primary key)
UnitName
UnitLocation
UnitContactPerson
(etc.)
tblAircraftModels
ModelID (primary key)
ModelName
(etc.)
tblAircrafts
AircraftID (primary key -- note that this could be
the tail number or the serial number)
AircraftTailNum (if you don't use tail number as
the primary key)
AircraftSerialNum (if this is not the same thing as
the tail number, and if you don't use
serial number as the primary key)
ModelID (foreign key from tblModels table)
(etc.)
tblWOPriorities
WOPriorityNum (foreign key)
WOPriorityDescription
tblWorkOrders
WONumber (primary key -- this would be the
support work order number)
AircraftID (foreign key to tblAircrafts)
UnitID (foreign key to tblUnits -- this is unit requesting
the work)
UnitWONumber
FaultDescription
WONotes
WOPriorityNum (foreign key to tblWOPriorities)
DateOpened
DateAccepted
DateClosed
(etc.)
tblWOParts (allows multiple parts for each work order)
WOPartsID (primary key)
WONumber (foreign key to tblWorkOrders)
PartDescription (memo field to allow free-form text
entry of information about the part;
this can be split into separate fields
if you know the specific details that
you want to store about each part
that is being repaired for the work
order)
(etc.)
How does this look?
--
Ken Snell
<MS ACCESS MVP>
M. Parker said:
sorry for the slow reply...work has been very hectic the past two days.
ok,
now to business. work requested by would be either an aircraft tail
number,
or tech supply. not a single person. the serial number would either be
the
aircrafts full tail number, or the serial number of the single part off of
the aircraft being repaired. the downfall of the single part is that i
won't
have the serial number until the part is in my hand, so i couldn't make a
table of parts..or at least as far as i can tell, i can't. for the
"business
rule" of it, units make request. the tail number of the aircraft, or if
it
is tech supply, lets me know the unit. i am thinking, maybe a table for
each
company with the tail numbers, or tech supply, as a field? the one part
per
workorder is a correct assumption. those are pretty much the rules. the
data
i need remain the same, minus the corrections i made in this post.
units(a;b;c;d co's), aircraft tail numbers, aircraft model(uh-60 or
ch-47),
unit workorder number(workorder number we generate with each request),
part
description(what the part is or what type of aircraft it is), work
requested
by( being either tail number or tech supply), serial number(being either
the
single parts number or the aircrafts full serial number), fault
description(what the issue is), priority of
work order(high or normal priority), opened date, accepted date, support
workorder number(work order number the supportng unit generates), and
closed
date. i hope this helps clarify things. once again, i really appreciate
the patience.
< snipped >