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, there is no need to make it an option.
2. TWS.Connect I don't know but yes you have to set the port appropriately.
The default port will be different in gateway than TWS, but if you've looked
in API - Settings you should have seen and had the opportunity to set the
port number and it should be no mystery. You can make the port number the
same as TWS if you like, and your setting will be remembered.
3. I don't use ActiveX but it is all the same socket. The Gateway is no
different from TWS in fundamental behavior. The system behavior is
different in various well-known ways, such as the fact that the gateway lets
you stay connected without your having to fight for it. There are probably
also subtle differences owing to the fact that they are different
executables and also are not necessarily released at the same time, so that
bugs may be different.
-Kurt
toggle quoted message
Show quoted text
On 7/19/13 12:05 AM, "Edbar" <edbar@...> wrote:
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 check "enable
activex and socket clients". But I notice that options isn't even there inte
gateway configuaration.
2. Do I have to change the TWS.Connect line to connect to the gateway vs
connecting to tws? My connect isn't working and I'm wondering if I have to
change the port. I've already got the gateway logged in and running but the
program doesn't connect to it.
3. Will all the tws activex methods and events work the same with the gateway
as they did with tws?
Thanks,
Ed
