Thank you so much!!!

This is exactly what I need. It works fine! :-))

Thank you for your help and samples. This forum is wonderful!!!!!

Hello Judith,

Thank you for your feedback.

The slowest part in the Creation Filter was GetUIElement method. I have implemented the creation filter without this method. I have tested this by scrolling the grid in all direction, changing the cell texts, and resizing the form.

Please check this optimized solution and let me know if you face the same issue again.

Thank you for using Infragistics Controls.

Sorry, I have another question: Is it possible to cancel the painting? Or : Why is the Performance so horrible when about 10 rows with * are in the visible area? Do you have any ideas?

If not:  Is it possible to split one datatable in two bands? so that i have the comments in the first band and the other rows in the second???

Ok, this is interesting.

I think the Performance is bad when more than about 8-10 rows (in the visible area) are * . Try your sample with "row mod 2 =0" and not 7. Or type in some rows a * ..after few rows the Performance gets very bad.

So sad!

Thank you so much. That is exactly what I Need.

Unfortunately the performance is bad. But just in my Project. I think the reason is because we have written so much Special Events like keydown, enteredit and so on which check the text of the columns...

I try to fix this... Hope I can do this.

Is it possible to decide in code when the cells are painted? I think the BeforeCreateChild-Method is to often busy

Thank you!