Viewing the Properties of the Security File
You can view the properties of a security file, whether in Microsoft Access or SQL Server format. To display the properties, select .
Microsoft Access security files
As a security administrator, you can view, and change, the properties of an Access security file.
| Property | Description |
|---|---|
| Security File | The location of the Microsoft Access security file. |
| Identifier | A code that uniquely identifies the security file. The identifier is optional for Microsoft Access security files. |
SQL Server security connection files
| Property | Description |
|---|---|
| Security File | The location of the connection file for the iBase security database. |
| Database Type | The security data is held in an SQL Server database. |
| Database name | The name of the SQL Server database, which may be different to the name of the connection file that you use when you log on. |
| Server | The name of the server machine on which the security database is stored. |
| Login Name | The SQL Server login used when iBase connects to the SQL Server instance. |
| Password | The password is never displayed. |
| Use Windows Authentication | The mechanism used for validating attempts to connect to the SQL Server instance that holds the database. Windows authentication is used when the check box is turned on, and SQL Server authentication when the check box is turned off. |
| Identifier | A code that uniquely identifies the security database and is, typically, the same as the main iBase database. This is mandatory for SQL Server connection files in a replicated iBase system where the identifier should be unique across all the replicated databases. |
Support for Unicode characters
Although iBase supports Unicode, the security file and database may not. Because security files are typically in Microsoft Access format, they will support Unicode characters in user names, passwords, group names and so on. However, these user names will not be supported in a non-Unicode enabled SQL Server database when saved as part of the entity and link records, for example in system fields such as Created By.
If the SQL Server database does not support Unicode then user names must not contain any Unicode characters.