Thanks, Keith. I had wondered about writing a method to copy each element of
the non-shared object into the shared object, but couldn’t believe that there
wasn’t a simpler way of doing it - hence my question. Clearly, I was wrong.
Jeremy
> On 16 Jul 2019, at 09:14, Keith White via 4D_Tech
Hi
I know you've sorted out an elegant solution using CALL WORKER, but just in
case you do need to copy to a shared object or collection in the future, please
see https://kb.4d.com/assetid=78197
Best regards
Keith White
Synergist Express Ltd, UK.
4697775
Kirk, you are so right. Thank you: after ten minutes’ work I have a solution
which both works and is enormously more elegant.
Jeremy
> On 15 Jul 2019, at 17:05, Kirk Brooks via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> Jeremy,
> It's easy to keep trying to do everything the same way we have
Jeremy,
It's easy to keep trying to do everything the same way we have for years.
That's why a list like this is so useful.
On Mon, Jul 15, 2019 at 9:01 AM Jeremy Roussak via 4D_Tech <
4d_tech@lists.4d.com> wrote:
> Kirk,
>
> Now why didn’t I think of that? It’s exactly what CALL WORKER is for,
Kirk,
Now why didn’t I think of that? It’s exactly what CALL WORKER is for, isn’t it?
Jeremy
> On 15 Jul 2019, at 16:44, Kirk Brooks via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> Jeremy,
> I don't think this would be a good situation for using Shared objects.
> Every object in a shared
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
6 matches
Mail list logo
