(Canadian

Thanks. That is really odd since they are the same code. One possibility is it worked in an earlier version of the app but we accidentally broke it or our aggregator broke it in newer versions. Let me reach out to you directly to discuss.Gilles9 said:Conection to "National Bank of Canada new login" does not work for Quicken Connect
after updating my production datafile from 6.1.1 to 6.2
However it is working fine with the 6.2 beta datafile I used for testing ( the datafile used for testing the 6.2 beta was created from scratch by importing all my accounts from my production 6.1.1 datafile )
this is surprising as 6.2 released has the same version number as the last 6.2 beta
Now I use the Datafile created for testing beta 6.2 with the release version and it became my production datafile
Just for you to know, as I have deleted my former 6.1.1 datafile updated to 6.2 because the Quicken Connect did not work for that Financial institution.
It may be something you want to look at
Go to the help menu, and submit the issue via the report a problem. I've done that for several issues I've had.gojohn said:I have a problem that has been getting worse over time. While it's not directly related to the 6.2 release, I find that Quicken pauses for 5 seconds for each character I type in the Payees & Rules search box. Auto-completion of payees in the register is super fast. I've tried a number of suggestions based on replies in a thread I started <https://community.quicken.com/discussion/comment/20180034#Comment_20180034>; but nothing helps. Is there a way to open up a bug report on this?
Hi gojohn, quite honestly these forum posts right after we ship are the best way to get something on our radar. I'm not aware of any issue regarding search in the Payee screen but I'm guessing you might have a huge number of payees and we haven't done a good job of indexing or optimizing the search in that screen. I'll contact you offline to work with you directly.gojohn said:I have a problem that has been getting worse over time. While it's not directly related to the 6.2 release, I find that Quicken pauses for 5 seconds for each character I type in the Payees & Rules search box. Auto-completion of payees in the register is super fast. I've tried a number of suggestions based on replies in a thread I started <" rel="nofollow">https://community.quicken.com/discussion/comment/20180034#Comment_20180034>; but nothing helps. Is there a way to open up a bug report on this?
Yes, as I tried to make clear, I made a mistake and I don't fault Quicken for creating the new linked transaction. I was just describing the chain of events.jacobs said:@Just Lurking Creating the transfer to a different account did what it should have. There's no way for Quicken to know what account you're transferring to, so if you say Account X, I don't think there's any way it would be able to say "Are you sure you didn't mean Account Y, because you transferred funds there last month?"
My simple brain is asking why shouldn't Quicken know the difference between a downloaded transaction and a newly-Quicken-generated linked transaction? If I delete the "main" (downloaded") transaction, I can understand why the Quicken-generated linked transaction should also get deleted. I just never in my wildest dreams expected the reverse to be true. At the very least please give me a warning!jacobs said:
If you delete a linked transaction, it properly should disappear from both accounts. I understand this wasn't your intent, but again, if you delete the transaction, I'm not sure how it would have the smarts to say, "Hold on a sec -- do you want to delete the other side of this transaction, which came from a download?" If you have just a plain downloaded transaction, you can click and delete it. So I'm not sure why, or even how, you'd expect it to work differently if you've edited the transaction into a transfer to another account.
I had been planning on trying to download a single transaction as a Quicken or Quickbooks file from the FI, and then import that file into Quicken. Would that also not have worked because it would recognize the transaction ID as one that has been deleted?jacobs said:
If you had tried to download again, the transaction wouldn't have downloaded. That's by design: if someone deletes a transaction, they usually wouldn't want it popping back up the next time they download.
Yes that makes sense, it's just that historically I have been leery about manually entering transactions that should have downloaded because I was afraid there might be some useful information in the download that might be hidden or non-obvious that I neglect to recreate in the manual transaction. As I get more comfortable with Quicken I'm learning that that's probably not the case...jacobs said:But the simpler alternative to reverting to a backup, to me, would have been to simply enter the transaction manually. (Even if you had to quickly log onto the bank's website to check the amount, that seems easier to me than quitting Quicken, finding the most recent backup, restoring, it re-downloading, and trying to recall if you had done anything else in Quicken you need to re-do.)
jacobs said:...I think the misconception in your head is that there were two separate transactions, and that you could therefore delete one without affecting the other. I think the terminology "linked transaction" possibly contributes to this; it sounds like one thing is "linked" to another. In reality, a transfer transaction is simply a single transaction which exists in two places, rather than two transactions with something tying them together.
...
@smayer97 Hmmm... You're saying each account in Quicken would be its own table? That seems unlikely to me. Since there are an indefinite number of accounts a user can have, it seems highly unlikely that each would have its own table. I think all transactions* likely exist in one transaction table. For each transaction, one field would be the account, and another field would be if there is a linked account. Thus it could be one transaction, not two. The reason I could see for two transactions -- within the same table -- and a link ID to relate them would be if it made queries of the database for registers and reports significantly faster. But modern SQL database design generally tries to use joins and views to avoid the need for such duplication of data in multiple places, which can potentially get out of sync.smayer97 said:
Actually, unless the database is designed to have a separate table or create virtual entries in one table or register exclusively for "linked" transactions (which is unlikely as this would make the database and programming unnecessarily complex), linked transactions are actually 2 separate entries, one in each table or register and use a hidden identifier to link them together.
Hopefully I will remember in the future, but it would be nice if Quicken made it a bit more explicit in the user interface that changing (or deleting) one linked transaction will immediately change the one that lives in the other account as well!jacobs said:Part of the problem, perhaps, is from my naive perspective there was no obvious way to undo my mistake after I had created the wrong transfer. From experimentation, I now know that I can "unlink" a transfer by going to the originating transaction and removing the transfer category, but at the time, it seemed entirely logical to me to simply "delete" the errant linked transaction. I feel pretty strongly that at the very least Quicken should warn what will happen and not simply delete something silently.
I think once you understand this how what transfers work in Quicken, you won't have any confusion or concern in the future about how to correct an error.
That is very helpful; thank you. I had futzed around with the Inspector before, but it's very useful to understand that the five fields at the bottom are the only things imported in a downloaded transaction.jacobs said:I have been leery about manually entering transactions that should have downloaded because I was afraid there might be some useful information in the download that might be hidden or non-obvious that I neglect to recreate in the manual transaction. As I get more comfortable with Quicken I'm learning that that's probably not the case...Yes, there's absolutely no harm, downside, or reason to avoid entering a transaction manually. (I enter most of my transactions manually, but that's another story.) Click on one of your downloaded transactions and select View > Show Inspector (or Command-Option-i). The bottom part of the Transactions Inspector window shows you 5 fields of data exactly as imported from your financial institution, starting with the FITID. The top section shows all the fields as they exist in Quicken.
Just FYIdebbeh said:Hi Quicken,
This still did not solve my connectivity to TD Canada Trust, which is not working since Nov.
waiting for the fix to have the Auto download working again.
Please fix this.