you start with a selection (one or more) records in your table
you run your transaction - just because you cancel the transaction does not 
mean that the record you start on is the one i memory (loaded)
somewhere in your transaction you could do a search, or sort, or create a new 
selection, or select to array all of which will the current record (or change 
the selection altogether)

push and pop insure that if the user had made any changes to the current record 
they are also saved aside.

- open record
- do whatever
- save selection
- push
- start transaction
  - do stuff (other transactions etc)
- finish transaction
- return original selection
- pop

> I'm still wondering why 4D holds the wrong field contents at the end, 
> after rolling back the transaction. Just doesn't seem right.
Hell is other people 
     Jean-Paul Sartre
4D Internet Users Group (4D iNUG)

Reply via email to