When you start a backtest with symbols that need an exchange rate, RightEdge looks through the symbols in your watchlist to find one that can provide the needed exchange rate.  It looks at all the symbols you have set up, not just the ones you have checked.  It doesn't look at the exchange, it just looks that the asset type is forex and that the base and counter currency combined will give you the exchange rate you need.  Now, you may have multiple symbols set up that match.  If it finds more than one match, it will try to select the "best" one based on the frequency.

The current logic to decide whether a frequency is better is this code:

bool bBetter = false;

if (newFreq == BarFrequency &&

      curFreq != BarFrequency)

{

      bBetter = true;

}

else if (newFreq > BarFrequency &&

            curFreq < BarFrequency)

{

      bBetter = true;

}

else if (newFreq < BarFrequency &&

   curFreq < BarFrequency)

{

      int newDiff = BarFrequency - newFreq;

      int curDiff = BarFrequency - curFreq;

      if (newDiff < curDiff)

      {

            bBetter = true;

      }

}

BarFrequency is the frequency of the symbols used in your system.  If bBetter is set to true, that means it considered newFreq a better match than curFreq.

Hopefully this makes some sense and helps.

Thanks,
Daniel

In the meantime, you can use the SystemData.AccountInfo object to get the current exchange rate, and size the position manually.  The following line gets the (Ask) conversion rate from GBP to USB (which should be close to 2):

double exchangeRate = SystemData.AccountInfo.GetConversionRate(CurrencyType.GBP, CurrencyType.USD, QuoteType.Ask);

Thanks,
Daniel

Do you mean the symbol's properties?  I don't think there is a system-level decimal places setting.  The P&L columns currently always use 2 decimal places, because they are in the account currency, not the symbol currency.

I don't know why the profit is showing as zero.  What does your symbol setup look like?  It also wouldn't hurt if you want to send us your system and data.

Thanks,
Daniel