Changing Transaction Database Location

If you are using the Enterprise edition of PC Verifier, then the transaction database can be shared over the network with multiple workstations. To allow this, it is important to make sure that the software on each workstation points to the same Transaction Database.

If PC Verifier is installed on a new workstation, the installation will ask for the location of the Transaction Database. If the workstation is not yet setup to share a Transaction Database over a network, it can use a local database.

The Administrator can then change the location of the Transaction Database by using this option.

If you are expanding or changing your network configuration, then you can also move your Transaction Database to a new location that has a mapped drive on each workstation (i.e., a server location that performs daily backups). You then need to go to each workstation that has PC Verifier and point the software to the new database location.

To change the transaction database location…

1.

Go to the Options screen.

2.

Click on the Folder icon .

3.

Choose a location for an existing or new transaction database, click Open.
If the database does not exist in the directory you choose, it will prompt you to create a new one. If the database exists, and your current administrator password is not identical to the security settings in the database you are opening, you will need to enter the administrator password for database at the new location. After the database has been changed, PC Verifier will exit, since security settings and merchant information may be different.

4.

Re-launch PC Verifier.
See the Quick Start Tutorial on how to launch PC Verifier.

5.

Enter your Administrator password.
If you created a new database, you will setup a new administrator password and confirm it at this stage. A new database has no transaction data and no users.

Note: If the Transaction Database is inaccessible, then PC Verifier will prompt the user to enter the location. This would happen if the database was removed from the last location recorded by the workstation or if the database is inaccessible (i.e., the Network that provides access to the location is down or the database is locked).