I wanted to reply to the post "Three problems..." and then changed my mind. 
But since this logbook does not allow to delete entries (not even my own) I was neither able to remove the draft
nor the final entry.

Another strange thing: the draft got submitted when I hit the "Back" button after reopening it.

Cheers
Andreas

> Another strange thing: the draft got submitted when I hit the "Back" button after reopening it.

Well, this is a problem indeed. When edit entries now, drafts gets saved regularly, overwriting your original entry. This is a limitation of the elog database, which cannot do full versioning. So "Back" is actually the same as "Commit without email notification". Or better "Commit some ten seconds ago". Now I 
don't know what the best solution is. I'm tempted to just remove the "Back" button and replace it with a "Delete" button. So people can either submit an entry or delete it completely. Any thoughts?

> > Another strange thing: the draft got submitted when I hit the "Back" button after reopening it.
> 
> Well, this is a problem indeed. When edit entries now, drafts gets saved regularly, overwriting your original entry. 
> This is a limitation of the elog database, which cannot do full versioning. 
> So "Back" is actually the same as "Commit without email notification". Or better "Commit some ten seconds ago". 
> Now I don't know what the best solution is.
> I'm tempted to just remove the "Back" button and replace it with a "Delete" button.
> So people can either submit an entry or delete it completely. Any thoughts?

I think it would be nice to have three options:
- "Submit": making the draft entry a "real" entry, with an ID
- "Abort": keeping the entry as a draft entry as it currently is (or was 10 sec ago)
- "Delete": removing the draft entry.

I understand that the draft is overwritten currently by the "Back" button, but why does it get an ID and does not stay as a "Draft"?
As a quick fix you may skip the "Abort" for now and just provide "Submit" and "Delete".

> I think it would be nice to have three options:
> - "Submit": making the draft entry a "real" entry, with an ID
> - "Abort": keeping the entry as a draft entry as it currently is (or was 10 sec ago)
> - "Delete": removing the draft entry.
> 
> I understand that the draft is overwritten currently by the "Back" button, but why does it get an ID and does not stay as a "Draft"?
> As a quick fix you may skip the "Abort" for now and just provide "Submit" and "Delete".

Any entry in elog (also drafts) need an ID in order to be stored on the server, no way around that.

The "Abort" button is exactly the same as the "Back" button, just the name is different. But I think the meaning will not be so clear
to the users. They could expect to abort the edit, and get the version as it was before they started editing (which is not possible).

So I'm tempted to just have "Submit" and "Delete". If one wants to abort, one can navigate away from the page, and confirm the "Leave page"
dialog box. So experts who know what they do can still do an abort if necessary.

Stefan

I am trying to use the command line utility elog. Some of the attributes 
that I have setup are multiple options. When I run the command line 
utility to create a new message, any attribute that is setup with multiple 
options will not be filled in. The syntax I am using is as  follows:

elog -h localhost -p 8080 -l Lab -a "Site=xxxx" -a "Area=System" -
a "Priority=Low" -a "Shift=1" -a "Status=Open" -m text.txt

Site and Area are defined in the config file as MOptions. Is there a way 
to use this feature with multiple options on attributes with the 
attributes = to one or more variables?

Greetings all.  A few ELOG users have posted issues with ELOG 3.0 and newer not working with a variety of MS Windows operating systems,.
I have also encountered a similar problem in my environment.

For the following operating systems:        
1) Windows XP SP3 (32-bit)           
2) Windows Server 2003 SP 2 (32-bit)
when either elog.exe or elogd.exe are run from command line or file manager, the operating system reports the program is not a Win32 application.

I have other test computers that succesfully ran ELOG 3.0, 3.1 and 3.1.1
1) Windows Vista Enterprise (32-bit)
2) Windows 7 Professional (64-bit) 

Has ELOG 3.x and newer changed in regards to support for MS Windows but is not documented on the
official ELOG documentation?

Any help would be most appreciated.

NOTE: The current production ELOG I use on Windows Server 2003 is 2.92-2475 but I would like to use the
features available on the 3,.x versions.  Unfortunately, I am not able to change my production operating system.
 

 First, I really appreciate this software. Thank you.

Next, I have question - am wanting to have a 'dashboard' of sorts that shows all entries that are 'open'. That part is easy enough. But, then I want to color the time (or some other field) if the ELOG has not been updated/created for more than X hours. This will help us keep track of events that need status updates.

Doable?

Thanks!