I have the following to access three ASCII files. This stripped down script takes several seconds to run. Why is it taking so long?

QUOTE:
using System;
using System.Collections.Generic;
using System.Text;
using System.Drawing;
using WealthLab;
using WealthLab.Indicators;

namespace WealthLab.Strategies
{
public class MyStrategy : WealthScript
{
protected override void Execute()
{
Bars SectorIndex = GetExternalSymbol("ISector Utilities Index", true);
Bars IndGrpIndex = GetExternalSymbol("IndGrp Capital Goods Index", true);
Bars IndustIndex = GetExternalSymbol("Indust Software Index", true);

}
}
}

QUOTE:
Why is it taking so long?

I don't know. Maybe you can help by giving us an idea about what is really important here:

* first and foremost, is this the case with other ASCII data sources containing regular stock data.
* your primary data provider and time frame

* your ASCII data settings (is Cache enabled),
* loaded data range
* ASCII data time frame
* anything special about the ASCII data, what's in there?

- I have only one dataset with ASCII files. All of these files are slow.
- Fidelity is my data provider. I am using daily charts for this.
- Cache is enabled
- The ASCII files contain data for the last 500 days. I am using 500 bars when I run the script.
- ASCII files contain date, a calculated index and close.

This morning I noticed that if I use a Fidelity sourced DataSet, the strategy runs very slow when I click one of the symbols in the DataSet. When I run the same strategy against a symbol in the DataSet that contains the ASCII files, it runs fast.

Disable on demand data update.

That did it. It appears that it tries to update the ASCII file if I click a stock but it does not try to update the file if I click one of the ASCII files in the DS. Why is there the difference?

It tries to update Fidelity data, and it's taking time. WLP knows that ASCII data can't be updated on demand.