>>Kim, try creating a property to hold the current ActiveRow value in the AfterRowColChange Event Test this property against the new ActiveRow value. If it increased call the method from your NAV buttons that checks for conditions for enabling/disabling its Next/End command buttons. If It decreased call your method from you NAV buttons that check s for conditions for enabling/disabling its Top/Prev command buttons. I use code like this.
>>
>>This code doesn't care about filters or indexing in my applications.
>
>Terry, thanks for your time,
>
>I hate to belabor my point but I have grids that are filtered and/or indexed. And using EOF() simply doesn't do the job. If there is a parent/child form with the parent fields being in edit controls on the form and the child records being in the grid with this data, whether the data is related thru code of the form properties for this purpose:
>
>PARENT | CHILD
> indexed
>A A 1
> A 2
> A 3
>B B 101
> B 102
> B 103
>C C 303
> C 304
> C 305
>
>If the current row of the grid is A 1 then the prev/first btns are disabled. B 101 and C 303 can disable prev/first because we know the ActiveRow = 1. My desired effects are to have B 103 and A 3 disable the next/last btns. And this is not possible in the options offered. And again this is something I'd like to do in a class and not have to code in any subclasses of the form/navbtns/grid.

have you thought about building a temp index? this could take the place of setting the filter and would give you an accurate record count.