• True if the dynamic audit was started,
• False otherwise.

Location and name of the audit file to create. The name and location of the audit file can be:

• fully customized.
• built using the following keywords:
  

  [%ExeDir%]	Directory of the executable, always filled with the "\" character. This directory is equivalent to the result of fExeDir.
  [%ExeName%]	Executable name.
  [%Date%]	Start date of the runtime audit (YYYYMMDD format).
  [%Time%]	Start time of runtime audit (HHMMSS format).
  [%UserName%]	Name of the current user.
  [%ComputerName%]	Computer name.
  Versions 18 and later [%DataDir%] New in version 18 [%DataDir%] [%DataDir%]	Directory of the 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:

• the extension of the audit file is ".wdaudit".
• the name of the audit file corresponds to: "[%UserDataDir%][%ExeName%]_[%Date%]_[%Time%]".
  For example: "C:\Users\Doc\AppData\Roaming\WINDEV Applications\MyApp\MyApp_20071023_130812.waudit".

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

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

becomes

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

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

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

becomes

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

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

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

becomes

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

Used to configure the options of the dynamic audit:

AuditAll (Default value)	All the audit events are written into the dynamic audit.
AuditAssertion	The assertions are written into the dynamic audit.
AuditComment	The audit comments are written into the dynamic audit. An audit comment is written by dbgWriteCommentAudit.
AuditEnabled	The dynamic audit is immediately enabled.
AuditError	The non-fatal errors not processed are written into the dynamic audit.
AuditException	The fatal errors, processed by WHEN EXCEPTION or not processed, are written into the dynamic audit.
AuditPause	The dynamic audit is initialized but it is not immediately enabled. It can be enabled thereafter by dbgAuditStatus.
AuditWarningAnomaly	The execution warnings regarding the detected anomalies are written into the dynamic audit.
AuditWarningPerformance	The execution warnings regarding performance are registered in the dynamic audit.
AuditWarningUser	The custom execution warnings are written into the dynamic audit. A custom warning is triggered by dbgWriteWarningAudit.