Another bug! in back testing this time
- This topic has 15 replies, 4 voices, and was last updated 4 months ago by
.
-
Nope just that message with a “Send report” dialogue, which I did, so it will go to my broker IG.com and then to ProRealtime.
I love the platform for manual trading, but for code… hmmm somewhat flaky frankly.
1 user thanked author for this post.
The best way to proceed, if you don’t want to share your code here in the forum, is send a thicket to PRT.
Have you tried to copy and paste you indicator inside the system code. In this way you will not use the call function. Sometimes it works.1 user thanked author for this post.
This is a very long shot but, try setting your timeframes to the same time units.
instead of 1 hour and 5 minutes etc, change to 60 minutes and 5 minutes.
One problem I looked into in the past, that helped.
1 user thanked author for this post.
I noticed that, in your other post, you called ‘#HourlyBollinger’, and I wondered, why not call it ‘#Bollinger’ since you were calling it from an hourly timeframe in main file.
To me, that could infer that you used the ‘Timeframe’ instruction in a/the called file.
Doing a bit of testing, it appears that, when back testing, if you call a file with a’timeframe’ statement included in it , you get the ‘Parsing error’ message.
The line/column, does, point to the line in the called file, where the ‘Timeframe’ statement sits.
Image shows bare minimum to get error message up.
Solution appears, used generic, no timeframe specific called files and use timeframe in main.
Not checked every possible combination, but error appears repeatable.
Find exclusive trading pro-tools on 
