开云体育

JP, I had figured out that I had to call that particular sub-routine to request updates but my problem is slightly different (which I realised I have not articulated correctly in my original

It appears that the default behavior (if you don't specify ocaType) is non-blocking, reduce proportionally. If I don't specify ocaType, I get the behavior as you described. And if I set ocaType to 3

I actually haven't researched scenarios with multiple contracts or more than 2 orders in the oca group. I use separate orders (and oca groups) for 1 contract each which allows separate prices for

The ocaType is in the C++ API documentation for the Order structure (also in IOrder for ActiveX and I assume similar for other languages). There are 2 blocking types, which guarantee that only 1 order

Hmm. I use oca all the time and the limit orders are on the exchange. I didn't know there were 'oca types' so maybe that changes how orders are handled. If you use the default oca type do you

When I mouse over the profit exit, it says the order is being held and monitored just like the stop order. The row for the order on TWS shows the status column as dark blue, where if I place a single

Limit orders are native to globex so your profit exit will be at the exchange. This has nothing to do with oca. The stop is not native so it must be simulated by ib. If you mouse over the profit

I'm working on using OCA for my profit and loss orders. It appears that once I set the orders up with an OCA group, they aren't actually sitting at the exchange but rather are on an IB server waiting

This is the method you should call to request account updates objTWSControl.m_TWSControl.reqAccountUpdates(True, accountName) If you are managing more than one account, make sure to use the right

I mainly suggested you choose wisely for your own needs. If synchronization *is* a bitch and you are using 2 threads and one handles incoming socket messages and the other is handling incoming GUI

Hi Brian :), Kurt, Thanks so much for your help! I will limit myself to just two threads and actually based on also Kurt's comment synchronization can be a bitch so I rather have two open connections

I don't know VB, but think it doesn't matter. 1. In all fundamental ways, Gateway works the same as TWS in terms of connections. Since the Gateway has no purpose except to connect to API clients,

I haven't used the gateway yet, but was wondering a few things: 1. Is any pre-configuration required to connect to the gateway from the VB6 program? For instance with TWS you had to go into tws and

It is 7/18, and I just noticed the recently slow contract details behavior seems to have reverted back to what it was previously. -Kurt

not sure of your problem but getting a full option chain for the underlying was never a problem for my code the biggest problem was getting all the details and it timing out. nick

Sorry, I've been away. That looks fine, I'm happy that I've got what I need now to download data, havn't been able to retrieve an option chain but I've come up with a workaround that is quicker.

This has indeed been fixed for live and paper trading accounts, but not for edemo

I use TwsActiveX.xls excel sheet to connect to IB Gateway. The connection between IB Gateway and TwsActiveX.xls is fairly stable. However, on occasions when IB Gateway loses connection to IB Server,

Call me brian :). I have no idea how to change that login name. If you scroll down in Example1.java you will see the tickPrice method. This is overriding the method of the same name in

Hi, Breaking in, I have a vague memory there may be people who said they open multiple connections in order to have a dedicated thread for each, but it is highly unusual and probably not