Walter,

>I was refering to constructs where strong typing is used to validate the type where a parameter might be of unknown class. For flexible and optional parameters in functions you've got to use overloading in C++.

Well, not necessarily. For optional parameters, yes you use overloaded methods. For flexible parameters, you can either use overloaded methods or have your parameters simply be object types and test for type in code. There's always several ways to skin a cat. <g>

>The case argues that if you've got to implement a SQL query in ADO.NET by iterating through collections and/or calling a collection of ADO.NET methods, you have to do a lot of programming to mimmick the SQL command (The SQL SELECTs internals). In this process you can write a lot of bugs because these types of queries normally are not simple.

No, you don't *have* to iterate through rows in the DataRowCollection. You can use a the .Select() method of a DataTable to return an array of rows that you need. Pretty simple.

>>Do you have any idea how this works? The dataview does not have any concept of indexes or optimizable expressions. With a VFP index the index is used as a very efficient tool to get your data. It is grouping the data based on index information, withouth touching the data that does not match your criteria. However if you are going to do this in .NET it has to examine every row if it matches the criterial just like a VFPs SET FILTER that is NON OPTIMIZABLE.

This might not be real performance killer with small resultsets (as using indexes also has an overhead, but is a bigger problem on larger sets of data).

Yes, of course I know how DataViews work. You're correct that they wouldn't be optimized, but with smaller DataSets, it wouldn't be a problem. If you have larger DataSets, then you most likely wouldn't use a DataView.

~~Bonnie