> I have several date-fields defined in my logboek. But when I click the icon and select another month the pop-up 
> window get's filled  with the contants of the logboek instead of the date-selection.

Ups, that problem must have been there for quite some time now. I fixed it in the current SVN version.

> I have been running ELOG on FreeBSD no problem for a year now,
> but this new version 2.5.8-x doesn't seem to wanna work, it compiles fine 
> with a few warnings (see attached logs).
> But has issues with password files, now it shows message "Can't open 
> passwords.pwd" for all my logbooks. It did convert the password files to 
> xml format. I had a good hard look at file permissions and config file with 
> no luck. So I went back a version and compiled 2.5.7-1 which works just 
> fine with old password files. So something with XML & FreeBSD?...

Hard to say. The simplest would be if I could debug this.

> Version 2.5.7-1 (maybe this has been fixed in 2.5.8?)
> When I run a ./elogd -C http://elog.blah.here:88 it clones the config file 
> just fine, also seems to copy over all logbook entries.
> But once I look through them there's a fault with one of the fields it 
> copies over, so entries never show up.
> 
> It should be:
> ========================================
> Date: Tue Mar 01 19:41:29 2005
> In reply to: 24
> Work done by: someuser
> Work done at (dd/mm/yy hh:mm):  1/03/05 3:30pm
> Downtime duration: 0 min
> Planned: Yes
> Reason: Normal work
> Attachment:
> Encoding: plain
> 
> But once cloned it looks like this:
> ========================================
> Date: Tue Mar 01 19:41:29 2005
> In reply to: 24
> Work done by: someuser
> Work done at (dd/mm/yy hh: m):  1/03/05 3:30pm
> Downtime duration: 0 min
> Planned: Yes
> Reason: Normal work
> Attachment:
> Encoding: plain
> 
> 
> For some reason it looses the "m" so line 4 instead of having
> "hh:mm" has "hh: m"

Your problem is that the attribute "Work done at (dd/mm/yy hh:mm)" which
contains a ":". This character is not allowed in attributes. Unfortunately I did
not document this (and even didn't know this until now... (;-) ). So you should
use the new option

Type Work done at = datetime

this gives you at the entry mask fields for day/month/year/hour/minute to fill
out, so you don't have to write it directly into the attribute. Another option
would be to use 

Comment Work done at = Please enter as (dd/mm/yy hh:mm)

which just displays a comment below the attribute in the entry mask.

- Stefan

> > I have been running ELOG on FreeBSD no problem for a year now,
> > but this new version 2.5.8-x doesn't seem to wanna work, it compiles fine 
> > with a few warnings (see attached logs).
> > But has issues with password files, now it shows message "Can't open 
> > passwords.pwd" for all my logbooks. It did convert the password files to 
> > xml format. I had a good hard look at file permissions and config file with 
> > no luck. So I went back a version and compiled 2.5.7-1 which works just 
> > fine with old password files. So something with XML & FreeBSD?...
> 
> Hard to say. The simplest would be if I could debug this.

Anything I could send you to help debug this?

> 
> > Version 2.5.7-1 (maybe this has been fixed in 2.5.8?)
> > When I run a ./elogd -C http://elog.blah.here:88 it clones the config file 
> > just fine, also seems to copy over all logbook entries.
> > But once I look through them there's a fault with one of the fields it 
> > copies over, so entries never show up.
> > 
> > It should be:
> > ========================================
> > Date: Tue Mar 01 19:41:29 2005
> > In reply to: 24
> > Work done by: someuser
> > Work done at (dd/mm/yy hh:mm):  1/03/05 3:30pm
> > Downtime duration: 0 min
> > Planned: Yes
> > Reason: Normal work
> > Attachment:
> > Encoding: plain
> > 
> > But once cloned it looks like this:
> > ========================================
> > Date: Tue Mar 01 19:41:29 2005
> > In reply to: 24
> > Work done by: someuser
> > Work done at (dd/mm/yy hh: m):  1/03/05 3:30pm
> > Downtime duration: 0 min
> > Planned: Yes
> > Reason: Normal work
> > Attachment:
> > Encoding: plain
> > 
> > 
> > For some reason it looses the "m" so line 4 instead of having
> > "hh:mm" has "hh: m"
> 
> Your problem is that the attribute "Work done at (dd/mm/yy hh:mm)" which
> contains a ":". This character is not allowed in attributes. Unfortunately I did
> not document this (and even didn't know this until now... (;-) ). So you should
> use the new option
> 
> Type Work done at = datetime
> 
> this gives you at the entry mask fields for day/month/year/hour/minute to fill
> out, so you don't have to write it directly into the attribute. Another option
> would be to use 
> 
> Comment Work done at = Please enter as (dd/mm/yy hh:mm)
> 
> which just displays a comment below the attribute in the entry mask.
> 
> - Stefan

Ok, i see, the problem for me now is that this attribute name has been in use for 
half a year or so by me. So now I have 100's of logbook entries with the old name 
in them, if I change it's name then all old logbook entries will show up with that 
field blank. I'm not sure if there's an easy way to change that attribute's name in 
100's of entries in 10's of logbooks, because I wouldn't want to try doing that by 
hand.. Any ideas? (i'm no good at scripting something like that 4 sure)

Thanks,
G.

> Ok, i see, the problem for me now is that this attribute name has been in use for 
> half a year or so by me. So now I have 100's of logbook entries with the old name 
> in them, if I change it's name then all old logbook entries will show up with that 
> field blank. I'm not sure if there's an easy way to change that attribute's name in 
> 100's of entries in 10's of logbooks, because I wouldn't want to try doing that by 
> hand.. Any ideas? (i'm no good at scripting something like that 4 sure)

find . -name "*a.log" -exec perl -pi -e 's|Work done at (dd/mm/yy hh:mm):|Work done at:|g' {} \;

Looks a bit cryptic, but searches for all *a.log files, and starts perl to replace
all occurences of "Work done at (dd/mm/yy hh:mm)" with "Word done at:". Better try
this first with a copy of your logbook. After you successfully changed that, you
have to modify the attribute list in elogd.cfg accordingly, like

Attirbutes = ..., Work done at, ...

Please note that after each manual modification of the logbook files, you have to
restart elogd.

I hope this helps.

 Hi Andreas

That worked,  thank you so much. now I'm on to a new error. 

Now every time i try to do the import it crashed the elogd. 

OS is windows server 2008 R2.  I have the elogd installed as a service.

here is the even log:

Faulting application name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707
Faulting module name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707
Exception code: 0xc0000417
Fault offset: 0x000682da
Faulting process id: 0x558
Faulting application start time: 0x01cf37d8870fc9a1
Faulting application path: D:\Program Files (x86)\ELOG\elogd.exe
Faulting module path: D:\Program Files (x86)\ELOG\elogd.exe
Report Id: defc3f39-a3cb-11e3-9dd5-005056954c86

I have attached the Data file I'm using to generate the fault every time.  same config as before.   Any Ideas?

 Anyone have any luck reproducing the error? or have suggestions on how to fix it?