Search results

Please contact the customer service. Thanks.

Followup: We moved the Sep 16 date to Sep 19. The date only affects builds lower than 832.

The key is in the very first sentence of the thread: "My TWS ( build 831.9 ) just told me, that i need to upgrade, because it wont be supported after 16, September." The 831.9 is quite old and had been scheduled to be desupported for a while. The magic date for that version was Sep 16...

Historical Market Data Server - charting data. Could you clarify how the templates should be changed?

Should it be the case that there is a significant problem with 851, we will fix it before we will de-support the earlier versions. As to the existence of this silly poll: what we are trying to avoid is the situation we had some 2-3 weeks ago. Namely, our ISP went down and we automatically...

If what you are doing is: a) observe the market-data and quickly react to its changes by hitting bids and lifting offers b) doing the a) w/ the computer and the decision logic runs on the computer in Australia you will be disadvantaged to the users who reside in Europe. You are at a...

We'll check. Thanks.

I suggest you try IB's "rapid order entry" or "book trader".

In an earlier post I prompted you to give us some specifics, but nothing arrived...

It was working yesterday (the first business day of the week) as promissed and it is working now.

Looks like a chart popup, not related to the API functions. I thought the issue was that you don't want pop-ups on activities related to API functionality. Did I misunderstand? (In the latest TWS version we have disabled a lot of API related popups).

2. I wish everyone took the responsibility for their actions the way you seem to. 3. Some examples of what the system does: - The market data is being constantly checked for staleness. The stale pieces are automatically hidden from the smart router. - When an exchange stops acking orders...

2. It seems a fine financial security measure to me. Assume you build an application that slowly trades away. A bug slips into your code, or our code, or we modify how a feature works. As a result of this your application starts bleeding money, albeit slowly. I very much like the fact that...

Do you use IB's smart leg-in combinations to execute the straddles/strangles? In case you don't, I suggest you give it a try.

We'll check it. Thanks.

Our reasons for not allowing the user to just remove any exchange they want don't have to do with the ease of coding. It is a business decision. Unless I get convinced with the statistics to allow for the removal of PHLX, I can only recommend to you to use directed routing. Sorry.

Yes, it is a crazy idea. We are a privately owned company and plan to remain so for the time being. While we very much like to see the requests and suggestions made by our clients, we will continue to make the final decision as to whether, what and when something gets implemented.

The glitch has been acknowledged in a different thread. It will be corrected for the next business day. Sorry for the inconvenience.

This thread is becoming a discussion about a glitch that: - has been acknowledged, and - will be corrected for the next business day. I would much rather it remained dedicated to its original purpose. Thank you.