Company Events Academic Community Support Solutions Products & Services Contact NI MyNI

Validate Database Settings - Database Name and Path 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 and a Database path that are the same as those of existing databases, this dialog box appears when you click the OK button.

Use this dialog box to specify how to handle the name and path conflicts.

  • Current database configuration—Displays the database name and path you specified for the project library.
  • Existing databases—Displays the name and path of each of the conflicting databases.
    • First database—Displays the name and path of the first conflicting database.
    • Second database—Displays the name and path of the second conflicting database.
  • What do you want to do?—Specifies the action to take to resolve the path conflict. You can select from the following options:
    • Use first database for this project library—LabVIEW logs historical data or events to the First database. LabVIEW changes the current database path and name to the First database path and name, respectively. LabVIEW does not create a new database.
    • Use second database for this project library—LabVIEW logs historical data or events to the Second database. LabVIEW changes the current database path and name to the Second database path and name, respectively. LabVIEW does not create a new database.
    • Change current project library configuration (database name and path)—Enter a different, unique name and path for the new database to eliminate conflicts with the Existing databases. LabVIEW uses the new database name and path for historical data or event logging for the project library.
    • Ignore conflicting database (warning may cause data logging to fail)—LabVIEW ignores the name and path conflicts, which may cause data logging to fail.
  • New database name—Specifies a unique database name. This component is available only when you select Change current project library configuration (database name and path) from the What do you want to do? pull-down list.
  • New database path—Specifies a unique database path. This component is available only when you select Change current project library configuration (database name and path) from the What do you want to do? pull-down list.

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

Current database configuration:

Database name: live_data

Database path: C:\process1\data

Existing databases on computer:

Database1 name: measurement_data

Database1 path: C:\process1\data

Database2 name: live_data

Database2 path: C:\process1\live_data


 

Your Feedback! poor Poor  |  Excellent excellent   Yes No
 Document Quality? 
 Answered Your Question? 
Add Comments 1 2 3 4 5 submit