yes :) it would simplify the code to create a new sequence value, rather then having to pass the needed info out of the current transaction/process into a new process, and then transfer it back.
I'll keep this in mind for when I finally get to v16+ :) On Mon, 27 Aug 2018 14:53:13 +0000, Keisuke Miyako via 4D_Tech wrote: > transactions can be paused since v16 > > would that help? > > http://doc.4d.com/4Dv16/4D/16.3/SUSPEND-TRANSACTION.301-3652123.en.html > >> 2018/08/27 23:46、Chip Scheide via 4D_Tech <4d_tech@lists.4d.com>のメール: >> working from inside a transaction requires (as far as I can figure out) >> stepping outside the transaction process and generating the value(s) >> then passing the value(s) back into the transaction. > > > > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:4d_tech-unsubscr...@lists.4d.com > ********************************************************************** --------------- Gas is for washing parts Alcohol is for drinkin' Nitromethane is for racing ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
