could be a hard one to describe
I need to store requirement values in a database, no problem, right?
Here's the skinny. At run-time, a user will pass into some procedure a set of acquired values.
example: C = 0.34, Cr = 1.00, Fe = 96.6 : and says, "see if this meets the requirements of x entry in data base".
here is where my problem is.
The "X" entry in database needs to somehow be phrased as fallows.
(C must be at least 0.2 and at most 0.5)
(Cr must be under 1.20)
(Fe > 92.00)
and here is the super, tricky one
(Other [Cr + Fe + C] > 97.95)
Other, will not always be the same and for most database entries it's not even used.
But it does have the potential the be used frequently and will rarely ever be the same.
Anyway, the acquired values need be compared to the specification provided by the database entry
to determine a Pass/Fail.
I'm anticipating thousands of entries into the database over a long period of time.
If anyone can help me find a solution for this I would appreciate that very much. If my desired result is unclear then let me know and I will try to provide more details.
------------- Update ------------------------------
Please see ArunRajendra's question and the response.
Here is a link to an excel file (Opens in browser) to show the database structure ... ish.
Excel File That Opens In Browser
Here is a link to an image for an At a glance view of the DB