Rich,

Thanks for the response, but I'm afraid maybe I wasn't quite as clear as I thought. It was my bad, regarding the the state of the table/view I'm replacing rest with. You are correct there is an index controlling the order.

In fact the view is indexed and filtered for example; a group of employee's wages for a particular year where the wages are in ascending order. This data is displayed in a grid and the current order is not desired to change.

So as you have suggested and as I have found setting the order back to it's original state before this copydown method doesn't exactly achieve the desired results.

But, if I do not do this and leave the current index on the column it takes a dreadfully long time doing the replace as I have observed, as the replace is being conducted foxpro then re-orders the records based upon the original table order causing it to conduct a replace upon records multiple times. Not exactly what I had expected, and it is still boggling the mind.

Now, what I have noticed in your code snippet provided is the TAGNO(), I will have to look this up and see exactly what it is as at the moment I'm not certain. Possibly this may help if I implement it I don't know.

I do appreciate the input though and if you can provide any more insight I would welcome the help.

Thanks again,

Steve