GetHistoryInternal-is-called-for-each-symbol-in-the-DataSet-when-viewed-in-the-Data-Manager

QUOTE:
When i open the view in the Data Manager window it all the symbols thats wihin a DataSet one by one which makes it very slow.

Have you profiled that call? Most other providers keep being responsive when updating even big DataSets in this context.

Unfortunately, the provider I am implementing against does not offer these convenience methods. Therefore, my approach is to cache the data and extend the cached data when newer data is needed, while being mindful of memory consumption. If this approach does not work, the company for which I am implementing this solution will need to extend their API.