Issue with a decimal field - InfoPath Dev
in

InfoPath Dev

Issue with a decimal field

Last post 04-12-2010 12:53 PM by ErnestoM. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 04-09-2010 04:02 AM

    Issue with a decimal field

    Hello all I am having an issue with a field formated as decimal(double) Since my template is for global use, I have formatted the field to ignore thousand separation, and only 2 position after the decimal comma to be active (apply this due to cents). Recently I have noticed that I have missed something very important. I suppose that for the IP product, there exist two types of general formats. US and EU US: uses "." - decimal point and "," for thousands separator (grouping symbol) EU: uses "," - decimal comma and "." for thousands separator (grouping symbol)

    Now I am experiencing a problem since users are using the form with both standarts (EU and US). And as you can imagine it causes me problem. I cannot understand if it is 55.55 (fifty five euros and 55 cents) or it is 5555 Euros.. Related to this how can I solve the problem. If I convert the field how will it be affected (converting to integer). I think it will give me validation errors if there are cents entered. I think I can iliminate cents if I use roudning but will it convert the number to integer..Very interesting question I think.
  • 04-12-2010 12:53 PM In reply to

    Hello!

    One option is to use Data Validation, and simply prevent people from entering non integer characters. That is, force them to only enter integers.

    Another option is to split this into two fields: one field for the numbers before the period/comma, and then one field for the two digits after the decimal

    Finally, you could try some wacky substring commands as in the attached form.

    Good luck!

    Ernesto Machado
    Qdabra® Software/ InfoPathDev.com
    The InfoPath Experts – Streamline data gathering to turn process into knowledge.™


Page 1 of 1 (2 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.