Validate Database Settings - Database Name Conflict

LabVIEW 2013 Datalogging and Supervisory Control Module Help

Edition Date: June 2013

Part Number: 371618J-01

»View Product Info
Download Help (Windows Only)

Requires: DSC Module

Right-click a LabVIEW project library and select Properties from the shortcut menu to display the Project Library Properties dialog box. On the DSC Settings: Database page, if you specify a Database name that is the same as that of an existing database, this dialog box appears when you click the OK button.

Use this dialog box to specify how to handle the name conflict.

  • Current database configuration—Displays the database name and path you specified for the project library.
  • Existing database—Displays the name and path of the conflicting database.
  • What do you want to do?—Specifies the action to take to resolve the name conflict. You can select from the following options:
    • Use existing database for this project library—LabVIEW logs historical data or events to the Existing database. The current database path for historical data or event logging will change to the Existing database path. LabVIEW does not create a new database.
    • Change current project library configuration (database name)—Enter a different, unique name for the new database to eliminate the name conflict with the Existing database. LabVIEW uses this new database name for historical data or event logging for the project library.
    • Change existing database name and create new database with current project library configuration—Rename the Existing database to eliminate the name conflict. LabVIEW creates a new database using the settings you specify.
    • Ignore conflicting database (warning may cause data logging to fail)—LabVIEW ignores the name conflict, which may cause data logging to fail.

The following configuration shows an example of a database name conflict.

Current database configuration:

Database name: process1_data

Database path: C:\process1\data

Existing database on computer:

Database name: process1_data

Database path: tank_measurement


Not Helpful