Page 1 of 1
bloomberg db import calendar error
Posted: Tue Dec 23, 2014 5:15 am
by jgutman
Hi
When importing data from Bloomberg, I occasionally get the following sort of error:
"Database Error: Bloomberg library error: 'The DateTime represented by the string is not supported in calendar System.Globalization.GregorianCalendar.' in "COPY(LINK) CURNCY::"KRW" KRW."
This happesn for eg KRW, BRL, and CLP, but not other currencies like CNY, EUR, JPY, MXN, etc. The page freq is d5. Has anybody else seen this error?
Thanks, and happy holidays!
Re: bloomberg db import calendar error
Posted: Tue Dec 23, 2014 12:37 pm
by EViews Jason
What is the build date of your copy of EViews (help->about EViews)?
I am not able to replicate the problem.
I however used
Code: Select all
copy(link) Bloomberg::"krw curncy" krw
whereby 'Bloomberg' is an entry in my EViews database registry (options->database registry).
Re: bloomberg db import calendar error
Posted: Wed Dec 24, 2014 7:08 am
by jgutman
25 nov 2014 is the build date
it is quite odd, because I get the same error when I drill down into the Bloomberg database via the browse function
it also refuses to download in any frequency of workfile
I wonder if I have the date setting in eviews somehow misconfigured?
thank you
Re: bloomberg db import calendar error
Posted: Wed Dec 24, 2014 11:09 am
by EViews Jason
It should not matter and if it does we will fix it.
Select Options->general options and choose Date representation from the left side column. I have Month/Day/Year and Frequency delimiter set.
Re: bloomberg db import calendar error
Posted: Mon Jan 05, 2015 7:24 am
by jgutman
Hope you had a good holiday
Alas, changing the date representation doesn't change the outcome -- the same series come up with the same error message
Re: bloomberg db import calendar error
Posted: Tue Jan 06, 2015 9:29 am
by EViews Jason
Send an email to
support@eviews.com with a reference to this forum topic. We will have to work offline to figure out what is going on.
Re: bloomberg db import calendar error
Posted: Mon Feb 02, 2015 8:31 am
by EViews Jason
The fix was added to the January 12 EViews 8.1 Patch. If you download the latest patch via help->EViews update and type 'regcomponents' and press the enter key into the command window, you should find the issue has been resolved.