Does using SetEngineBehavior make a difference?

>I have a situation with a client's app that results in the record pointer not moving properly. On the forms I develop, I use a pageframe with a List tab at the far right. On the tab is a grid showing the form's main table and this grid is used for locating a record. You click in a column, start typing, it does an incremental search, and when you hit the record you want you just press Enter. The pageframe's main tab is activated and this is where the data entry/edit is done. This works great, but after installing VFP 8 a client noticed a problem. While on the main tab, the user may move to another record (this is basically a bill of materials form and the user can right-click on a line item and choose Inspect this part and the record pointer will be moved to that part and the form will display 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. I had noticed some similar behavior in another client's app, but attributed it to an error in my code (though I could find none) and didn't think it was VFP 8 related because it had been awhile since we moved to VFP 8, so that connection didn't jump out at me. However, that may be the same issue. If the code is traced, it works, if the code is not traced it will fail. Has anyone seen anything like this?
>
>Thanks,
>
>Russell Campbell