>Can anyone shed some light on the reason why I need to put my sibling tables (one to one relationship with InitialSelectedAlias) into TABLE buffering instead of row buffering when editing fields from both tables on a form?? When I switch work areas and run a SELECT into a cursor in the same datasession (which, by the way, does NOT pull from the form's tables) the update trigger fires and commits the record!!! What's up with that??? Is that normal?? If I put the parent in Row buffering, but then put the siblings in Table buffering, the trigger does not fire. Does VFP inherintly commit records (or move the record pointer) when switching work areas (SELECT 0) ?? This seems kinda crazy. HELP.
>
>Thanks in advance

This would not seem normal behaviour for Optimistic buffering. Is the following similar to what you do (observe)?

   table1 related into table2
   do some editing
   select 0
   select somefields from table3, ... into cursor myCursor
   && somewhere in here, update trigger fires