<Source>.ChangeLogDir (Function)

WINDEV, WEBDEV AND WINDEV MOBILE
ONLINE HELP

Version:

Home | Sign in | English

Priority for defining the location of log files

The log file exists when <Source>.ChangeLogDir is used

Miscellaneous

Replication and log process

ErrorStatusModification

FilterIncludedBetween

MigrateLinkedCompositeKey

New WINDEV, WEBDEV, WINDEV Mobile 25 feature!

Priority for defining the location of log files
The log file exists when <Source>.ChangeLogDir is used
Miscellaneous
Replication and log process

WINDEV

WEBDEV

WINDEV Mobile

Others

See also

<Source>.ChangeLogDir (Function)

In french: <Source>.ChangeRepJnl

Available only with these kinds of connection

Modifies the location of log files corresponding to a HFSQL data file (*JNL files as well as JournalOperation and JournalIdentification files if they exist).

Reminder: The JournalOperation and JournalIdentification files are created:

if the management of replication is requested for the data file.
if the management of the selected log corresponds to "Write-to-file log and history of accesses".

The *JNL file is not created if only the log of access history is requested.

By default, the physical files corresponding to the logs are created:

in the directory specified in the analysis ("Analysis description", "Log process" tab).

in the specified directory when describing the data file ("Description of data file" from the popup menu, "Various" tab). This option is available only if the analysis directory corresponds to "<Default directory of files>".

The location of log files cannot be modified. This function is ignored. The location of the log is configured in the HFCONF.INI file.

This function has no effect and it always returns True.

Remark: From version 19, HFSQL is the new name of HyperFileSQL.

Example

// The "Customer" file has a log
Customer.ChangeLogDir("\\MyServer\Log\JNL", "\\MyServer\Log\Operation")
...
Customer.Add()
// -> the "CustomerJNL" file is opened
// in the "\\MyServer\Log\JNL" directory
//-> the "JournalOperation" and "JournalIdentification" files
// are opened in the "\\MyServer\Log|Operation" directory
...

Syntax

<Result> = <Source>.ChangeLogDir(<JNL file location> [, <LogOperation file location> [, <Backup location>]])

<Result>: Boolean

True if the operation was performed,
False if a problem occurred. HErrorInfo is used to identify the error.

<Source>: Type corresponding to the specified source

Name of the data file whose log must be moved. This is the logical name of the file (defined in the data model editor).

<JNL file location>: Character string (with quotes)

New access path to JNL file associated with the file with logs (full or relative path).
If this parameter corresponds to an empty string (""), the current file location is not modified.

<LogOperation file location>: Optional character string (with quotes)

New access path to JournalOperation file and JournalIdentification file associated with the file with logs (full or relative path). The JournalOperation file contains all the operations performed on the file with logs.
If this parameter is not specified or if it corresponds to an empty string (""), the current file location is not modified.

<Backup location>: Optional character string (with quotes)

Path of backups of log files. By default, this path corresponds to: <directory of JNL files>\__JNLBackup
This path is used during the automatic modification of data files to archive the logs. <Source>.HistoryModification will also find the history of the modifications in these files.
If this parameter corresponds to an empty string (""), the current location is not modified.
If this parameter corresponds to a relative path (and starts with a dot), the path will be relative to data files.

Remarks

Priority for defining the location of log files

The location of log files is defined according to the following priority order:

Location specified when creating the file with logs was created (<Source>.Creation).
Location specified by <Source>.ChangeLogDir.
Location specified in the analysis.
Location of file with logs.

The log file exists when <Source>.ChangeLogDir is used

If the log file already exists during the call to <Source>.ChangeLogDir, this log file is not used anymore: a log file is created at the specified location and it is associated with the HFSQL file.

Using <Source>.DeclareExternal with a file with logs: if an application uses <Source>.DeclareExternal on a file with a log, the modifications performed by this application are saved in the log files specified in the header of the HFSQL file.

Miscellaneous

If the files are opened while the directory is modified, the files are automatically closed.
If the path of the log is redefined several times by <Source>.ChangeLogDir, only the last path is used. The modification is effective for all the applications that use the file with logs.

Replication and log process

If <Source>.InitSubscriber is used, the location of logs and operation tables must also be initialized (<Source>.ChangeLogDir, ..LogDirectory and ..OperationLogDirectory).

Reminder: The replication is based on the logs and on the operation tables of the data files. The replication fails if the location of the logs and operation tables is invalid.

Component : wd250hf.dll