The Problem (Q-score 7, ranked #225th of 303 in the Excel VBA archive)
The scenario as originally posted in 2013
I have to download historical end of day data for a huge list of stocks. I found on the bloomberg excel add-in the function BDH that is very useful. That is what I need but there is an issue: my stocks are identified by ISINs and i have tried in many way to put the ISINs in the first field of the function but it doesn’t work. The function isn’t able to identify the security by the ISIN despite the fact that is reported as security identifier in the bloomberg formula syntax: look at slide 24 here http://lgdata.s3-website-us-east-1.amazonaws.com/docs/205/56376/bloomberg%20excel%20desktop%20guide.pdf
Why community consensus is tight on this one
Across 303 Excel VBA entries in the archive, the accepted answer here holds niche answer (below median) status — meaning voters are unusually aligned on the right fix.
The Verified Solution — niche answer (below median) (+6)
Verbal answer — walkthrough without a code block
Note: the verified answer is a prose walkthrough. If you need a runnable sample, check Excel VBA entries ranked in the top 10 of the same archive.
The problem is that an isin does not identify the exchange, only an issuer.
Let’s say your isin is US4592001014 (IBM), one way to do it would be:
-
get the ticker (in A1):
=BDP("US4592001014 ISIN", "TICKER") => IBM -
get a proper symbol (in A2)
=BDP("US4592001014 ISIN", "PARSEKYABLE_DES") => IBM XX Equitywhere
XXdepends on your terminal settings, which you can check onCNDF <Go>. -
get the main exchange composite ticker, or whatever suits your need (in A3):
=BDP(A2,"EQY_PRIM_SECURITY_COMP_EXCH") => US -
and finally:
=BDP(A1&" "&A3&" Equity", "LAST_PRICE") => the last price of IBM US Equity
When to Use It — classic (2013–2016)
Ranked #225th in its category — specialized fit
This pattern sits in the 98% tail relative to the top answer. Reach for it when your scenario closely matches the question title; otherwise browse the Excel VBA archive for a higher-consensus alternative.
What changed between 2013 and 2026
The answer is 13 years old. The Excel VBA object model has been stable across Office 2013, 2016, 2019, 2021, 365, and 2024/2026 LTSC, so the pattern still compiles. Changes that might affect you: 64-bit API declarations (use PtrSafe), blocked macros in downloaded files (Mark-of-the-Web), and the shift toward Office Scripts for web-first workflows.