Posted another question that more better explains the problem. Turns out the ASSERT .F. (actually, it is just the debug window opening), moved my recordsource back to the top of the table. The CASE statement was .T. for recno()=4, then the ASSERT put me back on recno()=1. Put messageboxes before the ASSERT that displayed the recno(). Very strange. Still might be a focus related problem.

>Brenda,

>It sounds like it may be a focus problem. Since the toolbar control never gets focus, it's safe to assume that your grid never loses focus. Try setting the focus to another control. Yes, you can set focus to a read only control. You can not set focus to a disabled control.

>>The client (in this case, me) changes the paytemp.int_pmt in the grid, tabs to the next column, then clicks on the SAVE button of the toolbar. The method is validating then saving the data. I believe that if I can take focus off the grid maybe it will update the paytemp table with the column.textbox.value. Unfortunately they only other fields on the page are readonly. Can readonly fields take focus?
>>
>>Do you have any rules of thumb for grids and setfocus. Have run into problems with beforerowcolumnchange being fired because I moved the record pointer with a GO TOP. Someone told me that if focus was not on the grid, then moving the record pointer would not fire any grid events. Is that true? Should I maybe always take focus from the grid while manipulating the table?
>>