Welcome to Forex-TSD!, one of the largest Forex forums worldwide, where you will be able to find the most complete and reliable Forex information imaginable.
From the list below, select the forum that you want to visit and register to post, as many times you want. It’s absolutely free. Click here for registering on Forex-TSD.
Exclusive Forum
The Exclusive Forum is the only paid section. Once you subscribe, you will get free access to real cutting-edge Trading Systems (automated and not), Indicators, Signals, Articles, etc., that will help and guide you, in ways that you could only imagine, with your Forex trading.
Elite Section
Get access to private discussions, specialized support, indicators and trading systems reported every week.
Advanced Elite Section
For professional traders, trading system developers and any other member who may need to use and/or convert, the most cutting-edge exclusive indicators and trading systems for MT4 and MT5.
Hi,
i always get this error. The problem is that the OrderClose() function contains Bid as parameter for getting the price. But i always get this error 4107, which tells me that e.g. 0.7900500000 is an invalid price. Of course it's an invalid price, because there is no price as mentioned above. It would be more likely something like 0.790000000 or 0.79010000, only for digits behind the point, not five.
How does the strategytester come to this invalid price, when i have inserted Bid as the price parameter for OrderClose?
Do you know any solutions.
Thanks in advance
Greetings
-mike
Sometimes I have wierd problems like this. I usually just find another way of doing the same thing, like putting in something like "Ask-spread*Point" with having spread defined somewhere earlier in the EA as being the value of whatever the spread is for the pair you are testing.
Sometimes I get a problems that I know are coded right and you just have to find another way, knowing that there are some issues still with MT4. If you want, you can send a copy of your code to Metaquotes and tell them about the error, and hopefully the next update will correct it.