When you request data from a datafeed like eSignal, NeuroShell gets as much of that data as it can get (most data feeds have only a few months of historical). NeuroShell saves all the data “loaded in the chart” from the data feed when you shut down. Next time you load newer data, it get concatenated with the older data, allowing you to build up a larger datafile than the vendor supplies. The older data is not reloaded from the vendor, but from our binary file storage. Some data feeds, like Quote.com, send “correction signals” to correct recent bad data, which we honor, but we aren’t sure if eSignal does that. So you could wind up with bad data stored which you can correct in one of three ways:

1. Erase the old data file (Tools->Data Sources->Server->Manage realtime files), which will cause that partcular file to be completely reloaded next time you call for it. If the vendor made a correction, it should now be fixed. The disadvantage is you loose saved data older than the datafeed supplies.

2. Correct the bad ticks (double click on the Close to see the dialog for that). This creates a “patch” that overrides the original data, but doesn’t actually change it. That is so you can change back if you ever want to.

3. Purchase Bowfort’s Data Utility (www.bowfort.com), which reads and edits our binary saved files. This is probably the best solution, because you don’t lose saved data and there are more things you can do with it than just editing bad data.

On occasion, NeuroShell may reload old data itself if it senses that the first few bars of the data selected is missing. It also reloads data if you request data farther back in time than it currently has stored in the data file. Note that even if the data file contains all the past data available from the data feed, setting the date prior to the first date stored in the data file will still reload all the data because NeuroShell doesn’t keep track of how far back each specific data feed stores data (data feeds frequently change their stored data capabilities).