To clarify, the window is not blank. After I click OK on the error message, WL finishes loading and then I can load the strategies.
Answers:
1.
Strategy names: "151", "152", "dummy", "boo". I give my strategies integer names. I have strategies with numbers all the up to 152. The problem seemed to appear when I reached 151. "dummy" and "boo" were just test names I tried to see if there was some issue with the naming. I could not find any change in behavior with different names.
I went back and reran older strategies, specifically "37" and "55", ran optimizations on them, saved the results, and now these are broken too. They used to work OK. The problem occurs with all strategies, including ones that used to work.
2.
DataSet names: This occurs with any dataset, regardless of the name. I originally observed it in a data set name "SP rand 186 shift" but I now observe it in all datasets.
3. Code: I created a new strategy based one of one your Wiki examples, ran it, saved optimization results, got the same error. Here is the code:
CODE:
Please log in to see this code.
Basically, this error appears at WLPro launch for any strategy with which I have saved optimization results, using any dataset. I do not know if this is related or not, but when I try to log in to Fidelity, it fails - I get a spinning cursor that never returns, and I have to force quit WL via Task Manager. Data Updates for Fidelity however are working.
Ron