Hi Geoff

There are usually two reason why I would want to use a different dataview. The first was to not move the record pointer for the currently active row while doing some other activity. However, as you explained this is no longer a concern with ADO.net. The second would be to sort the data in a different order which I used to do using a different Index.

Thanks
Simon

>Hey, Simon,
>
>As to your second question, the answer is yes, the changes should be reflected.
>
>If I create two different dataviews on the same table and then add a row to the main table, modify a row, etc - the changes show up in both views. (Of course, if the two views have two different filters, this may not apply).
>
>As for your first question, perhaps if you could provide some details on your specific requirements (as opposed to how you implemented them in Fox), it might help to determine if/how you need them.
>
>Again, there's no such thing as a "record pointer" in ADO.NET. That means that I can bind a dataview to a datagrid, the user can be sitting on row #3 in the grid...and I can run a process that loops the entire dataview (maybe to calculate a grand total or something)...all without "disturbing" the grid and the highlighted row.
>
>So if that is your case, then perhaps they're not necessary. But if you have something different...maybe one view with one filter, and want to perform a quick check on a different criteria, then maybe they'd provide benefit. Anyway, let me know what you're trying to do.
>
>Thanks,
>Kevin