I am requesting MSFT 1 minute data for the last 7 days via the COM interface. I'm getting a result that looks like this (time,OHLC,vol,accvol):

1999-11-30 10:34:43,30.03,30.03,30,30,1200,1200
1999-11-30 10:34:43,30.03,30.03,30.03,30.03,1175,2375
1999-11-30 10:34:43,30.03,30.03,30.03,30.03,525,2900
1999-11-30 10:34:43,30.03,30.03,30.03,30.03,200,3100
1999-11-30 10:34:43,30.03,30.03,30.03,30.03,430,3530
1999-11-30 10:34:43,30,30,30,30,570,4100
1999-11-30 10:34:43,30.09,30.09,30.09,30.09,200,4300
1999-11-30 10:34:43,30.04,30.04,30.04,30.04,250,4550
1999-11-30 10:34:43,30.1,30.1,30.1,30.1,160,4710
1999-11-30 10:34:43,30.15,30.36,30.15,30.3,11324,16034

The error has been reproduced on two different machines running respectively the latest stable release and the beta version of your API. The error appears both when using your demo C++ examples (using Lookup1) and from C# where I do

_iqHistory = new DTNHISTORYLOOKUPLib.HistoryLookupClass();
_iqHistory.MinuteCompleted += new DTNHISTORYLOOKUPLib._IHistoryLookupEvents_MinuteCompletedEventHandler(_iqHistory_MinuteCompleted);
_iqHistory.MinuteProgress += new DTNHISTORYLOOKUPLib._IHistoryLookupEvents_MinuteProgressEventHandler(_iqHistory_MinuteProgress);
_iqHistory.RequestMinuteHistory("MSFT", 7, 1);

Over 400 other symbols that I have requested seem to produce good data. Using the Lookup2 interface on MSFT also gives good data.

Help would be appreciated. Thanks in advance.

Correction: The lookup2 interface gives good data but only for yesterday (2008-04-21) and not further back as does the socket interface. Lookup1 gives junk dates. How come?

Hello jacobi, I apologize for the delay responding. I am not seeing this issue today using the C++ example app. Are you still having problems?

No, the problem is not there anymore, neither using COM or sockets. I'm now getting the full amount of requested MSFT data without any errors.

Thanks.