I'm a relative "newbie" to Access and have stumbled through most of what I've done on my own. What I'm wondering now is, can I use one form to input "same-as" data into various tables? Here's some background to give you an idea of what I'm doing.
The purpose of my database is to track performance of a certain piece of equipment (did it work or didn't it; if it didn't, let's look at each detail to try and figure out why). The piece of equipment is made up of 3 different "assemblies." One of those "assemblies" is made up of 2 components, while one of those breaks down even further into roughly 5 "major" components.
Here's my table breakdown:
Table "Event" contains general info about the event such as the event id# (key), event date, environmental conditions, and top-level assembly hardware info (Comp1 S/N, Comp2 S/N, Comp3 S/N, Comp4 S/N, Comp5 S/N).
Table "Comp1Mfr" contains event id# (key) and specific hardware data such as Comp1S/N, Comp1 E/L Lot No, Comp1 Mfr, and Comp1 Mfr Lot No.
Table "Comp2Assy" contains event id# (key) and "breakdown" data for the top-level assembly such as Comp2S/N, Comp2 Lot No, Comp3 S/N, Comp3 Lot No., Comp4 S/N, Comp4 Lot No.
Table "Comp3A/T" contains breakdown and test data for that assembly, such as Comp2 S/N (key), Comp3 S/N, Comp3 Lot No, Lot and serial number fields for 5 components, and 5 fields for test data. (Generally Comp2 and Comp3 S/N's are the same but I include both in case they differ, or to differentiate between lot numbers between Comp2 and Comp3).
Table "Comp4Test" contains test data for that assembly, such as Comp4 S/N (key), Comp4 Lot No, and 4 fields for test data.
If we look at relationships, "Event" is related to "Comp1Mfr" and "Comp2Assy" through event id#. "Comp2Assy" is related also to "Comp3A/T" through Comp2 S/N. "Comp4Test" is related to "Comp3Assy" through Comp4 S/N.
Here's what I want to do: If I input an unique id# for a new event, I'd like for it to be saved to the 3 tables that use it. And when I go further and enter the various S/N's and/or other data, I want them sent to the various tables that use them, too.
Can this be done as I have it set up now? Or do I need to re-think my whole database strategy, rework the relationships, or . . . ? Do I need the same key throughout each table (i.e., event id#)?
Is it even possible to get the data into the various tables by only entering it once?
Hopefully, this made sense and someone can shed some light on this for me. I've signed up for some Access courses but they're still a couple of weeks to a month away and I'd like to get this going right now.
The purpose of my database is to track performance of a certain piece of equipment (did it work or didn't it; if it didn't, let's look at each detail to try and figure out why). The piece of equipment is made up of 3 different "assemblies." One of those "assemblies" is made up of 2 components, while one of those breaks down even further into roughly 5 "major" components.
Here's my table breakdown:
Table "Event" contains general info about the event such as the event id# (key), event date, environmental conditions, and top-level assembly hardware info (Comp1 S/N, Comp2 S/N, Comp3 S/N, Comp4 S/N, Comp5 S/N).
Table "Comp1Mfr" contains event id# (key) and specific hardware data such as Comp1S/N, Comp1 E/L Lot No, Comp1 Mfr, and Comp1 Mfr Lot No.
Table "Comp2Assy" contains event id# (key) and "breakdown" data for the top-level assembly such as Comp2S/N, Comp2 Lot No, Comp3 S/N, Comp3 Lot No., Comp4 S/N, Comp4 Lot No.
Table "Comp3A/T" contains breakdown and test data for that assembly, such as Comp2 S/N (key), Comp3 S/N, Comp3 Lot No, Lot and serial number fields for 5 components, and 5 fields for test data. (Generally Comp2 and Comp3 S/N's are the same but I include both in case they differ, or to differentiate between lot numbers between Comp2 and Comp3).
Table "Comp4Test" contains test data for that assembly, such as Comp4 S/N (key), Comp4 Lot No, and 4 fields for test data.
If we look at relationships, "Event" is related to "Comp1Mfr" and "Comp2Assy" through event id#. "Comp2Assy" is related also to "Comp3A/T" through Comp2 S/N. "Comp4Test" is related to "Comp3Assy" through Comp4 S/N.
Here's what I want to do: If I input an unique id# for a new event, I'd like for it to be saved to the 3 tables that use it. And when I go further and enter the various S/N's and/or other data, I want them sent to the various tables that use them, too.
Can this be done as I have it set up now? Or do I need to re-think my whole database strategy, rework the relationships, or . . . ? Do I need the same key throughout each table (i.e., event id#)?
Is it even possible to get the data into the various tables by only entering it once?
Hopefully, this made sense and someone can shed some light on this for me. I've signed up for some Access courses but they're still a couple of weeks to a month away and I'd like to get this going right now.
