System Databases tab - Document Settings dialog

Users may want to establish a database containing program or template common data that can be accessed easily from any CaseView document in any client file. Using the system database can eliminate the need to duplicate data in CaseView databases within and between client files.

A system database can be used to store system-wide information for template and client file use. Browses can be created using it as a basis.

To associate a database with the current document:

  1. In the Document | Settings | System Databases tab, click the Add button to launch the New System Database dialog.
  2. Click Browse to locate the .dbf file for the database.

    To create a new database, browse to the location you want the database to be stored, and then, in the File Name box, type a name for the database file. CaseView automatically creates the appropriate files.

  3. In the Label box, CaseView automatically fills in a label for the file based on the first 6 characters for the file name. You may edit this label if desired, but the label must be unique for each database. This label displays in the Cell External Data tab and is used to identify the database when using the CVDATAC() function.
  4. Click OK. The file added will be listed under the available system databases.

Notes

  • If you create a new database by entering a new file name in the database dialog, and then remove it from the list of available databases before closing the dialog, CaseView deletes the files created for this database.
  • CaseView supports relative file paths pointing to the System database. This will allow for easier file sharing and greater adaptability. As an example, if a document is designed on a workstation whose program directory is C:\CaseWare, the hard-coded calculation paths using that folder as the location of CaseView database would fail on a workstation who used C:\Program Files\CaseWare. By using a path relative to the document itself, a client could simply specify the path as one folder above the document, and ensure when the client file is shared, recipients store the file in a program directory subfolder.

Related Topics