When you generate the report, assuming there's some US$ (or other non-CA$) securities, is "Transaction Exchange Rate" checked?WishingWealth wrote:Anyone has/had this issue and solved it?
Documentation explains how the software is supposed to work. Code explains how it actually worksPeculiar_Investor wrote:Real programmers don't write Help text, the functionality is what it is. Why should you need Help text?
When I used to report mainframe operating system bugs to IBM I gained some insights into what goes on behind closed doors in the kitchen. IBM would close my problem reports using various categories, e.g. "fix issued," "user error," "working as designed" and "documentation error." Working as designed meant that regardless of what the documentation said, according to the developers the software was working as they'd designed it (and "trust us" because the functional specs were confidential.) Documentation error meant that even if the documentation correctly described how the software was supposed to work, it was far easier to get the publications group to make the documentation agree with the code than it was to get the developers to make the code agree with the documentation. Documentation error was a favourite when a problem report uncovered a serious design flaw
Quicken's documentation and Help is even worse. ISTM they start with the US verbiage then change all US-isms to CA-ism, e.g. an IRA becomes an RRSP. IIRC I once even saw a reference to "Roth RRSP" Of course you'd expect that by now they'd translate it to TFSA. This is also why you'll see reports produced by Quicken that refer to short and long term capital gains or that allow you to compute capital gains using any of the methodologies that the IRS accepts even if CRA doesn't.