I dont ask any support, just bugreporting.

Metastock Adapter return 2 unnecessary bars. I test it in 10 min scale database and 60 min scale.

CODE:
Please log in to see this code.

endTime = 22.07.2009
this operation return 2 bar from next day (from 23.07.2009)
I think this is a Bug.

1 more bug of Metastock Provider. If in 10 min scale database Bar close time Is 10:40, then in WLD his close time become 10:50. So Provider decide that in metast. database time = open time and than convert time to close time. Thus if in Metastock base is already close time, provider shift data to the right in 1 bar. Such error happens on intraday databases. Usually people use CloseTime for bars/candles.
This is serious error.

1. Cannot duplicate the "2 bar next day" problem, and no customer has ever brought this issue to my attention.

2. Our only customer who I know of that is using MetaStock data provided a DataSet for which the intraday bars were timestamped at the beginning of bar. Since the MetaStock format doesn't specify how the bars are timestamped, the adapter was specifically written for our customer to mark the end-of-bar time to be compatible with Wealth-Lab scaling functions. If any customer has intraday MetaStock data that is already timestamped at the end of bar, we'll create a solution.

QUOTE:
1. Cannot duplicate the "2 bar next day" problem, and no customer has ever brought this issue to my attention.

I get this bug again and again. I made this step.
1. Reinstall Metalib COM object
2. Reboot computer
3. Make new metastock dataset.
4. Reinstall WLD.
This bug is only ON INTRADAY dataset. Customers jast don't know about this, because they don't know how to get External data like I do (I think so).
I can correct this bug for myself, but your customers shouldn't have this error.

QUOTE:
If any customer has intraday MetaStock data that is already timestamped at the end of bar, we'll create a solution.

may be they just don't notice this data shift? Anyway I just tell what I see, you deside what to do with this.

Sure thanks. I'm using an intraday MetaStock DataSet too.

Maybe the problem is with your data? If the header is wrong or dates are out of sequence, then the ML Library will seek to the record and return the wrong data.

Do you actually see the problem in the chart data or are you calling .RequestData yourself?

I am using this code

QUOTE:
Bars bars = DS.Provider.RequestData(DS, sSymbol, startTime, endTime, 0, false);

QUOTE:

Maybe the problem is with your data?

I looked in Metastock database files and found no errors there. All right, my code and results are in support ticket. I can't post Images here.

QUOTE:
Do you actually see the problem in the chart data or are you calling .RequestData yourself?

I can't see the problem in the chart data because i can't use Data Range for Metastock Dataset. In support ticket there is my sceenshot of this. I am calling .RequestData myself

I have found 1 more bug. It is minor. All in the support ticket

QUOTE:
I am using this code

Well, the problem doesn't really exist then. Data adapters are not responsible for filtering data, Wealth-Lab is. Adapters can filter data if it's more efficient, but they are not required to.

QUOTE:
Well, the problem doesn't really exist then. Data adapters are not responsible for filtering data, Wealth-Lab is. Adapters can filter data if it's more efficient, but they are not required to.

Filtering Data in wealthlab is ineffective. But without possibility to use Data Range for Metastock Dataset problem does not exist. No filtering needed. If you plan to make this possibility in the future, I think the problem will come again.
Just notice this bug.

Closed.