/ impossible for me to trace. What could I have done to cause this / behavior? Dunno, but I got an idea of a workaround. Add a property to the form(set?) .currecno=recno() and fill it in each time you deactivate a frame, and issue go thisform(set).currecno in each frame's .activate(). I know it lacks gracefulness, but it might solve the problem. Looking for the cause of the problem seems to me like one more analysis-paralysis situation in this case. It might be worth the while only if the problem reoccurs on some other form. Eh, another hint - in the debugger, put a watch on eof("table"), and see when it changes.