Well, then, that's one not-so-good developer because functionality like tracking the first record, resetting button enabled, et al more properly belongs at the class level anyway. I mean, this argument could be made for any added functionality in a container or control.

>Your method sounds good, for our regret, we're using the same technique, Ian uses. On the other hand, each developer should not forget to properly reset this property, if he/she changes order or applies filter in a form. Just a hypotetic situation: you developed a form class with this property, then somebody new comes and uses this class... What happens, if he/she changes the order and doesn't reset this property? :(((((((((((((((( :)