<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How to overcome JMP converting very large numbers to scientific notation? in Discussions</title>
    <link>https://community.jmp.com/t5/Discussions/How-to-overcome-JMP-converting-very-large-numbers-to-scientific/m-p/452208#M69892</link>
    <description>&lt;P&gt;And depending what you are doing, maybe you can use Character column instead of numeric&lt;/P&gt;</description>
    <pubDate>Tue, 18 Jan 2022 19:44:20 GMT</pubDate>
    <dc:creator>jthi</dc:creator>
    <dc:date>2022-01-18T19:44:20Z</dc:date>
    <item>
      <title>How to overcome JMP converting very large numbers to scientific notation?</title>
      <link>https://community.jmp.com/t5/Discussions/How-to-overcome-JMP-converting-very-large-numbers-to-scientific/m-p/452151#M69887</link>
      <description>&lt;P&gt;JMP converts integers to scientific notation if the number's base 10 exponent is greater than 15 i.e 10000000000000000 will be converted to 1e+16.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is convenient, but in my case I would like this number to remain unchanged, specifically to avoid further backend work to ensure SQL can interpret this correctly.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 09 Jun 2023 18:09:04 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/How-to-overcome-JMP-converting-very-large-numbers-to-scientific/m-p/452151#M69887</guid>
      <dc:creator>mmelende</dc:creator>
      <dc:date>2023-06-09T18:09:04Z</dc:date>
    </item>
    <item>
      <title>Re: How to overcome JMP converting very large numbers to scientific notation?</title>
      <link>https://community.jmp.com/t5/Discussions/How-to-overcome-JMP-converting-very-large-numbers-to-scientific/m-p/452191#M69890</link>
      <description>&lt;P&gt;JMP uses double precision float for numeric continuous values.&amp;nbsp; This is limited to 16 digits of precision.&amp;nbsp; If you want to display all 16 digits without exponential notation, right-click on the column, choose column info, and change Format from Best to Fixed Dec and make the width 16 and the Dec value 0.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;If you wish to preserve more than 16 digits of information, then you will need to import the numbers as nominal character strings as suggested below.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jan 2022 21:21:06 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/How-to-overcome-JMP-converting-very-large-numbers-to-scientific/m-p/452191#M69890</guid>
      <dc:creator>Mark_Zwald</dc:creator>
      <dc:date>2022-01-18T21:21:06Z</dc:date>
    </item>
    <item>
      <title>Re: How to overcome JMP converting very large numbers to scientific notation?</title>
      <link>https://community.jmp.com/t5/Discussions/How-to-overcome-JMP-converting-very-large-numbers-to-scientific/m-p/452208#M69892</link>
      <description>&lt;P&gt;And depending what you are doing, maybe you can use Character column instead of numeric&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jan 2022 19:44:20 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/How-to-overcome-JMP-converting-very-large-numbers-to-scientific/m-p/452208#M69892</guid>
      <dc:creator>jthi</dc:creator>
      <dc:date>2022-01-18T19:44:20Z</dc:date>
    </item>
  </channel>
</rss>

