Log Events

Home

4D v20 R7

Log Events

Constant	Type	Value	Comment
Error message	Longint	2
Information message	Longint	0
Into 4D commands log	Longint	3	Indicates to 4D to record the message in the 4D commands log file, if this file has been activated. The 4D commands log file can be enabled using the SET DATABASE PARAMETER command (selector 34). Note: 4D log files are grouped together in the Logs folder (see the Get 4D folder command).
Into 4D debug message	Longint	1	Indicates to 4D to send the message to the system debugging environment. The result depends on the platform: Under Mac OS: the command sends the message to the Console Under Windows: the command sends the message as a debug message. To be able to read this message, you must have Microsoft Visual Studio or the DebugView utility for Windows (http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx)
Into 4D diagnostic log	Longint	5	Indicates to 4D to record the message in the 4D diagnostic file, if this file has been enabled. The diagnostic log file can be enabled using the SET DATABASE PARAMETER command (selector 79).
Into 4D request log	Longint	2	Indicates to 4D to record the message in the 4D requests log, if this file has been activated
Into system standard outputs	Longint	6	Indicates to 4D to send the message to a standard output stream. The message is sent to: stdout if importance = Information message or Warning message stderr if importance = Error message
Into Windows log events	Longint	0	Indicates to 4D to send the message to the “Log events” of Windows. This log receives and stores messages coming from running applications. In this case, you can attribute a level of importance to message via the optional importance parameter (see below). Notes: For this feature to be available, the Windows Log Events service must be running. Under Mac OS, the command does nothing with this output type
Warning message	Longint	1