Forum Discussion
Not a legal OleAut date..
Hi
I solved this problem!
It was a date that I used in a relationship called DueDate, I found a value that was 05/05/0016 and this value was causing traoubles on scheduled refresh.
So, look all your date values, try sorting and checking de min and max value of each field.
Regards
Rodrigo
Thanks Anonymous for your post! You helped me out.
I had the same error message. And indeed some of my dates ware having strange values, like 01-01-0015 and 01-01-0215. These should have been 01-01-2015. After I changed the data the refresh worked.
In my case these dates were not used in a relationship.
- sweidlich8 years ago
Advocate II
(I wanted to add to this, in case other people google this and find this...)
The messed up years were proving to be the issue for me, too. Fortunately, there were only a few (0997 should have been 1997, etc.). And I was able to add some steps to the query to replace the values with the correct date. This kept me from changing column number types back and forth.