6 New Messages
Digest #2955
Messages
Mon Feb 3, 2014 7:35 pm (PST) . Posted by:
e_bartsch
I have two problems I hope the group can solve.
First, Element 886 (MorningtarT Take -- Consider Buying) does not seem to be working. It is returning "Error." I am logged onto my Morningstar account via Internet Explorer before I launch Excel and run the add-in.
Second, I have a spreadsheet that calculates potential near-month spreads. Before the advent of weeklies, it worked well. I simply pulled "OTM1" values for the short leg and "OTM2" values for the long leg of the spread. Now, however, and depending on the underlying, "OTM1," "OTM2," "OTM3" etc. return different strike dates and strike prices that vary with the date on which I calculate the spreadsheet and the security.
I would like to reprogram the spreadsheet so that, no matter the security or date, I always get the same near-month strike date values for the short OTM1 and long OTM2 legs of a near month spread. Any way to solve this problem?
Thanks.
Eric
First, Element 886 (MorningtarT Take -- Consider Buying) does not seem to be working. It is returning "Error.
Second, I have a spreadsheet that calculates potential near-month spreads. Before the advent of weeklies, it worked well. I simply pulled "OTM1" values for the short leg and "OTM2" values for the long leg of the spread. Now, however, and depending on the underlying, "OTM1," "OTM2," "OTM3" etc. return different strike dates and strike prices that vary with the date on which I calculate the spreadsheet and the security.
I would like to reprogram the spreadsheet so that, no matter the security or date, I always get the same near-month strike date values for the short OTM1 and long OTM2 legs of a near month spread. Any way to solve this problem?
Thanks.
Eric
Mon Feb 3, 2014 8:01 pm (PST) . Posted by:
"Randy Harmelink" rharmelink
Hmmm. #886 is "Fair value" and "Consider Buying" is #887. In any case, both
are working fine for me, so I'm not sure what to tell you. I'm assuming you
do have the latest element definitions. Can you see the data if you go to
this web page using the EXCEL Web Query dialog (keyboard shortcut
alt+d+d+w):
http://quotes.morningstar.com/stock/c-morningstar-take?t=MMM
The best way to get the ITM and OTM strike prices is the
smfGetOptionStrikes() function. But I'm not sure I understand what issues
you're running into. First OTM and ITM prices can vary, depending on the
expiration date.
On Mon, Feb 3, 2014 at 8:35 PM, <eabartsch@comcast.net> wrote:
> I have two problems I hope the group can solve.
>
> First, Element 886 (MorningtarT Take -- Consider Buying) does not seem to
> be working. It is returning "Error." I am logged onto my Morningstar
> account via Internet Explorer before I launch Excel and run the add-in.
>
> Second, I have a spreadsheet that calculates potential near-month
> spreads. Before the advent of weeklies, it worked well. I simply pulled
> "OTM1" values for the short leg and "OTM2" values for the long leg of the
> spread. Now, however, and depending on the underlying, "OTM1," "OTM2,"
> "OTM3" etc. return different strike dates and strike prices that vary with
> the date on which I calculate the spreadsheet and the security.
>
> I would like to reprogram the spreadsheet so that, no matter the security
> or date, I always get the same near-month strike date values for the short
> OTM1 and long OTM2 legs of a near month spread. Any way to solve this
> problem?
>
are working fine for me, so I'm not sure what to tell you. I'm assuming you
do have the latest element definitions. Can you see the data if you go to
this web page using the EXCEL Web Query dialog (keyboard shortcut
alt+d+d+w):
http://quotes.
The best way to get the ITM and OTM strike prices is the
smfGetOptionStrikes
you're running into. First OTM and ITM prices can vary, depending on the
expiration date.
On Mon, Feb 3, 2014 at 8:35 PM, <eabartsch@comcast.
> I have two problems I hope the group can solve.
>
> First, Element 886 (MorningtarT Take -- Consider Buying) does not seem to
> be working. It is returning "Error.
> account via Internet Explorer before I launch Excel and run the add-in.
>
> Second, I have a spreadsheet that calculates potential near-month
> spreads. Before the advent of weeklies, it worked well. I simply pulled
> "OTM1" values for the short leg and "OTM2" values for the long leg of the
> spread. Now, however, and depending on the underlying, "OTM1," "OTM2,"
> "OTM3" etc. return different strike dates and strike prices that vary with
> the date on which I calculate the spreadsheet and the security.
>
> I would like to reprogram the spreadsheet so that, no matter the security
> or date, I always get the same near-month strike date values for the short
> OTM1 and long OTM2 legs of a near month spread. Any way to solve this
> problem?
>
Mon Feb 3, 2014 8:04 pm (PST) . Posted by:
mikemcq802
For the M* problem, try using the Excel Web Query to bring up www.morningstar.com. It's in the Data tab, then From Web. You don't have to do anything, just bring up the website home page. Then, exit Excel and restart. The Web Query seems to set security cookies in a different manner than using IE which I've had to do to get other M* elements. Don't know why some require this and others not - just that it's worked for me. I need to do this every day for certain elements.
Mon Feb 3, 2014 8:11 pm (PST) . Posted by:
"Randy Harmelink" rharmelink
I thought the only time that happened is when there is a mismatch between
the installed IE browser and what object EXCEL uses. That is, when they are
two different version of EXCEL, using different cookies and temporary
storage.
But I don't use IE as a browser, so I *always* use the EXCEL Web Query
dialog to log in to web sites, or to satisfy their "first visit of the day"
redirections for potential advertising or special notices.
Also, you shouldn't need to exit and restart EXCEL. Just run the
smfForceRecalculation macro and the add-in will get fresh copies of any
needed web pages.
On Mon, Feb 3, 2014 at 9:04 PM, <mikemcq802@yahoo.com> wrote:
> For the M* problem, try using the Excel Web Query to bring up
> www.morningstar.com. It's in the Data tab, then From Web. You don't
> have to do anything, just bring up the website home page. Then, exit Excel
> and restart. The Web Query seems to set security cookies in a different
> manner than using IE which I've had to do to get other M* elements. Don't
> know why some require this and others not - just that it's worked for me.
> I need to do this every day for certain elements.
>
the installed IE browser and what object EXCEL uses. That is, when they are
two different version of EXCEL, using different cookies and temporary
storage.
But I don't use IE as a browser, so I *always* use the EXCEL Web Query
dialog to log in to web sites, or to satisfy their "first visit of the day"
redirections for potential advertising or special notices.
Also, you shouldn'
smfForceRecalculati
needed web pages.
On Mon, Feb 3, 2014 at 9:04 PM, <mikemcq802@yahoo.
> For the M* problem, try using the Excel Web Query to bring up
> www.morningstar.
> have to do anything, just bring up the website home page. Then, exit Excel
> and restart. The Web Query seems to set security cookies in a different
> manner than using IE which I've had to do to get other M* elements. Don't
> know why some require this and others not - just that it's worked for me.
> I need to do this every day for certain elements.
>
Mon Feb 3, 2014 8:19 pm (PST) . Posted by:
mikemcq802
I can't explain it. I'm only running Excel 2010 and IE 11 on this machine. I have to use Web Query daily for some M* items. IE isn't sufficient. If there's a way to "reconnect" them I'd appreciate any tips.
I'm happy to use smfForceRecalculation but wasn't sure the OP was so gave him the easiest way.
I'm happy to use smfForceRecalculati
Mon Feb 3, 2014 9:11 pm (PST) . Posted by:
mikemcq802
FWIW, on my SurfacePro2 with Win8.1 and Excel 2013, I get the exact same issues with certain M* elements (884, for example). That is a fairly clean install with mostly default settings and no prior versions of anything.
I can even duplicate this issue outside of SMF - it seems related to XMLhttp. I have a simple com app using XMLhttp written in Powershell. It just uses an open and send to do a simple GET.
Each day, if I use it to access http://www.morningstar.com I get an "access is denied" exception. I can access the website just fine in IE - both as http: and https: and it renders fine. But, XMLhttp will keep throwing "access is denied" until I use Excel Web Query at which time the data is returned normally.
I only have this issue with the main domain website - www.morningstar.com. I can access the quicktake, bond, and quotes subdomain sites (i.e., quotes.morningstar.com) just fine with SMF and my XMLhttp app without prior use of Excel Web Query that day.
I can even duplicate this issue outside of SMF - it seems related to XMLhttp. I have a simple com app using XMLhttp written in Powershell. It just uses an open and send to do a simple GET.
Each day, if I use it to access http://www.mornings
I only have this issue with the main domain website - www.morningstar.
Tidak ada komentar:
Posting Komentar