Login Page - Create Account

Support Board


Date/Time: Fri, 29 Mar 2024 05:24:02 +0000



Post From: Your Workaround to connect old version to CQG works well; Only backfill a problem

[2020-02-09 14:40:39]
User791263 - Posts: 151
I relied on your workaround of Instance2 V1488 in its' own folder; I assumed V1488 would not be able to trade, but I needed those 56 charts, 14 spreadsheets which could not upgrade past V1488 due to version changes handling of some studies(VbP and another)caused columns shifting. Conversion would take months.

V1991 as server and trade Instance worked well. V1488 had superior region-adjust and scaling (you were too busy to look into that, and not my main reason for 1488).

I now get a "forced update" to current, saying V1488 has a feed incompatibility. When I bypass/cancel update, everything seems to work fine.

Am I forced to stop what works well even if 1488 is not used to trade?
(I may update Inst-1 V1991 to V2018+, sticking with 32 Bit a year or so; Recompile is a hassle.)

For a long time, SC users could use old versions when necessary (though some risks of minor bugs) Many were using years-old versions.

Did sub-instance core data feed change so much it forces a new version? We realize the "front end" trading instance must be near-current.

Can't you keep some circa V2018 server-portion with newer everything else?
(like my current set up)

Does this forced upgrade assume only a Main trading instance?

Some users had no choice or preferred older versions. We know we can't go on for 5 years, but force to current Vers for sub-instance feels like Microsoft's forced Win10 push.