B
Barry A&P
I have been working on a Aircraft parts database and i truely appreciate the
great answers and help ive been getting. I have been happy with my progress
and i have been having a great time but i have been having a little trouble
figuring out the best way to deal with self join data. here are some of my
tables.
T_PartNumbers
PNID (pk)
PartNumber
Description
Life
(CategoryID (fk)
T_SerialNumbers
SNID (pk)
SerialNumber
NextHigherAssyID (fk) (self join to SNID)
LocationID (fk)
T_installHistory
InstallID (pk)
SNID (fk)
InstallTime
RemovalTime
Notes
some of my forms are
F_SerialNumbers (based on Q_AllItems)
SNID (pk)
PartNumber
Description
SerialNumber
ParentID (combo)
F_Sub_InstallHistory
SNID
ParentID
InstallTime
RemovalTime
TimeInService (=RemovalTime-InstallTime)
TimeRemaining (=T_Partnumbers.Life-TimeInService)
My main form is based on T-SerialNumbers as S/N individuates each item.
i can use my form to enter Times and installation data for each serialized
item but i find myself searching around alot to update sub-component times.
How would i do something like a subform that would display all of the
Sub-Components associated to the Major component listed on the main form. and
group them by Sub-Assemblies.
Also how would i run a report to show a tree of all related sub-assemblies,
and sub-components.
would anybody be willing to share a database sample that reports self join
data.
would anybody be willing to look at my database to see if i am way off base?
Or If anybody has more insight on what im doing it would be greatly
appreciated. here are some criteria or goals i am trying to meet.
1. A Part Number (P/N) can have many Serial Numbers (S/N)
2. Different P/N's can have same S/N (most Sub-components are serialized to
assembly)
3. A P/N belings to a category, a Category has many P/N's
4. A S/N may either be a parent assembly, A sub-Assembly or a Sub Component
5. A S/N must belong to a current Location (or Parent that has a current
location) history must be kept of previous locations (or Parents).
6. If Time in service is updated on a parent S/N the sub-S/N's must also
reflect a time update.
7. when a Major assembly is added it will be convienient to also add its sub
assemblies from existing recorded items or by adding new records.
8. If a report is requested on a S/N Assembly it will show all
Sub-Components, Sub assemblies, and Sub-assembly Sub-Components. Or just
Sub-Assemblies.
9A. A S/N component may have a Life limit. #of hours in service.
9B. A Sub component may have a shorter life than its parent.
9C. Current Time in service is applied to the highest level parent, Low time
sub components must be easy to report, or alert if a time threshold has been
exceeded.
Am i out of my league or what.
great answers and help ive been getting. I have been happy with my progress
and i have been having a great time but i have been having a little trouble
figuring out the best way to deal with self join data. here are some of my
tables.
T_PartNumbers
PNID (pk)
PartNumber
Description
Life
(CategoryID (fk)
T_SerialNumbers
SNID (pk)
SerialNumber
NextHigherAssyID (fk) (self join to SNID)
LocationID (fk)
T_installHistory
InstallID (pk)
SNID (fk)
InstallTime
RemovalTime
Notes
some of my forms are
F_SerialNumbers (based on Q_AllItems)
SNID (pk)
PartNumber
Description
SerialNumber
ParentID (combo)
F_Sub_InstallHistory
SNID
ParentID
InstallTime
RemovalTime
TimeInService (=RemovalTime-InstallTime)
TimeRemaining (=T_Partnumbers.Life-TimeInService)
My main form is based on T-SerialNumbers as S/N individuates each item.
i can use my form to enter Times and installation data for each serialized
item but i find myself searching around alot to update sub-component times.
How would i do something like a subform that would display all of the
Sub-Components associated to the Major component listed on the main form. and
group them by Sub-Assemblies.
Also how would i run a report to show a tree of all related sub-assemblies,
and sub-components.
would anybody be willing to share a database sample that reports self join
data.
would anybody be willing to look at my database to see if i am way off base?
Or If anybody has more insight on what im doing it would be greatly
appreciated. here are some criteria or goals i am trying to meet.
1. A Part Number (P/N) can have many Serial Numbers (S/N)
2. Different P/N's can have same S/N (most Sub-components are serialized to
assembly)
3. A P/N belings to a category, a Category has many P/N's
4. A S/N may either be a parent assembly, A sub-Assembly or a Sub Component
5. A S/N must belong to a current Location (or Parent that has a current
location) history must be kept of previous locations (or Parents).
6. If Time in service is updated on a parent S/N the sub-S/N's must also
reflect a time update.
7. when a Major assembly is added it will be convienient to also add its sub
assemblies from existing recorded items or by adding new records.
8. If a report is requested on a S/N Assembly it will show all
Sub-Components, Sub assemblies, and Sub-assembly Sub-Components. Or just
Sub-Assemblies.
9A. A S/N component may have a Life limit. #of hours in service.
9B. A Sub component may have a shorter life than its parent.
9C. Current Time in service is applied to the highest level parent, Low time
sub components must be easy to report, or alert if a time threshold has been
exceeded.
Am i out of my league or what.