<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://www.infopathdev.com:443/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>General</title><link>https://www.infopathdev.com:443/forums/41.aspx</link><description>If you're not sure where to ask your question, ask it here. If necessary, our moderators will make sure it gets classified in the correct board.</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP3 (Build: 31118.962)</generator><item><title>Re: Issue with a decimal field</title><link>https://www.infopathdev.com:443/forums/thread/53600.aspx</link><pubDate>Mon, 12 Apr 2010 19:53:31 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:53600</guid><dc:creator>ErnestoM</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/53600.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&amp;PostID=53600</wfw:commentRss><description>&lt;p&gt;Hello!&lt;/p&gt;&lt;p&gt;One option is to use Data Validation, and simply prevent people from entering non integer characters. That is, force them to only enter integers.&lt;/p&gt;&lt;p&gt;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 &lt;br /&gt;&lt;/p&gt;&lt;p&gt;Finally, you could try some wacky substring commands as in the attached form.&lt;/p&gt;&lt;p&gt;Good luck! &lt;br /&gt;&lt;/p&gt;</description></item><item><title>Issue with a decimal field</title><link>https://www.infopathdev.com:443/forums/thread/53516.aspx</link><pubDate>Fri, 09 Apr 2010 11:02:49 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:53516</guid><dc:creator>Svetoslav</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/53516.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&amp;PostID=53516</wfw:commentRss><description>&lt;p&gt;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 &amp;quot;.&amp;quot; - decimal point and &amp;quot;,&amp;quot; for thousands separator (grouping symbol)
EU: uses &amp;quot;,&amp;quot; - decimal comma and &amp;quot;.&amp;quot; for thousands separator (grouping symbol)&lt;/p&gt;

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.</description></item></channel></rss>