Hi Saravanakumar,

I can't tell you why RowsCopy has a speed advantage in PowerServer Web. If it does, well - rewrite where relevant for performance reason.

object.data has other benefits: It can take any rectangular subset of rows and columns in one statement whereas RowsCopy/RowsMove/RowsDiscard all process data at the full row level.

I have often used object.data to pick out one or more columns and process them. Like:

dec{4} priceList
priceList = object.data[1, priceColNo, ll_rows, priceColNo]
for row = 1 to rows
   priceList[row] *= ldec_exchangeRate
next
object.data[1, priceColNo, ll_rows, priceColNo] = priceList

Also, object.data supports qualifiers like .current, .original, and .selected. To compare with C#: object.data has some of the strengths of LINQ - despite invented mid 1990s - not too shabby IMHO

HTH /Michael

Thanks Chris.

In my scenario I will not able to use sharedata, as this is kind of data backing up and main data window will get reset.

I thought rowscopy and object.data might have any difference. If these are same, then I will go ahead and modify the object.data to rowscopy.

But do you have any idea why object.data is too slow?

Thanks,

Saravanan.

Hi Saravanakumar;

  Those two commands are functionally the same. The only thing faster would be to use a ShareData() command between the two DC's (and /or a DataStore).

Regards ... Chris