CwEventLog.

Feature list native NT event logging up to 10,000 event IDs binary data and user name logging supported Comes with legacy and ABC templates supports Clarion 5, 5.5 and 6.0 low pricing: only 59,- US$

Most applications require some kind of logging mechanism: To keep track of critical errors, user errors or application failures; import / export protocols, auditing capabilities or whatever else. Until now there have been at least as many approaches to this as there were developers - Many applications record errors and events in various proprietary error logs.

These proprietary logs have different formats, apply different user interfaces for their display, and cannot be merged to provide a complete report. But all of these logs store similar information and present the logged data in similar ways.

Event logging in Microsoft Windows provides a standard, centralized way for applications (and the operating system) to record important software and hardware events. It also supplies a standard user interface for viewing the logs and a programming interface for examining the logs. Event logging provides a means to merge events from various sources into a single informative story.

So why re-invent the wheel? Using CwEventLog, your applications can write to the system's event log! Simply apply a global extension template and log-enable your programs! Using an additional code template, you'll be able to do so *WITHOUT* handwriting a single line of code!

For the ease of use, CwEventLog consists of only three functions, still providing full flexibility:

• RegisterMessageFile() tells the system that your application wants access to the event log and sets up some registry keys needed for that
• CanReportEvent() detects whether or not event logging is possible (that is: your app is running on Windows NT / Windows 2000)
• ReportEvent() does the main work: It writes to the system's event log. You can tell it the text to write, the type of the entry (info, warning or error, for example), an optional event ID and if the user name should be included. Additionally, you can pass the address() of some binary data also to be included in the log.

Just like all solid.software products, CwEventLog is extremely easy to use, highly flexible and of course very reasonably priced! Please take a look at the demo version or order immediately!

Screenshots:

(Sorry, I used the German Windows version for creating the screenshots - screens might look different on your system!)

Comes with a code template - no handcoding necessary!

Linkability chart

The table below lists the supported Clarion versions, template chains, target operating systems and link modes. More about linkability charts here.

CwEventLog Version 1.3.2		DLL version, standalone		LIB version, standalone		LIB version, local runtime
		16bit	32bit	16bit	32bit	16bit	32bit
Clarion 5 Ver. 5.002	Legacy	-	*	-	*	-	*
	ABC	-	*	-	*	-	*
Clarion 5.5	Legacy	-	*	-	*	-	*
	ABC	-	*	-	*	-	*
Clarion 6 6.1 EA2	Legacy	N/A	*	N/A	*	N/A	*
	ABC	N/A	*	N/A	*	N/A	*
Source included		No, but available on demand.