>I think you're open to criticism. In general it looks appealing.
>I suggest either to change 'filter' logic or completely remove it. Extremely slow and not working right I think (ie: Try directly searching for 'reason' you get 999).
>
>Hi, Cetin,
>
>Yes, I'm definitely open to criticm. I defintely appreciate people pulling it down and looking at it. This is an on-going project to demonstrate the capabilities of the .NET datagrid. I've received some good feedback on ways to improve it.
>
>As for your example, I ran it on a 4-year old, low-end pentium with just 64 MB of memory, and the filters run in about a second. What type of machine are you running on and where specifically did you run into a speed problem?
>
>I'll look into the '999' - when I created the test data, I included the word 'reason' in the parent description table. But I'll look into it.
>
>Thanks,
>Kevin

Kevin,
It's not specific to 'reason'. I used that one as I noticed whenever you directly go to search and provide a value that exists on all rows (ie: 2004 or 20) it returns total-1 (tested with populating 10 items too and returns 9). However as soon as you do something like find,find next then it starts to work correctly (didn't check the reason).

About being slow. I've Athlon XP 2500+ with 512Mb RAM. Yes it returns in a second if you do not change anything. However I simply increased populate row count to 100000. First I thought it was hung then left it to work. After 35 minutes it was still running with CPU at 100%! I ended the process from task manager. Didn't check in depth but had a quick glance to search routine. There you're checking the search columns for each row. I think with a single pass there you could build a row filter expression.
I couldn't add something positive at the moment but hope in future. Sorry.
Cetin