If you'd like to see a form that reproduces this problem, go to the Downloads section and type in "Campbell" in the last name field. The only item that will come up is the sample form I submitted. It is based solely on VFP base classes and has only enough code to reproduce the problem (and it has instructions on how to reproduce it).

>> After doing this and clicking back on the List tab, instead of the grid being positioned on the record displayed in the main tab, the grid will be on some other record. It's not
>>necessarily a record that was previously being viewed on the main tab. As I mentioned before, this has worked perfectly up until the install of VFP 8. In fact, when the client tests on a VFP 7 version of the app, it still works fine.
>
>Lets try to get a handle on the unspoken things: you are not running a framework, but only your own code and no compile/run switches based on version() ? Nothing in the click events ?
>
>>If the code is traced, it works, if the code is not traced it will fail. Has anyone seen anything like this?
>
>Yupp. Debugger changes event orders, since it set focus differently. Best way to combat:
>StrToFile() while running normally, usually in xxxfocus(), Refresh() and similar suspects.
>Grid and Refresh can be ugly...
>
>You might get lucky with a breakpoint set to recno("YourAlias")=m.gnPreviouslySet and not tracing.
>
>What happens if you .refresh() the grid page before leaving it ? And I'ld put the nodefault directly after the if, not as the last line to be executed - just to be sure it doesn't hamper switching focus.
>
>regards
>
>thomas