|
|
Re: Transaction retrieve usability suggestion[ Q2 03 - Q4 05 Archive ] [ Current Message Board ] [ Archives ] [ Search ] Posted by Mark on January 16, 2005 at 12:07:42:In Reply to: Transaction retrieve usability suggestion posted by George Timms on January 15, 2005 at 09:40:28: : When I checked some transactions downloaded from Vanguard, I found that the "Price" was the value they publish (rounded to the penny) for that date. : For as long as I've used FM, it has computed an extended-precision form (presumably based on internal floating-point implementation) of whichever of the "Shares" and "Price" fields I select last (using mouse or tab key). When entering transactions manually, I always round the "Price" (by selecting it last) to ensure FM accounting matches fund company records. In my experience, fund companys vary as to how many fractional digits they keep for shares, but I want/need my records to match the number of shares (regardless of transaction price) to avoid rounding errors. : My concern is that because none of the downloaded transactions have extended-precision prices, I might inadvertently recompute/change the number of shares later if I view (with no real intent to edit) a downloaded transaction. (This doesn't happen to me today because I make sure the stored prices are computed/stored with extended-precision) : Possible improvements: Do the extended-precision calculation for "price" when downloading transactions, or restrict extended-precision computations when editing a transaction to only the "price" field (maybe conditioned by a new investment attribute), or add a warning before storing an edited transaction that has recomputed the "shares" with extended-precision, etc.
I understand and share your concern about rounding errors. It is most Thanks,
|
FundManagerSoftware.com | Search | Site Map | About Us | Privacy Policy |
Copyright ©1993-2025 Beiley Software, Inc. All rights reserved. |