Invalid DateTime for 28/02/1900

AFL Programming
1

Hi,
I have historic data back to 1900. .SPX in my Metasctock database has a value for 28/02/1900.
When I run the Explore on .SPX it is all fine. When I create a ~Add to Composite with the date of 28/02/1900 i get Invalid DateTime.

All tickers created with ~Add to Composite have invalid date instead of 28/02/1900.
Does any one know a trick to solve this issue? /trick/setting, anything......

Any help would be welcome.
Regards

J

2

@jbenfeld, I don't know if you are aware, but there is a very well documented Excel/OLE related bug handling dates, that for compatibility reasons is also replicated at least in on AmiBroker function (specifically the DaysSince900() one). (See also this Wikipedia article).

This bug refers to a "phantom" Feb 29th, 1900, (that year WAS NOT a leap year).
So I cannot say if this is also the cause of the issue you are facing, but the fact that it is a day after the one that you indicated is at least a bit suspicious....

Unfortunately, I have no idea to handle your specific issue.

3

The date 28.02.1900 works fine in AmiBroker

I just went to Quote Editor, clicked (new), added artificial bar at 28.02.1900 and it worked perfectly fine:

image

Note that bar back in 1900 HAS TO BE "End-of-day" bar. Intraday data back in 1900 are not supported.

4

Thanks to both of you.

In my case the .spx works fine, but some indicatos cretaed with add to composite do have invalid date.

They are cretaed on a monthly time frame and pad and align to .SPX which has the corrcet date 28/02/1900. This is the code used:

Suffix=ParamList("Suffix","#|$|!|~|~~|~~~");
Buy=0; Sell=0;
BI=BarIndex()+1;
AddToComposite( BI, "#IND00", "X",1+4+8);

//===============
Filter=1; 
AddColumn( BI, "BI   ",1.1);
AddColumn( BI, "#IND00",1.1);

Capture2

Capture