BACKTRACK (Project Administration)

Function:

Allows the administrator to backtrack a Database (DB) to a previous session.

Description:

Sessions are defined as the work done between SAVEWORK commands. The administrator can backtrack to the date or session number required, or, if the required session has been stamped, the administrator can backtrack to the stamp. The current state of the DB will be lost.

In a Global Project, this command can only be used when the DBs are Primary at your administering Location.

In a Global Project, use the REMOTE <loc> BACKTRACK command to backtrack a constructor DB that is Primary at a remote Location, where <loc> is the Location identifier. Refer to the REMOTE (Global Project Administration) command for examples.

If the administrator tries to backtrack over any stamped sessions to a previous session, the administrator will receive an error message. Backtracking over stamped sessions is not allowed. The administrator must remove the stamp from the intervening sessions before they backtrack.

BACKTRACK removes the sessions permanently. The related command REVERT adds a session containing the data for the specified old session.

The backtracked DB is written to a new file. This is done to avoid the situation where secondary DB files in a Global Project could still contain removed sessions. This situation would cause propagation failures if further sessions were added to the backtracked file.

Note:
For extracts, the REVERT command is used instead of BACKTRACK.

Examples:

Command Syntax:

Querying:

Q SESSION

Related Commands:

REVERT (Project Administration)

MERGE CHANGES (Project Administration)

REMOTE BACKTRACK

REMOTE REVERT - Global only