This article has been machine translated. If you find any errors, we would be grateful if you could report them to
translation@timesensor.com.
General
The timeSensor client app is a rich client, i.e. a generic client with which you can log on to a 4D database. The client app is provided by 4D and is sometimes referred to simply as the 4D Client. This article describes where to install the client app and explains some technical background.
Installing the Client App
- The client app is installed under Windows in the path C:/ProgramData/timeSensorProgram/timeSensor Client/timeSensor Client.exe.
- The Client App is installed under macOS in the path /Users/Shared/timeSensorProgram/timeSensor Client.app. This allows it to be shared by users with different user profiles on the same workstation.
It is important that the users have full read/write access to the directory in which the client app is located, as the client app must be able to update itself. If an update of the 4D database is installed on the server, the client app notices this the first time it connects and downloads a new client app and updates itself.
Depending on how user rights are set up under Windows, your client app may not be able to update itself to a newer version. In this case, start the client app with increased rights by right-clicking on the app and selecting 'Run as administrator'.
Path to the server
When you start the client app by double-clicking, the app first searches for the address of the last server used. This is located in an XML file called "lastServer.xml", which is located in the following path:
- Windows: C:/Benutzer/<Benutzername>/AppData/Roaming/timeSensor/lastServer.xml
- macOS: ~/Library/Application Support/timeSensor/lastServer.xml
If the XML document cannot be found at this point, the Open dialogue is displayed. Any application name can be entered here (this is not relevant and is for your information only). Under Network Address, the IP number of the server and possibly the port must be entered (the default port is 19813).
If the connection between client app and server is encrypted, the application name must be preceded by a circumflex, e.g. ^timeSensor Server. This signals to the client that it must address the database server in encrypted form.
You can also force the connection dialogue to the server by holding down the Alt/Option key immediately after starting the app. The connection data you enter in the dialogue is automatically saved in the "lastServer.xml" file, so of course you must have write access to the corresponding path.
With the checkbox "Show this dialogue at next start", you cause the connection dialogue to be displayed each time the Client App is started. This function is only useful in exceptional cases.