Is is no longer necessary to create a ClientLocal folder to specify a local client cache.
Note that since v17 64-bit on Windows, it is possible to launch multiple instances of 4D.
(On Mac this was always possible, by the CLI open -n)
The ClientLocal feature was originally used to let multiple instances of 4D connect to the same server.
Starting with 17 R5, the client local cache folder has a suffix,
derived from a hash value of the full path to the application; 3 decimal digits, incremented until there is no collision. a client local in use has a file named inuse.txt and uuid.txt. the former contains the process ID and full path to the application separated by LF, the latter contains a UUID.
so instead of the default client local folder in R4
we now have
Get 4D folder(4D Client database folder) returns this path.
By default a built client app on Windows is blocked from launching a second instance,
but this can be over-ridden by the build key