DTN IQFeed, DTN.IQ, DTN ProphetX Support Forums

Join the 80,000 other DTN customers who enjoy the fastest, most reliable data available. There is no better value than DTN!

(Move your cursor to this area to pause scrolling)

"Boy, probably spent a thousand hours trying to get ******* API to work right. And now two hours to have something running with IQFeed. Hmmm, guess I was pretty stupid to fight rather than switch all this time. And have gotten more customer service from you guys already than total from them… in five years." - Comment from Jim

"I am enjoying the feed very much - so superior to the broker provided feed I was previously using." - Comment from George

"After all the anxiety I had with my previous data provider it is a relief not to have to worry about data speed and integrity." - Comment from Eamonn

"IQ feed is brilliant. The support is mind-bending. What service!" - Comment from Public Forum Post

"I have to tell you though that using the IQFeed API is about the easiest and cleanest I have seen for some time." - Comment from Jim

"I ran your IQFeed DDE vs. my broker vs. a level II window for some slow-moving options. I would see the level II quote change, then your feed update instantaneously. My broker's DDE, however, would take as much as 30 seconds to update. I am not chasing milliseconds, but half a minute is unacceptable." - Comment from Rob

"As a past ******* customer(and not a happy one), IQ Feed by DTN is a much better and cheaper product with great customer support. I have had no problems at all since switching over." - Comment from Public Forum

"I noticed that ******* quotes locked up shortly after the interest rate announcement yesterday while yours stayed stable." - Comment from Ron in Utah

"I have been using IQFeed now for a few years in MultiCharts and I have zero complaints. Very, very rare to have any data hiccups or anything at all go wrong." - Comment from Public Forum

"I'm very glad I switched to IQFeed. It's working perfectly with no lag, even during fast market conditions." - Comment from Andy via Email

Home

Recent Posts

Information on DTN's Industries:
DTN Oil & Gas | DTN Trading | DTN Agriculture | DTN Weather

DTN.IQ/IQFeed on Twitter
DTN News and Analysis on Twitter

»Forums Index »Archive (2017 and earlier) »IQFeed Developer Support »Feature Request: Historical via COM...

Author	Topic: Feature Request: Historical via COM... (6 messages, Page 1 of 1)
dis -Interested User- Posts: 24 Joined: Apr 16, 2007	Posted: Jun 4, 2007 10:23 AM Msg. 1 of 6 Suggestion is following: Raise an event in case when no data available for the requested interval. Now my calling thread is sleeping up to timeout (20 seconds - 1 minute for me). It would be great if the event would inform about it immediately. It is very important for my application. Many thanks for your consideration.
DTN_Steve_S -DTN Guru- Posts: 2093 Joined: Nov 21, 2005	Posted: Jun 4, 2007 10:28 AM Msg. 2 of 6 Can you give me an example of the request you are making?
dis -Interested User- Posts: 24 Joined: Apr 16, 2007	Posted: Jun 8, 2007 07:07 AM Msg. 3 of 6 HistoryLookupClass.RequestMinuteHistory("MSFT", 1, 1); The situation reproduces if I'm doing such request on Monday morning (or holidays...), because there is no historical data.
DTN_Steve_S -DTN Guru- Posts: 2093 Joined: Nov 21, 2005	Posted: Jun 8, 2007 09:31 AM Msg. 4 of 6 What you are requesting is actually the intended functionality of IQFeed. You are experiencing a bug that is specific to the HistoryLookup interface. It does not exist in the HistoryLookup2 interface or in the sockets interface.
dis -Interested User- Posts: 24 Joined: Apr 16, 2007	Posted: Jun 8, 2007 10:29 AM Msg. 5 of 6 I'm not experiencing a bug, I'm offering you to enhance it a bit so that the AbortLoad event needs to be raised in some additional case, or MinuteProgress event brings 0 bars loaded in its event args in case if there is no data on the requested interval. This does not require the changes in the interface.
DTN_Steve_S -DTN Guru- Posts: 2093 Joined: Nov 21, 2005	Posted: Jun 8, 2007 10:38 AM Msg. 6 of 6 I never said that it required changes to the interface. I simply said that this interface is the only interface affected. The fact that the request takes a LONG time to return an error in the given scenario, IS the bug. It is due to a combonation of factors involving the communication with the servers. It will be fixed in an upcomming release of IQFeed.