---
title: "Export a DeltaV database"
---

# Export a DeltaV database

Running DeltaV's database export from the Editor on a Windows DeltaV engineering station, how the program is found, how the outcome is decided, and the verification kit.

**Verification state:** kit shipped. The command line comes from Emerson users on the Emerson Exchange forum, not from Emerson's books; **it has not been run against DeltaV on any version.** The program's location and arguments, its exit codes and messages, whether it writes the file it is given, and how long a whole database takes are not verified. Tested on Linux with a stand-in process host and file system.

## Run the export

On a Windows DeltaV station (ProfessionalPLUS or DeltaV Simulate) with the environment enabled, run **Export DeltaV Database (FHX)**:

1. Name the database. `neuralInverse.dcs.deltav.database` is offered first. Use a non-production database.
2. Pick the file to write. It must be a `.fhx` inside the workspace; an existing file is replaced only after asking.
3. The module runs `DBImpExpClient.exe -e <database> <file>` with your rights, cancellable, and logs the command line, the output and the verdict to **Output > DCS**. The logged command line quotes Command Prompt metacharacters and says when it cannot be pasted into a Command Prompt.
4. The outcome is decided from the written file, never from the exit code alone. A file newer than the run that reads as FHX is an export: it is counted by modules, classes and areas, and opened. Anything else says what happened: not started, stopped, no file, an earlier file left, unreadable.

Off Windows the command says DeltaV runs on Windows. The program runs only in a trusted workspace with the environment enabled, whoever calls it.

## Where the program is found

| Setting | Meaning |
|---|---|
| `neuralInverse.dcs.paths.deltav` | The program, the DeltaV folder, or its `bin` folder, as a full path (a machine setting) |
| `neuralInverse.dcs.deltav.database` | The DeltaV database this station works on (a machine setting) |

With the path empty, the module looks for `DeltaV\bin` at the root of the system drive, then of C:, D: and E:.

## The verification kit

A verification kit runs the same export on a DeltaV engineering station and collects what it wrote and said, so the command can move to verified. To run it, ask your Neural Inverse contact. Do not send plant exports outside your company.