Hi Barney

I believe the issue is not necessarily with PRT 10.3 but rather the CFD provider.

I know IG is apparently having issues with the Trailing Stop function in ProOrder.

I have asked them about this but all they can tell me is that their IT team is ‘working’ on it.

In the meantime you can try manually coding a trailing stop but someone with more technical skill than myself will have to assist us as this is as far as I could get.

//custom trailing stop

//trail points having been defined at position open i.e. trail = 100

If longonmarket then
if close > positionprice then
If trail > trail - (close - positionprice) then
trail = trail - (close - positionprice)
EndIf
EndIf
If close < positionprice and close < positionprice - trail then
SELL AT MARKET
Elsif close > positionprice and close < positionprice + trail then
SELL AT MARKET
EndIf
ElsIf shortonmarket then
if close < positionprice then
If trail > trail - (positionprice - close) then
trail = trail - (positionprice - close)
EndIf
EndIf
If close > positionprice and close > positionprice + trail then
EXITSHORT AT MARKET
ElsIf close < positionprice and close > positionprice - trail then
EXITSHORT AT MARKET
EndIf
EndIf

There are already trailing stop code snippets in the blog. Of course stoploss will only move once per bar since code are only read one time each period. So it will not act as the IG “set ptrailing” function.