• True if the runtime log was started,
• False otherwise.

Location and name of the log file to create. The name of the log file can be built from the following elements:

[%ExeDir%]	Directory of executable, always filled with the "\" character. This directory is equivalent to the result of fExeDir.
[%ExeName%]	Executable name.
[%Date%]	Start date of runtime log (YYYYMMDD format).
[%Time%]	Start time of runtime log (HHMMSS format).
[%UserName%]	Name of current user.
[%ComputerName%]	Computer name.
Versions 18 and later [%DataDir%] New in version 18 [%DataDir%] [%DataDir%]	Directory of HFSQL data files specified by the user when installing the application. This directory is equivalent to the result of fDataDir.
Versions 18 and later [%DirUserData%] New in version 18 [%DirUserData%] [%DirUserData%]	Directory for the data of the current user of the current application. This directory is equivalent to the result of fDataDirUser.

By default:

• before version 180062: the name of the Log file corresponds to: "[%ExeDir%][%ExeName%]_[%Date%]_[%Time%]".
  For example: "C:\MyApp\Myapp_20071023_130812.wlog".
• from version 180062: the name of the Log file corresponds to: "[%UserDataDir%][%ExeName%]_[%Date%]_[%Time%]".
  For example: "C:\Users\Doc\AppData\Roaming\WINDEV Applications\MyApp\Myapp_20071023_130812.wlog".

By default, the name of the Log file corresponds to: "[%UserDataDir%][%ExeName%]_[%Date%]_[%Time%]".
For example: "C:\Users\Doc\AppData\Roaming\WINDEV Applications\MyApp\Myapp_20071023_130812.wlog".

Versions 22 and later
Caution: If you are using the dynamic construction of strings ("Allow "[% %]" in the strings" option in the "Compilation" tab of project description), a compilation error occurs (unknown identifier). In this case, each string must be preceded by '-%'. Example:

dbgEnableLog("[%DirUserData%][%exeName%]_[%Date%]_[%Time%]")

becomes

dbgEnableLog(-%"[%DirUserData%][%ExeName%]_[%Date%]_[%Time%]")

New in version 22
Caution: If you are using the dynamic construction of strings ("Allow "[% %]" in the strings" option in the "Compilation" tab of project description), a compilation error occurs (unknown identifier). In this case, each string must be preceded by '-%'. Example:

dbgEnableLog("[%DirUserData%][%exeName%]_[%Date%]_[%Time%]")

becomes

dbgEnableLog(-%"[%DirUserData%][%ExeName%]_[%Date%]_[%Time%]")

Caution: If you are using the dynamic construction of strings ("Allow "[% %]" in the strings" option in the "Compilation" tab of project description), a compilation error occurs (unknown identifier). In this case, each string must be preceded by '-%'. Example:

dbgEnableLog("[%DirUserData%][%exeName%]_[%Date%]_[%Time%]")

becomes

dbgEnableLog(-%"[%DirUserData%][%ExeName%]_[%Date%]_[%Time%]")

Used to configure the options of the runtime log:

LogEnabled	The runtime log is immediately enabled.
LogWLanguageFunctions	The WLanguage functions are written into the runtime log.
LogParameters	The parameters of the functions are written into the runtime log.
LogPause	The runtime log is not immediately enabled
LogAll	The runtime log retrieves: the WLanguage functions the parameters of the functions the processes
LogProcessOnly	The runtime log only retrieves information about the processes.

The combination LogEnabled + LogWLanguageFunctions is used by default if this parameter is not specified.