Hey Randy, There's nothing directly equivalent because EOS lets us use two different machines. In single user there's no other machine and no twined process to run something in synchronously. Launching a separate process locally, pausing the current process and so on is good enough in a lot of cases. If you're looking for a solution that lets you manage different selections of the same table it's probably the best.
Other options require a bit of rethinking what the ultimate goal of the task is. If the process needs to update a given record but calculating that data requires changing the current selection or current record, which is where EOS is so cool, you can flip things around: collect the relevant data into a c-object then do the calculations (clobbering current record and related records and such), updating the c-obj, and when it's done reload the original record (reestablish any related records) and update it from the c-obj. This sort of thing is really fast in single user and avoids the complexity of managing multiple processes for what might be a pretty easy task. On Sun, Dec 4, 2016 at 9:11 AM, Randy Engle <[email protected]> wrote: > Maybe I'm just being a dope and this already exists. > > Any wise shoves in the right direction would be graciously appreciated > -- Kirk Brooks San Francisco, CA ======================= ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
