>>4. We assume it is something in our framework, but can't figure out where to look.
>
>Is this your own framework? (Sounds a little like VMP).
>
>Anyway, yeah, I think the problem is in the framework. I have seen nothing in native VFP that would cause this, and I use this sort of strategy all the time. I Don't what to tell you except to walk through the code looking for something that moves the pointer.

I have really not had a chance to try and figure it out... I had to patch it by checking RECNO() and setting it back after the TABLEUPDATE.