Dear Support,

Since last night (Jan.12, 2014, Sunday) both DEMO and Live Platforms didn't work properly for MQL4 command of OrderSelect(). Please refer to the attachments for details.

That's really terrible for our users. I understand it’s hard for you to keep it working properly but as a platform, it must provide a high quality of service to your users. Such kind of low level mistake should not occur for a platform like Dukascopy !!! What I really don’t understand is why all these MQL4 commands worked correctly before didn’t work properly now !!! My impression to Dukascopy platforms now are unstable and lack of strong enough technical support !!!

Please correct the BUGs ASAP and let all your users a peace of mind trading.

Thanks!

We are currently investigating this case.

We investigated this case:

1) OrderSelect() in your strategy actually works properly and shows exactly the same results in Metatrader 4 as in JForex platform. The problem is in incorrect MQL4 API usage. When OrderSelect() with SELECT_BY_POS flag is used, it expects order index as first parameter, but in your strategy order id is passed instead. See MQL4 documentation for details.
2) To make your strategy work in JForex as in Metatrader4, you need to change if statement in start() function of your strategy from "if(OrdersTotal() == 0 && CheckForOpen() == -1000 && CBarWaiting_Sign)" to "if(CheckForOpen() == -1000 && OrdersTotal() == 0 && CBarWaiting_Sign)". There is significant difference how if statements gets evaluated in MQL4 and Java, and unfortunately it can't be fixed soon.
3) We found some other small bugs, that could affect the work of your strategy. It's fixed now and will be available in new API release. The release on DEMO is scheduled this week.