Todd,
A couple of questions come to mind:

1. Does the second form participate in the same datasession as the first form?
2. Are you using row or table buffering (buffer set to 2 or 4)?
3. If the second form participates in the same datasession, does it open the same tables?

A combination of these could change your buffering. Or moving the record pointer in the table could issue an automatic tableupdate if you are using row-level buffering and not table.

>I'm using pessimistic buffering on a form that edits basic name and address info.
>
>While the name/address record is being eddited I allow access to another form through a command button. When the user is finished editing the 2nd form, it is released and the name/address form is active again.
>
>When I save [using tableupdate()] on the 1st form, I get the error "Function requires row or table buffering mode". Is something turning off my buffering mode?