>Thanks. I didn't realize that Michel was using System.Diagnostics. See my reply to him - I ran some test code on a Application log and discovered that some entries were not found (wrong path info probably) and when that happens accessing some of the EventLogRecord properties (KeywordsDisplayNames, LevelDisplayName, OpCodeDisplayName and TaskDisplayName) throws a EventLogNotFoundException. Can't see any solution other than trapping for that in a try block :-{

That is correct. The only way to workaround those is with Try/Catch.