What is the security symbol for 'Broadcom INC Cdr' for Quicken Canada ?

Michael 49
Michael 49 Member ✭✭✭

Quicken Classic Deluxe - version R55.15; Build 27.1.55.15; edition Canada; Windows 10 Pro
Browser: Firefox version 124.0.2 (32-bit)
Windows 10 Pro Version:10.0.19045

What is the security symbol for 'Broadcom INC Canadian Depository Receipts'?

Setting up the following security details doesn't download the daily quotes:

Symbol: AVGO

Type: Other

Currency: Canadian

Exchange: Toronto

Do not want to manually update from https://www.theglobeandmail.com/investing/markets/stocks/AVGO-NE/performance/

Best Answer

  • q_lurker
    q_lurker Quicken Windows Subscription SuperUser ✭✭✭✭✭
    Answer ✓

    Like you mention, it only imports the last price not the high/low/volume.

    I did not mention that.

    There are two approaches:

    1. The well documented within Quicken approach importing only closing prices using a simpler format of: Ticker, price, date. I believe that is also flexible enough that Ticker, date, price can work.
    2. Using a more complex syntax with hi, lo, and volume data included among a series of dashes. That is a singularly defined sequence as far as I know and not formally documented by Quicken.

    I did say that the first approach is often quite adequate; that the hi, lo, and volume data are of little to no value within Quicken.

    In my experience, both approaches work correctly when the import csv file is setup correctly. I am not in a position to identify what is wrong with your more inclusive csv file.

Answers

  • Ps56k2
    Ps56k2 Quicken Windows Subscription Alumni ✭✭✭✭

    is this it - https://finance.yahoo.com/quote/AVGO.NE/

  • Michael 49
    Michael 49 Member ✭✭✭

    Hi Ps56k2,

    AVGO.NE works for Yahoo but not Quicken. Changed the symbol from AVGO to AVGO.NE in the security details, then requested historical prices for the past month, but nothing changed.

  • NotACPA
    NotACPA Quicken Windows Subscription SuperUser ✭✭✭✭✭

    If you look at other threads on this forum … NEO doesn't currently support Q, which may be the issue here.

    Q user since February, 1990. DOS Version 4
    Now running Quicken Windows Subscription, Business & Personal
    Retired "Certified Information Systems Auditor" & Bank Audit VP

  • Michael 49
    Michael 49 Member ✭✭✭

    Hi NotACPA,

    I've come to the same conclusion going through various threads. I'm reluctantly importing the prices via .CSV, however, after editing the downloaded file from https://www.cboe.ca/en/live/security-activity/AVGO#!/history to the "symbol. closing price, —-, date. —-,high, low, volume/00, *" as suggested in the thread

    only the closing price for the first date is imported,not hi, low, volume or other dates.

  • q_lurker
    q_lurker Quicken Windows Subscription SuperUser ✭✭✭✭✭

    See if this FAQ clears up anything.

    Note that the hi/lo/vol data is not very valuable and the more common csv structure of

    Ticker, close, mm/dd/yyyy

    Is probably easier to get working.

  • Michael 49
    Michael 49 Member ✭✭✭

    Hi q_lurker

    The link you provided is one of the threads I checked. Like you mention, it only imports the last price not the high/low/volume. At the moment, it's better than nothing if importing a lot of historical data.

  • q_lurker
    q_lurker Quicken Windows Subscription SuperUser ✭✭✭✭✭
    Answer ✓

    Like you mention, it only imports the last price not the high/low/volume.

    I did not mention that.

    There are two approaches:

    1. The well documented within Quicken approach importing only closing prices using a simpler format of: Ticker, price, date. I believe that is also flexible enough that Ticker, date, price can work.
    2. Using a more complex syntax with hi, lo, and volume data included among a series of dashes. That is a singularly defined sequence as far as I know and not formally documented by Quicken.

    I did say that the first approach is often quite adequate; that the hi, lo, and volume data are of little to no value within Quicken.

    In my experience, both approaches work correctly when the import csv file is setup correctly. I am not in a position to identify what is wrong with your more inclusive csv file.

This discussion has been closed.