Editing a Database Password
|
|
Click the Edit DB button and then the "Password" choice on the Select TBK Tracker Database screen to edit the user name and password of the selected database. This screen will also come up automatically when you click the OK button after adding a new database. |
Security of TBK Tracker databases is very important. For that reason, both the user name (UID) and password are encrypted in the tbksettg3.ini file. You use the screen shown below in four circumstances:
|
|
1. You have just added a new database. If that database already has a user name and password, you need to enter them in the dialog box and leave the "Encrypt Password Without Changing Database" box checked. If not, you'll need to use Access or SQL Server as appropriate to assign a user name and, optionally, a password. If you need to change the password of an Access database, then enter it and uncheck the "Encrypt Password Without Changing Database" box. Since the Administrator and Reporter cannot change SQL Server passwords, this box is disabled when your provider option is SQL.
2. You want to change the user name and/or password. Here you will enter a new user name and password. TBK Tracker will change the password as described above (unless you check the "Encrypt Password Without Changing Database" box for JET/Access), but will only encrypt the user name and password. You must change the user name manually in Access (Tools menu => Security => User and Group Accounts). You must change both the username and password manually in SQL Server.
3. You have changed the user name and/or password in Access/SQL Server but now need to update the tbksettg3.ini file. In this case, you'll need to check the "Encrypt Password Without Changing Database" box.
4. You want to change the password of an existing Access database. In this case, you enter the new password, verify it, and then click OK. TBK Tracker Administrator will then change the database to use this new password. Notice you do not need to open the database in Access (or even own Access for that matter). This option is not available for SQL Server databases. |
![]() |