When is it worth using a BindingSource?

Question

I think I understand well enough what the BindingSource class does - i.e. provide a layer of indirection between a data source and a UI control. It implements the IBindingList i

Answer 1

Hi I also have some confusion about the subject.
When I use datatables those implement all the interfaces.
However I always use the bindingsource just to be sure.. :)

There are some arguments why that I can think of

1. Multiple views on the same recordset. (ie. 2 grids with diffent sort orders/filters)
2. Filtering,Sorting while not changing the sort order of the records themselves (Filter/Sort)
3. Ability to disable binding for a while for performance reasons. (when there are big updates in the table, don'y listen to all the IXXChanged events)
4. IErrorprovider never worked for me without a bindingsource, however this could be my fault.