Dumuzi wrote:

phil_trade wrote: The problem is not is the code but in your Empty4.

Try to install a fresh Empty4 with version 427.

Which criminal ?

I can of course try a fresh installation of build 427. My criminal is FxPro.

At work we regularly blamed the compiler or the platform (Windows). However, 99% of the time we were wrong. Later it was required that I proved the problem to be in the the compiler or the platform. I find this to be sound because the alternative is to become a victim. Pardon me, but I still believe this problem can be fixed in the EA and I really, really hope it can because the alternative is "unbearable".

phil_trade wrote: If you can find something in the code, you're welcome ! I just resolve it for a friend with the same problem by installing a new Empty4. I think the problem was in History data. Try this solution first.

Dumuzi wrote:

phil_trade wrote: If you can find something in the code, you're welcome ! I just resolve it for a friend with the same problem by installing a new Empty4. I think the problem was in History data. Try this solution first.

Uninstalled Empty4, deleted program folder and subfolders, downloaded build 427 and installed it. First thing EA did was taking a trade and closing it. hmmm...

Just to verify: Only files I need to install in addition to EA are indicators from NanningBob's thread at FF. Right?

To look at totally unknown code is something I prefer not to do because it takes time just to feel comfortable inside it. Oh, well. I have the problem in front of me so I guess that's reason enough to try.

phil_trade wrote: Try with my SET file to confirm it's not your parameters.

Dumuzi wrote:

phil_trade wrote: Try with my SET file to confirm it's not your parameters.

Will try your SET file as soon as the problem reappears. Everything is working good at the moment.

Dumuzi wrote:I had a short debugging session, but had to stop because the problem went away again. There are some preliminary results and guesses though:
1) In function LookForTradeClosure the variable "take" has a bad value and my OP_SELL was closed.
2) The problem seems to appear when I have one active trade and a second is taken. The problem is with the second trade.
3) The value of variable "take" seems to come from the first trade, meaning its value is logical in the context of the first trade. Cannot see why though.

Of course, being a programmer, I make mistakes and bad guesses faster than most...

Dumuzi wrote:Problem is back so I debugged some more:
Set CloseThisTrade back to False so I could see the lines. The Tpxxx and Slxxx lines for the second active trade are way off and equal those in the first trade. Don't know if they are initially wrong or has been changed.

As I said earlier my brain set up a fuss when I do this kind of work so I need a break.