Now this is a weird one, and it doesn't seem to affect the functionality. When running a LogEvent call via the Lotusscript debugger I noticed that this line in the LogEvent function raised a Type Mismatch error, even though globalLogItem was defined, and its "message" attribute was populated - go figure!:
LogEvent = globalLogItem.message<br/>
I'll post back if I can dig out anything. I thought it might be related to a public/ private clash, but "message" is a public string, so that shouldn't be the issue at all (and in any case, the event is successfully logged).