tag:infinitekind.tenderapp.com,2009-01-14:/discussions/investments/4595-decimal-places-in-share-unitsInfinite Kind: Discussion 2019-09-20T12:48:15Ztag:infinitekind.tenderapp.com,2009-01-14:Comment/475357142019-08-18T14:17:30Z2019-08-18T14:17:30ZDecimal places in share units<div><p>Hi Adam,</p>
<p>Thank you for providing your version of Moneydance and your computing environment.</p>
<p>The number of decimal places for a security is determined when the security is created and cannot be changed after the fact.</p>
<p>-Kevin N. (not a member of MD support)</p></div>-Kevin N.tag:infinitekind.tenderapp.com,2009-01-14:Comment/475357142019-08-18T14:52:33Z2019-08-18T14:52:33ZDecimal places in share units<div><p>Okay, thank you. So what is your recommendation? Delete the security and re-add it? If so, what would that do to the transactions I already have with the security associated to it?</p></div>adamtag:infinitekind.tenderapp.com,2009-01-14:Comment/475357142019-08-18T15:29:52Z2019-08-18T15:29:52ZDecimal places in share units<div><p>Hi Adam,</p>
<p>I'm afraid that there is no elegant way to resolve this issue.</p>
<p>You will not be able to delete the security while it is in use. e.g. the security is used in transactions and / or reminders.</p>
<p>Something that you may be able to do to make the process a little easier is to rename the 'old' security to something that can be easily seen in the register. e.g. rename the security to 'DELETE THIS SECURITY'. Then create a 'new' instance of the security in question (with the desired decimal places) and mimic the 'new' securities transactions in the register with the old security. You can then, one-by-one delete the 'old' security transactions and eventually delete the 'old' security altogether.</p>
<p>Safe computing 101 dictates that you make a copy or make sure to have a working backup of your data file before making any drastic changes (especially deletions).</p>
<p>-Kevin N. (not a member of MD support)</p></div>-Kevin N.