A question on DataTable filtering technique, i.e. when you use DataTable.Select(filterExpression, SortExpression). How to construct a filter expression string that specify the date within a range? Since this filter expression treat every column in the datatable as strings and compare them as strings, it wouldn't give correct result if you say " WHERE date >= 'Jun 30 2004' ". Anybody has any advices on this?

**********Code Snippet Starts Here**********
   DataTable objTable;
   objTable = DataSet1.Tables["TestTable"];

   string strExpression;
   string strSort;
   strExpression= "JoiningDate > '16/12/04'";
   strSort = "FirstName DESC";

   DataRow[] objResults;
   objResults= objTable.Select(strExpression, strSort);

   for(int i = 0; i < objResults.Length; i ++){
      Response.WriteLine(objResults[i][0]);
   }
**********Code Snippet Ends Here**********

Best Regards
Vadivel

MVP ASP/ASP.NET
http://vadivel.thinkingms.com

I think a better idea would be to write a stored procedure and do you WHERE clause in it instead of filtering on the front end. I would be easier, and faster.

ybao,if your scenario is just filtering DataTable,I think DataView would be a better choice,
jbenson001,it could not be faster,connecting to datasource and executing sql queries and getting filtered rows is certainly slower than working on objects like DataView in disconnected environment.

_____________________________
Mehdi.
software engineering student.
Looking for a good job for summer 2005.

Mehdi,

The original poster never states that they are working with a truly disconnected dataset. We can't assume that the application is caching the dataset/datatable, nor should we. Regardless of any of this, the DataView class is operating on the same exact data as the DataTable.Select method, therefore provides no additional help to this scenario.

ybao-
If you construct a datatable with columns that are the correct data type (which they should be if you get them directly from the database) filtering and sorting *should* function as expected. Without testing, I can't categorically state that this is the correct answer, but I suspect that the DataTable column typing has something to do with the problem.