I just set up IB TWS with eSignal so I could get more data coming in (more symbols). TWS seems to operate just fine with the eSignal data, but when I use my Visual Basic API it makes the initial connection to TWS without any problems, but then seems to lose the connection right away. When I try to retrieve data in Visual Basic, say on SPY, the errMsg event comes back and says it's not connected. If I change the TWS configuration back to receiving IB data (instead of eSignal) the API works fine again. It seems like it shouldn't make a difference to the API how TWS is getting it's data. As long as TWS is running properly, the API should run properly. If anyone has any experience with this, any ideas would be much appreciated. Thanks.