Introduction

Have you ever gotten a call from a user that began, “I got an error message and I think it said …” or “last week your program started acting strange …”? Some applications only record errors to the computer monitor and depend on the user to keep track of the error message and situation. Some applications have some kind of logging mechanism to keep track of critical errors, user errors or application failures; import / export protocols, audit trails or whatever else. There are at least as many approaches to this as there are 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.

Features

Why re-invent the wheel? When you use 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 that provide 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 / Windows XP)
• 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!

Package Contents

Let me start by saying what you not get: The box shown above is a virtual one - the software is only available for download via internet. Upon purchase, you'll be provided with all data required to download and install the product. This will give you:

• a state-of-the-art installer which automatically detects installed Clarion versions and (optionally) registers the templates
• runtime libraries (lib and/or dll files) for all supported Clarion versions
• easy-to-use template files for both ABC and Clarion (legacy) template chains
• class and template documentation in compiled HTML format (.chm file)
• comprehensive example applications for both template chains

Plus

• lifetime free email support
• lifetime free minor upgrades (the ones after the dot)

Linkability

The table below lists the supported Clarion versions, template chains, target operating systems and link modes.

CwEventLog Version 1.3.5		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.0 Build 9015 6.1 Build 9034 6.2 Build 9049 6.3 Build 9050	Legacy	N/A	*	N/A	*	N/A	*
	ABC	N/A	*	N/A	*	N/A	*
Source included		No, but available for purchase by request.

Pricing and availability

CwEventLog is available exclusively at ClarionShop for just 59,- US$ (single user license - please contact our sales office for discounted multi-user licenses!)