I am trying to modify a database that stores leak data from air leak surveys.
Currently it has basic data such as date found, date repaired, type of leak, etc.
We use a simple form to make new entries to the database.
Air leaks are quantified by a dB reading on the collector, but need to be represented as a CFM or $ amount to mean anything. So:
Also, as the dB_Value (in the lookup table) will always equal the id, do I need the dB_Value column? or is it better to use it rather than the ID? What problems might I encounter using the id column instead of the dB_Value column?
Currently it has basic data such as date found, date repaired, type of leak, etc.
We use a simple form to make new entries to the database.
Air leaks are quantified by a dB reading on the collector, but need to be represented as a CFM or $ amount to mean anything. So:
- I have added colums for dB reading "dB" of the leak, and the estimated CFM "CFM" of the leak.
- I created a new table consisting of "dB Value"(field 1), which has the values 1 through 120, and "CFM"(field 2), which has the estimated leak rates for the values in field 1.
- I added a combo box to the form to lookup the values, based on the dB. It populates to the "dB' field in the "Air Leak" database table just fine. But how do I also get the corresponding value to populate the "CFM" field in the "Air Leak" database table?
Also, as the dB_Value (in the lookup table) will always equal the id, do I need the dB_Value column? or is it better to use it rather than the ID? What problems might I encounter using the id column instead of the dB_Value column?