Setting up iBase clients
After you create the iBase database, you might need to configure each iBase installation to suit the work to be done in that database.
Setting options on local machines
You can specify some general options for how users use iBase in the Options (on the Tools menu in either iBase or iBase Designer). You do not need to log on to a security file or open a database, the options apply to the application not to any databases.
Page | Detail |
|---|---|
General | Basic options for using iBase, for example, how users use categories. Any user can change these options without affecting any other user of the machine. These options take effect immediately. |
Charting | Defaults that are used when charting in Analyst's Notebook® (unless specified otherwise in a charting scheme or the Charting Settings dialog). Any user can change these options without affecting any other user of the machine. These options take effect the next time records are charted. |
Advanced | User options that can be changed by any user of the machine; changes to the Local Machine Settings affect all users of the computer. You can prevent users from changing the local machine settings by denying write access to the Settings.xml file. |
Hiding plug-ins
You can deny access to certain iBase features for any user that is working on a specific machine. This is a local machine setting and can be copied between machines.
For more refined control set at the user group level, you might prefer to define System Commands Access Control groups.
Copying the local machine settings to other machines
The local machine settings in the Options dialog and Plug-In Manager are saved in the file Settings.xml. You can copy this file to the other machines on which iBase is installed. For details of where to copy the file, see Installation and Application Data Folders.
SQL Server connection files on local machines
Users should connect to iBase databases that are in SQL Server format by using connection files stored in a shared folder on the network.
Copying connection files to client machines might compromise the security of your system and adds to the administrative workload. If it becomes necessary to copy a connection file, then the file name and path must be identical on each machine to which you copy it.