> > > Was just wondering about the status of the multi-line attributes in Elog, are 
> > > they implemented in elog yet? If not is that something you are planning to do 
> > > in the future?
> > 
> > In order to have multi-line attributes, the whole format of the logbooks has to be
> > changed. I plan to use XML for the logbook format in the future. We would not have
> > any more one file per day, but one big file per logbook. I have already some XML
> > functionality in elog, but this one requires a major rewrite of the whole code. On
> > the other hand, searching etc. will become much faster afterwards. I plan to start
> > this development soon, but it might take quite some time, so don't expect it
> > before summer or fall.
> > 
> > Best regards,
> > 
> >   Stefan
> 
> Thanks for your help, thats useful to know.
> 
> Paul

Hi Stefan,

any update on the multi-line request?

cheers,

Paolo

> > > > > Was just wondering about the status of the multi-line attributes in Elog, are 
> > > > > they implemented in elog yet? If not is that something you are planning to do 
> > > > > in the future?
> > > > 
> > > > In order to have multi-line attributes, the whole format of the logbooks has to be
> > > > changed. I plan to use XML for the logbook format in the future. We would not have
> > > > any more one file per day, but one big file per logbook. I have already some XML
> > > > functionality in elog, but this one requires a major rewrite of the whole code. On
> > > > the other hand, searching etc. will become much faster afterwards. I plan to start
> > > > this development soon, but it might take quite some time, so don't expect it
> > > > before summer or fall.
> > > > 
> > > > Best regards,
> > > > 
> > > >   Stefan
> > > 
> > > Thanks for your help, thats useful to know.
> > > 
> > > Paul
> > 
> > Hi Stefan,
> > 
> > any update on the multi-line request?
> 
> Nope. Too many other things to do during my "day job".
> 
> Stefan

Thank you, your eLog is already a very good instrument!

Hi all,

I am successfully using ELOG V2.9.2-2455 to manage several laboratory logs.

I am looking for a way, if possible, to format the subject attribute in bold type while in thread display.

I've used the following code

Display Subject = <b>$subject</b>

with no success, then I've tried

Subst Subject = <b>$subject</b>

again with no success. It seems that the <b> tag is not iterpreted.

Have you any suggestion about this?

Thank you in advance.

Paolo

Dear Andreas,

thank you very much for your prompt reply and for you suggestions, which helped me to solve the problem. Now it's all working perfectly.

Cheers,

Paolo

Have a working copy of 1.35 running on NT4 server.
Went to upgrade to latest version.
Stopped service, installed the 2.52 version, restarted service and when 
trying to connect get nothing but server not found, dns errors, etc.
Copy back the 1.35 elogd.exe and everything is fine - I can connect and add 
entries to log.
Copy 2.52 elogd.exe and nothing.

So being the bright boy, I unistalled E-log, went through the registry and 
yanked everything out that referenced ELOGD, rebooted, installed 2.52, made 
the necessary registry changes, started service and nothing. 

Stopped service and copied 1.35 Elogd.exe back into folder, started service, 
and everything works.

Any ideas on why 1.35 works like a charm but 2.52 won't? I've tried stepping 
back to 2.10 version before giving up.

This is a server that is patched to latest and runs quite well with 1.35.

tuens out that the first log file was causing the problem. Elconv would just hang 
on trying to convert it. renamed it, reran elconv, reload service and 2.51 elogd 
and all was working as it should.


> Have a working copy of 1.35 running on NT4 server.
> Went to upgrade to latest version.
> Stopped service, installed the 2.52 version, restarted service and when 
> trying to connect get nothing but server not found, dns errors, etc.
> Copy back the 1.35 elogd.exe and everything is fine - I can connect and add 
> entries to log.
> Copy 2.52 elogd.exe and nothing.
> 
> So being the bright boy, I unistalled E-log, went through the registry and 
> yanked everything out that referenced ELOGD, rebooted, installed 2.52, made 
> the necessary registry changes, started service and nothing. 
> 
> Stopped service and copied 1.35 Elogd.exe back into folder, started service, 
> and everything works.
> 
> Any ideas on why 1.35 works like a charm but 2.52 won't? I've tried stepping 
> back to 2.10 version before giving up.
> 
> This is a server that is patched to latest and runs quite well with 1.35.

Have set up 3 top level groups, each with their own password file.
Ever since users have to 'login' twice to get to the appropriate elog.
You click on top level group, get to log book and click on the one you want 
and get login/password dialog box, click ok and and you get it again and 
then you finally get into the elog book.

Anything I can check on this behavior?

> > Have set up 3 top level groups, each with their own password file.
> > Ever since users have to 'login' twice to get to the appropriate elog.
> > You click on top level group, get to log book and click on the one you 
want 
> > and get login/password dialog box, click ok and and you get it again 
and 
> > then you finally get into the elog book.
> > 
> > Anything I can check on this behavior?
> 
> Sorry my late reply, was very busy these days... (;-) Can you send me your
> elogd.cfg so that I can see how you defined your groups?
> 
> - Stefan

OK elogd.cfg is attached.