Symbol lookup when adding a new security cannot find a valid ticker MFC.PR.C on the TSE
Unknown
Member
Valid symbol on TSE MFC.PR.C is not working MFC-C does not work either, Any suggestions
0
Comments
-
Hi @ Jean-Marc Arsenault ,
See this Article: https://getsatisfaction.com/quickencommunity/topics/add-your-quicken-information-to-your-posts-plus-...
You have not include any information on your operating system or Quicken version.thecreator - User of Quicken Subscription R53.16 USA
Windows 10 Pro 32-Bit Build 19045.3693
Windows 10 Pro 64-Bit Build 19045.3754
0 -
Additional information to open problem: Using Home & Business 2016 Canadian version recently updated last week. The problem happens on manual input of a security purchase. See symbol on MSN Money https://www.msn.com/en-us/money/stock...0
-
Bonjour Jean-Marc - I think you are trying to find a preferred stock? They are much, much harder to get a working ticker for. This is not a Quicken application problem; it's that preferred stocks do not trade much (in the US, anyway), and also if it's a new issue it might not be out there yet. Are you downloading from a brokerage account? or entering things manually?Jean-Marc Arsenault said:Additional information to open problem: Using Home & Business 2016 Canadian version recently updated last week. The problem happens on manual input of a security purchase. See symbol on MSN Money https://www.msn.com/en-us/money/stock...
0 -
Don't recall a quicken for Mac home & business application0
-
Entering manuallyJean-Marc Arsenault said:Additional information to open problem: Using Home & Business 2016 Canadian version recently updated last week. The problem happens on manual input of a security purchase. See symbol on MSN Money https://www.msn.com/en-us/money/stock...
0 -
Yes you are right I entered on MAC tab by error. I am working on Windows 100
-
Tested this, appears to work. Just stumbled across this post looking for something else Canada related.
TSE:MFC-CQuicken user since 1994.
Quicken Forum/Community Contributor since 2005.0
This discussion has been closed.