Jeremy, I don't think this would be a good situation for using Shared objects. Every object in a shared object must itself be shared. There's a lot of overhead involved in maintaining the various lockers and such.
I would look at using CALL WORKER. Bundle up everything into an object and pack it off to a worker. When the worker is done the results come back via CALL FORM. This will be faster and easier. On Mon, Jul 15, 2019 at 8:27 AM Jeremy Roussak via 4D_Tech < 4d_tech@lists.4d.com> wrote: > I have a form which accepts some information and, when a button is > clicked, does some fairly time-consuming calculations which return a set of > figures. At present, it uses objects with the Form object for input and > output data. > > I’d like to hand off the calculations to a separate process. As I > understand it, I can’t pass the Form object to the new process but have to > create a shared object. > > How do I get the information from the Form object into the new shared > object? I’ve tried > > $shared.formObj := OB Copy(Form) > > but it gives a error: “Not supported value in a shared object”. > > Am I, as so often, missing something obvious? > > Jeremy > ********************************************************************** > 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 > ********************************************************************** -- Kirk Brooks San Francisco, CA ======================= What can be said, can be said clearly, and what you can’t say, you should shut up about *Wittgenstein and the Computer * ********************************************************************** 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 **********************************************************************
