Hi Y'all,

In a form that has a nav grid on page one and an editing grid on page 2 (VMP form) in just one of the .scx's built form the class I have a wierd record pointer movement behaviour. The form has the table open for the navigational grid, no buffering and then the data entry is into a parameterized view for the current record pointed to in the nav grid. In all my other forms, when I press Save such that a TABLEUPDATE(.T.) is issued, the data is updated and the record pointer stays where it originally was.

But in this form, when I press Save, the record pointer goes to the last physical record in the table regardless as to the original starting record. And note that this is the last physical record not the last record in the index (because the table is indexed on name).

And this wierd behaviour happens outside of the form as well so it does not seem to be form code or properites etc. If I open the table in one work space, position the pointer, open the view in another workspace, make a change and post the change, the record pointer moves to the end of the file.

I have checked *all* settings for the view against views that work properly and have not found anything. I have also checked type of buffering on the view (Optimistic Table) and they are all the same. And there is no wierd index that might fire to move the record pointer. I have also recreated the view from scratch in case that would help.

In my testing, it seems that when a SELECT or view is first fired, the record pointer does NOT move (because VFP does a USE...AGAIN and so the currently open table does not have its record pointer moved) but then when the TABLEUPDATE() is done, the pointer moves to the last record updated (or stays where it was if the pointer was correct in the first place). I cannot see anything in the view that would cause it to move. The view is a basic SELECT * FROM Microfilm WHERE Microfl_ID == ?lnMicrofl_ID (so nothing fancy there).

Any ideas?

Albert Gostick