InfoPath Dev

So i emailed qdabra support, never heard back from anyone. I decided to spend some time trying to dechiper this problem as i am pressed to get this project finished. AND BOOM, the answer hit me. here it is for anyone ever encountering the same problem :   number(substring(string(round((my:o_labour + my:o_expense) * 100) * .01), 1, ...

 Will do, Thank you. We would very much prefer you if you could. Have you ever, or anyone else who is viewing this, had an issue like this before with calculated values? Are there any other type of rounding formulas that I haven't tried using?

 Hey Hilary, Just spoke with my boss and he says we have some more hours to spend with your team. Would you like to schedule a conference and you can look over my shoulder? Would that help so you can get a better feel for what's going on? I tried putting up the screenshots. I couldn't get them uploaded. Perhaps im doing it wrong. ...

 Because the problem isn't the data, The data is fine, upping the decimal point max wont change the calculated value from coming up with a number that doesn't exist or from the rounding function not rounding. if we add 500.00 + 500.20 it will equal 1000.20 but when the calc value does this, it comes up with a sum ...

 It's a numeric 28, 9, sorry.. Long day.

 Sorry the Data type is a simpleType. I believe its int in SQL but it comes across as simpleType in InfoPath. It's all coming across fine and looks great. Its only the calculated value creating a very strange long decimal. That wont adhear to the round function.

 Its not a data issue, It allows 9 decimals the data comes out of SQL fine. It's in the calc value that InfoPath or rather xpath that for some reason is taking a regular number and making a long decimal value.. Ex: Sql data = 154.200000000 and 200.290000000 in InfoPath the field data will be fine when we view the xml data(matches ...

 No, unfortunately it does not. Since the formatting is only at face value it still throws a validation error. This is a sql integration data form. The budget changes occur in the form and are then put back into the server. Knowing this, Everytime we try a submit of data back to the server it throws a validation error in InfoPath. In ...

 K, I still haven't found a fix. Would a rule be preferable over the default value for these functions? If so could you tell me why and to what would cause the calc value to behave in such a manner?

Hi guys, I'm developing a data form with nested repeating groups. I have all of the data coming across perfectly and it's a beautiful thing! The problem i am discovering in our form(s) is that when we calculate a new budget, simple addition, we get a  long decimal value. Not a big problem, or so i thought. I attempted a round ...