I am running into an annoying bug with "Execute on client" functions. Even
though I have put UNLOAD RECORD and READ ONLY commands into the methods that
are executed there, the client process keeps records locked even if they are
unloaded and set to read only. I am noticing this as I try to test
any chance In Transaction?
> On Mar 11, 2020, at 8:20 AM, Janet Jonas via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> I am running into an annoying bug with "Execute on client" functions. Even
> though I have put UNLOAD RECORD and READ ONLY commands into the methods that
> are executed ther
I also forgot to note the 4D version - it is 17.4.
If I try to do the editing on the client machine, it reports that the record is
locked by the " Registered Client" process, so I am certain the issue is in
Execute on client.
JJ
> On Mar 11, 2020, at 8:25 AM, Spencer Hinsdale wrote:
>
>
Remember you must have code in the following sequence
Unload record
read only
The reason it may be unlocking on server is that the process ends
Regards
Chuck
Chuck Miller Voice: (617) 739-0306
In
Thank you so much, Chuck! Changing the order of the commands did the trick! I
will be sure to remember this next time.
My server process does not end, but I am not using any print jobs on it, and,
oddly, normal users use the exact same printing code in processes that do not
end for a long time
maybe a method called before the user prints is doing something like:
Read only([table])
print routine
Chip
> Thank you so much, Chuck! Changing the order of the commands did the
> trick! I will be sure to remember this next time.
>
> My server process does not end, but I am not using any prin
6 matches
Mail list logo
