-1

I have a function named currency. It takes a parameter A which is a currency like "EUR/USD" . Then I do this: n<-getSymbols(A,src = "oanda",from = "2016-01-01",to = Sys.Date(),auto.assign = FALSE) The paradox is that the program was running fine 2 days ago. The error message is: Error in charToDate(x) : character string is not in a standard unambiguous format.

This is the traceback()

Thanks in advance!

mike
  • 1
  • Please post your code, marked as code (click the {} when editing). For dates, take a look at package `lubridate` which has robust functions for date parsing, such as , `ymd`. It is best to follow the posting guidelines in [reproducible example](http://stackoverflow.com/questions/5963269/how-to-make-a-great-r-reproducible-example) – Andrew Lavers Apr 09 '17 at 12:31

1 Answers1

0

I think that this a duplicate

quantmod::getFX function returns "character in a standard unambiguous format"

In any case, I followed the code of the getSymbols.oanda and it seems that oanda changed their API so instead of downloading a .csv you get a .xml file.

Speaking for me, I will go for a different source for the data until this is resolved by the quantmod guys.

Community
  • 1
  • 1
sen_saven
  • 182
  • 12
  • actually the fix is already out, try this command: devtools::install_github("joshuaulrich/quantmod@144_getFX") – sen_saven Apr 11 '17 at 07:53