Solved simple calculations causing errors (1 Viewer)

[miked18]

I have a form where i enter products, quantity, price. you can enter up to 8 products (it's ok) I have a button to update the quantities and calculate the the total price.(cmdUPDATETOTALS)
simple code. TotalQuantity = quantity1+quantity2, etc. TotalPrice = price1*quantity1+price2*quantity2, etc.

After form load, if i hit the cmdUPDATETOTALS with no values present, nothing happens. which is fine. If i enter data and hit the cmdUPDATETOTALS, it does the calculations fine.

I have other buttons to either cmdCLEARALLPRODUCT data or I can clear individual products with cmdCLEARPRODUCT1. these set the fields to "". example: me.quantity1 = ""

after I use either commands to clear the data, i start getting "runtime error 13, type mismatch" when I click the cmdUPDATETOTALS. this happens if any of the product fields are empty. if i just cleared product1, then entered new data into product1, its fine. if i clear product1 and product2 and only enter new data into product1, i get the error.

i dont get it. on form load, all of these values are set to ="", so why would clearing the data and setting it back to ="" cause a type mismatch error?

thanks.

 

[theDBguy]

Hi. My first impression is you're hitting an issue with Nulls. However, I am wondering if anyone has already told you about having fields called quantity1, quantity2, price1, and price2? That's usually an indication of a bad design.

 

[CJ_London]

these set the fields to "". example: me.quantity1 = ""

“” is a string- you can’t multiply strings wrong datatype

use 0 or null

 

[GaP42]

Setting a numeric field to null may be the source of the problems - but hard to tell without a sample/cut down version of the db / table defs and code.
The display of controls on the form does not necessarily mean the data structure is flawed. I presume that it is set up to allow quick entry for multiple line items, and not repeating columns in a table.

 

[ebs17]

Setting a numeric field to null may be the source of the problems

No, setting numeric field to null is the solution.

type mismatch error

@CJ_London understood the loud outcry. Look at #3.

 

[miked18]

I get that it may be bad design, but I am not sure how else to do it to accomplish what I am after. I appreciate all of the responses. @CJ_London, thanks. I see my error now and forgot that "" is a string. Setting the numeric fields to "0" fixed that. Thanks.

 

[Pat Hartman]

but I am not sure how else to do it to accomplish what I am after.

Why not start a new thread and ask us