We have two joint accounts at Bank of America. Each account has a credit card associated with it. The credit cards are visible only in the account with which they are associated , so updating credit card transactions in Quicken requires separate logins into each of the two BofA joint accounts. ,
BofA today required reauthorization of our Quicken connection to its servers. Reauthorization worked, except for the credit cards. Credit cards for both BofA accounts already have transaction accounts in Quicken. A reauthorization request in either BofA account correctly does not see, or offer to reconnect to Quicken, credit cards associated with the other account. HOWEVER, on completion of the reauthorization process, an error dialog window pops up in Quicken, for transaction accounts associated with credit cards in the other BofA account, advising these credit cards were not found during the reconnection process and that associated transaction accounts in Quicken should be deactivated. AN ERROR FLAG then appears in Quicken next to these transaction accounts. The reauthorization process for the second BofA joint account, with which the now error flagged Quicken credit card transaction accounts are associated, DOES SEE AND RECONNECT these accounts in Quicken. HOWEVER, since the second BofA login does not see credit cards associated with the first of the two BofA accounts, now the credit card transaction accounts in Quicken associated with the first BofA account are ERROR FLAGGED, a catch 22.
Interestingly, the error flagged credit card transaction accounts in Quicken still show an activated online connection and do allow an update process with BofA. Makes sense, as BofA had authorized a Quicken connection for all credit card accounts, each after their respective BofA login. The reauthorization process worked, as far as BofA is concerned, for all accounts.
The GLITCH is the appearance of error flags in Quicken during this reconnection process , when there is no error. It seems the Quicken program's expects that all transactions accounts in a data file associated with a financial institution require only a single login. A second login to access different accounts at the same financial institution creates error
simple enough to fix. Why not simply replace the error flag with a warning that can be dismissed?
