Dude... You're tilting against windmills in the vein of Don Quijote. These people like to argue simply for the sake of seeing their words in print or impressing others on how smart they are. There is no point because their positions are set in stone and will never change.



>I know, However this only works on PKs, not on other columns. OF course there are a number of feartures like SET NEAR and SET FILTER, TAG orders etc that don't come in ADO.NET
>
>I believe your words were 'no SEEK on local data'. You are now qualifying your statement.
>
>Correct, to create a primary key and then a FIND (analogous to a SEEK), it must be on a unique key.
>
>You can do a ROWFILTER. You can also create multiple dataviews on a datatable with different sort orders. You can also specify in a lookup (by using different special characters) whether you want an exact match or partial match.
>
>As I mentioned months ago, I wrote a generic LOCATE function that receives a collection of column(s) and a lookup value to return the datarow(s). I am not denying that I had to write some code to do the same things that VFP has in one command.
>
>But this argument that it 'adds complexity, increases the possibility of bugs' is no more valid than it would be if argued against VFP people who wrote some additional code to do things with, say, the Win API that VB supported 'out of the box'.
>
>Kevin