Support Board
Date/Time: Fri, 07 Feb 2025 19:04:59 +0000
Upgrade broke studies
View Count: 629
[2020-06-09 20:52:34] |
rhovega - Posts: 279 |
Hi. Just uprgaded to latest version. Had not updated in about six months or so. Updating "broke" my custom studies. error code 126, specified module could not be found. Did not change the data folder, and checked that indeed updating did not change the data folder location. Need help to fix this please. Date Time Of Last Edit: 2020-06-09 20:52:43
|
[2020-06-09 21:43:19] |
Ackin - Posts: 1865 |
Hi, Statically linking to the C++runtime lib or not? I don't know what operating system you are using, but Win10 + new ver SCH is a problem for a few of my colleagues. If the studies are yours, recompile them again. In the last few months, the changes have been large only in "def time" and "persistant vars". That would give you another error. I would really try to recompile it with the current ver sierrachart. Then you'll need also this: Notice: Study Exceptions in New Versions and Code Efficiency Notice: Study Exceptions in New Versions and Code Efficiency Date Time Of Last Edit: 2020-06-09 21:46:25
|
[2020-06-09 23:58:11] |
Sierra Chart Engineering - Posts: 104368 |
We are not aware of any reason why that error would occur related to updating Sierra Chart. It does not make any sense to us. We recommend rebuilding the custom study files using remote build: How to Build an Advanced Custom Study from Source Code The other thing to check is that perhaps security software on your computer is preventing the loading of the DLL file. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2020-06-09 23:58:31
|
To post a message in this thread, you need to log in with your Sierra Chart account: