Thanks for your input, everyone.
I have used calls to the server in my code quite extensively so I am competent
and confident in doing that.
It’s good there is a simple method of getting the server to give a client the
information it wants.
Maybe if I explain why I want(ed) to do this:
COMBO
Chris,
To expand on this a little bit, Storage consists of shared objects only.
It's not possible to share objects between clients or a client and the
server. Nor would you really want to. Nor would you want to attempt using
something like Variable to Variable.
As Lutz points out you can read
...
Regards
Lutz
> Subject: Re: Storage — Server vs Client
>
> I was hoping there was a way to access the storage object on the server from
> a client.
> it would make a lot of things very simple. For example, the record key
> sequencing
> would be very simple.
>
> Is there
18 9:33 AM
To: 4D iNUG Technical <4d_tech@lists.4d.com>
Cc: Chris Belanger
Subject: Re: Storage — Server vs Client
I was hoping there was a way to access the storage object on the server from a
client.
it would make a lot of things very simple. For example, the record key
sequencing woul
[mailto:4d_tech-boun...@lists.4d.com] On Behalf Of Chris
>> Belanger via
>> 4D_Tech
>> Sent: Monday, September 10, 2018 8:20 AM
>> To: 4D iNUG Technical <4d_tech@lists.4d.com>
>> Cc: Chris Belanger
>> Subject: Storage — Server vs Client
>>
&
gt;
> Cc: Chris Belanger
> Subject: Storage — Server vs Client
>
> I am intrigued by the storage object.
>
> The documentation says that there will be a storage object for the server and
> for each
> client.
>
> But I have not been able to see an
I am intrigued by the storage object.
The documentation says that there will be a storage object for the server and
for each client.
But I have not been able to see an explanation of how you directly use both.
So how are they differentiated in code?
— Thanks
7 matches
Mail list logo
