Re: Re(2): Layered transaction - need to push and pop?

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

Re(2): Layered transaction - need to push and pop?

Hi Kirk, The program is currently single-user. I did include load-wait and unload type record handling which I use on server applications. I considered variables. It might run faster, too, though I don't know how 4D manipulates records within transactions. Ssince it's happening in memory, they