Is there a known issue with specifying time and date filters in the History3 COM interface? I'd rather not have to request more data than I need and trim it down after I get it back.

As a quick example I tried to request the last 60 minutes of 1-minute data for SPY.

BeginDateTime = "";
EndDateTime = DateTime.Now.ToString("yyyyMMdd 160100"); // Also hard-coded "20100315 160100"
BeginFilterTime = "093100";
EndFilterTime = "160100";

I keep getting after-hours data. Am I doing something wrong? I see the same results in the IQFeed History Viewer diagnostic app as well.

Thanks,
Eric

Eric, I do not see the issue here when using the history viewer. Can you tell me exactly which parameters you are passing into the request for all fields or exactly what you are specifying in the HistoryViewer?

Here is an example assuming this attachment works.

I did notice that if I do NOT specify the number of bars to return, it works correctly. However I'd rather not spend the time coding all that. In this example, I want the last 120 1-min bars DURING MARKET HOURS. As you can see, it start a few minutes before the close and return everything it has. The filtering has no effect when I tell it how many bars I want.

Eric

This is a known issue. Combining the Oldest to Newest flag with the number of datapoints parameter causes unexpected results. It will be fixed in an upcomming server release.

Until then, I can only recommend using one or the other and doing the extra filtering on your end.

Excellent, that's great to know. For now I'll just request them backwards and reverse the collection before shooting the result to my requesting app.

Thanks!