Matt,

I've found this approach a real pain. I've decided to run a timer instead. The calculation will be only activated if the user stops for a while.
In fact I use a methof of the grid to decide if the recordpointer is moved (Using AFTERROWCOLCHANGE but only from VFP 7 (you missed to enter your version))
This (re) starts a timer. The timer event will do the calculation. I use thus for refreshes I need too.

HTH
Agnes


>Also, bear in mind, this fires via Grid.AfterRowColChange()... My point is that the user can tab or cursor up/down many times in a very short time while editing the grid, and this method fires each time, so, I wonder how (a) storing and restoring the Recno() would compare to (b) Using the table again, from a speed standpoint? For some reason, opening and closing the table with every row/col change seems like it would be slow and "heavy" activity, whereas just moving the pointer back would be a lot leaner.
>
>It's easy enough to test each method. I'll let you know how it turns out.
>
>Regardless of this case, I like knowing about this approach in general. I'm sure I'll have plenty of places to use it.
>
>Thanks for sharing.