Unfortunately not. Thanks for the reply. This is what I am seeing so far:
I have noted that if I delete the grid on the Parts form and replace it with another (still based on my igrid class) that has one column for part number and nothing else, that the behavior is correct. So I attribute this to something within that grid (but related to a VFP 8 error or change since this works under VFP 7). I use the ingrid class for speed searching, so it may have something to do with that. Also, I notice that if I use the List tab to search for 147-415, then go to the main tab and inspect part 147-904, then click on the List tab, the record that it goes to is 147-390. This happens to be the record that is displayed in the first row of the grid immediately after doing the original speed search for 147-415. If I search for 147-415, then scroll the grid so that another record is displayed (147-389 for instance), then go to the main tab, inspect 147-904, then go back to the List tab, it's 147-389 that is displayed. Also, it's not an indexing issue because I've reindexed (and this is handled by SDT, so it deletes and totally recreates the indexes).
Thanks again for the reply. Please don't hesistate to offer anything else. :~)
Russell
>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.
