Sorry if blunt, no intent
but IMHO and using my limited experience of IBKR I feel the need to share the feeling that you are "swimming against the flow".
?
1- Development should start easy and gradually increase in complexity,
Here it look to me you have a first mandatory daunting task to overcome, to create a non existing ABI lib for another language, able to do the telecom with the IBKR ABI,
And extend this later taking control and experiment the API itself (not a minor task and requiring a lot of trials)
All of this without any examples or help or support.
Then and only then will you be able to focus yourself on your algo.
?
2- Although this business require well designed and safe code, a loosely type language like Basic is not a way to make your future life simple.
You also increase the odd of uncontrolled polymorphic calls that could create hard to diagnose side effect.
(I already get bad feeling with your code that morph "clientid" to a string)
If your aren't familiar with C++ from your embedded system experience, go for Java, surely a strongly type language and also the best portable solution (I wonder why do you need to design a cross platform, solution)
?
3- I don't understand your terminology, what IBKR codes are you calling the "windows socket solution" ?
hints: the IBKR Client code sample ?
Where did you get the "TWSlib.dll" ? I just don't remember if IBKR does supply a precompiled binary.
note: this may show how difficult it could be to give help if you don't comply with a standardized terminology, by default the IBKR API convention
?
Last:
Why don't you consider a mix with another REST data oriented vendor and using IBKR Web API (a REST API) ?
It is surely more easy to implement and debug.
?
?
?
