Support Board
Date/Time: Fri, 20 Mar 2026 01:28:10 +0000
Post From: sc.GetTradeAccountData()
| [2026-02-08 16:58:56] |
| sirron - Posts: 3 |
|
Somewhat alarmed by your answer, “we know what the problem is”. sc.GetTradeAccountData worked in at least SC 2624. Somewhere between then and now SC pulled support for IB customers. Call me old fashioned, but I need to know how much money is available before I trade! I could potentially get it visually from TWS. But then I have to somehow get the value into ACSIL; ultra manual and defeats the reason for using ACSIL. Correct me if I’m wrong, but the end result is that people using IB will not be able to utilize any of the ACSIL trading functions in any sensible automated/semi-automated trading (can’t calc risk, size, etc). Such a shame, I’ve been using ACSIL trading functions with IB for years and they are superb. I think its fair to say, you're not members of the IB fan club. I’m sure you have your reasons and I’m not questioning them. But as a paying SC customer for over 18 years I’ve witnessed SC encounter all manner of problems not of your own making, yet impressively put in the effort to resolve them, or come up with novel solutions. So I’m very surprised at you pulling support for something that’s so fundamental. I’ve no intention of wasting both our time by banging on about this. If you have very few IB customers who use ACSIL functions to automate/semi-automate trading, then I guess it’s a sound business decision. But in an effort to persuade you to reconsider, I’ll leave you with this... … before sc.GetTradeAccountData came along (circa 2022), we had sc.TradeServiceAvailableFundsForNewPositions. It was very simple, did as it said, and worked with IB. Sure, it didn’t have all the whizzy fields of sc.GetTradeAccountData, but most of those fields could be considered nice-to-have, whereas available funds is essential. |