On Mon, 11 May 2009 20:37:01 -0700, viren < XXXX@XXXXX.COM >
Since you have not described how you structured your tables - rather just how
you use them - all I can say is "Do tell me more".
I would EXPECT that some of the Entities (real-life persons, things, or
events) of importance to your application would be Engines, Inspections,
Parts, and many to many junction tables between Engines and Inspections (each
engine will need many kinds of Inspections, and many engines will need a Rotor
Lubrication Inspection, say) and between Engines and Parts (a given engine
will have many, many Parts and each type of Part may be in many different
Engines). I see nothing there that would require storing data redundantly,
but... I don't know how to inspect jet engines, so I really don't know.
John W. Vinson [MVP]