Log In    |    Knowledge Base    |    4D Home
Tech Tip: The LOG EVENT command and the 4DMSG.DLL
Published On: September 1, 2000

The "LOG EVENT" command allows you to post events to the Windows NT Event Log.

The events can be one of three different importance levels: Information, Warning, and Error. This sets the level of the event, which should not be confused with the value shown in the "Event" column of the Event Viewer, which the LOG EVENT command does not set.

To use 4D's LOG EVENT feature, the following conditions must be met:

1. The command must be executed from a 4D application on Windows NT.
2. The 4DMSG.DLL file must be installed in the System32 subfolder in the Winnt system folder.
3. The Windows NT EventLog service must have already been launched.

When you perform the full installation of 4D 6.5 on Windows NT, the "4DMSG.DLL" file gets installed on your hard disk. For example, if your boot drive is the C volume, this 41.7 KB file will be installed into:


After using the LOG EVENT command to send some text text, you can view the event by using the Windows NT Event Viewer (from the Windows Start Menu, choose Programs/Administrative Tools/Event Viewer). In the Event Viewer window, to see the events posted from 4D, choose "Application" from the "Log" menu. You may also want to update the list by choosing "Refresh" from the "View" menu.

If you are running 4D Server on Windows NT, it is possible for any of your 4D Clients to post events to the Event Log on the Windows NT server computer. You can do this from clients on other operating systems such as Windows 95, Windows 98, or even Macintosh. To do this, all you need to do is call the LOG EVENT command from a stored procedure.