P
pwizzle
Hi all,
I've got a real challenge this time with an access database that I'm
writing. I'm at my witts end trying to figure out a feasible solution,
but to no avail. I'm writing this database for work, and failing to
come up with a fix for this problem is going to be a major problem.
Long story short:
1) I work for a grocery store, and I have imported a listing of about
12,000 items that we sell into this database. This list includes
dimensional data about every product (height, width, and depth)
2) We have several people out in our stores measuring product in an
effort to audit this data. They input their measurements into a form
that I put together and the form dumps the audit measurements into
separate columns in the same table via a recordset.
3) I have conditional formatting set up that compares the data in the
table to the data they enter into the text boxes. This conditional
formatting works fine and correctly identifies when the two numbers do
not equal by coloring the text box red.
My problem is that I have a query put together that spits out all of
the data in the table. For example, column #1 in the query is titled
"System Case Height" and column #2 is titled "Audited Case Height".
Column #3 is set up to spit out "Yes" or "No" depending on if these
numbers are equal or not.
Here is the code for column 3:
CaseHeight_In_Tollerance?:
IIf([System_Case_Height]-[Audit_Case_Height]=0),"Yes","No")
Most of the time, Yes and no are returned correctly. However once every
few records, the query returns "No" when the numbers are the same.
Looking directly at the query, 1.9 is in column #1 and 1.9 is in column
#2, yet the query still returns "No".
In the table, both columns are set to type "Number" and Decimal places
to "Auto".
The key here (I presume) has something to do with the precision of the
numbers. I'm betting that access is somehow storing an extra decimal
place or something that I cannot see... however I am stumped as to how
to test for this.
This question is very long and very detailed, and I will understand if
I get no responses, but I'm keeping my fingers crossed that maybe
someone knows a way of going about testing this problem out that I
haven't thought of... I will be eternally grateful for any help that
you guys can provide.
--Pat
I've got a real challenge this time with an access database that I'm
writing. I'm at my witts end trying to figure out a feasible solution,
but to no avail. I'm writing this database for work, and failing to
come up with a fix for this problem is going to be a major problem.
Long story short:
1) I work for a grocery store, and I have imported a listing of about
12,000 items that we sell into this database. This list includes
dimensional data about every product (height, width, and depth)
2) We have several people out in our stores measuring product in an
effort to audit this data. They input their measurements into a form
that I put together and the form dumps the audit measurements into
separate columns in the same table via a recordset.
3) I have conditional formatting set up that compares the data in the
table to the data they enter into the text boxes. This conditional
formatting works fine and correctly identifies when the two numbers do
not equal by coloring the text box red.
My problem is that I have a query put together that spits out all of
the data in the table. For example, column #1 in the query is titled
"System Case Height" and column #2 is titled "Audited Case Height".
Column #3 is set up to spit out "Yes" or "No" depending on if these
numbers are equal or not.
Here is the code for column 3:
CaseHeight_In_Tollerance?:
IIf([System_Case_Height]-[Audit_Case_Height]=0),"Yes","No")
Most of the time, Yes and no are returned correctly. However once every
few records, the query returns "No" when the numbers are the same.
Looking directly at the query, 1.9 is in column #1 and 1.9 is in column
#2, yet the query still returns "No".
In the table, both columns are set to type "Number" and Decimal places
to "Auto".
The key here (I presume) has something to do with the precision of the
numbers. I'm betting that access is somehow storing an extra decimal
place or something that I cannot see... however I am stumped as to how
to test for this.
This question is very long and very detailed, and I will understand if
I get no responses, but I'm keeping my fingers crossed that maybe
someone knows a way of going about testing this problem out that I
haven't thought of... I will be eternally grateful for any help that
you guys can provide.
--Pat