> Is it possible to get around this problem by having more then one main text field 
> per record?

No, not at the moment. You can increase the 1500 characters by recompiling elogd, but
at some point you will hit the stack limit and elogd will crash. I plan a major
redesign with completely dynamic memory allocation, thus permitting any number of
characters on any attribute. But this will take a couple of months or so.

> > If I want to go to the latest CVS release, what files do I have to compile
> > along with the elogd.c file?  Also, do I need to use any special gcc flags
> > for the compilation?  Thanks.
> 
> You need elogd.c, mxml.c and regex.c, the Makefile you can get from CVS as well 
> 
> http://midas.psi.ch/cgi-bin/cvsweb/elog/Makefile

Worked like a charm.  Thanks again.

> If I want to go to the latest CVS release, what files do I have to compile
> along with the elogd.c file?  Also, do I need to use any special gcc flags
> for the compilation?  Thanks.

You need elogd.c, mxml.c and regex.c, the Makefile you can get from CVS as well 

http://midas.psi.ch/cgi-bin/cvsweb/elog/Makefile

If I want to go to the latest CVS release, what files do I have to compile
along with the elogd.c file?  Also, do I need to use any special gcc flags
for the compilation?  Thanks.

The reason for the earlier question is that we are trying to use Elog to store 
data in a form we'd need to store more 1500 characters in more than one field.

Is it possible to get around this problem by having more then one main text field 
per record?

thanks

Paul

> > > When creating/updating entries in elog, excluding the main text field are 
> > > there any limits on the size of the other fields?
> > 
> > Yes, this is controlled by the variable NAME_LENGTH in elogd.c, which is
> > currently set to 1500 characters. You can try to increase this and recompile,
> > but at some point you will produce a stack overflow and elogd will crash. So
> > the current length is a compromise.
> > 
> > - Stefan
> 
> Thanks. Thats useful to know.
> 
> Paul

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

is printed to the browser encoded, so that it is diplayed as is..

> > Is there any solution to obtain an non-clickable column ?
> > For example here : http://midas.psi.ch/elogs/Config+Examples/ what should 
> > I do to obtain the data of the Category column non clickable?
> > I don't have find a solution in the Syntax of elogd.cfg  
> > (http://midas.psi.ch/elog/config.html)
> 
> What do you mean by "non-clickable column"? The column header for sorting, or
> the column contents which brings you to the single entry page? For both of
> them, there is no way right now to obtain that. Why do you want it?

I talk about the column contents. In fact on ELOG, we store password so its 
more easyer to click twice on it to select them and after to copy them instead 
of select from right to left the password and to try to copy them. The HMTL 
link gave problem, its more hard to copy data from HTML link than an normal TXT.
A little hard to explain sorry for my mistakes and explication I'm French :o).

> Is there any solution to obtain an non-clickable column ?
> For example here : http://midas.psi.ch/elogs/Config+Examples/ what should 
> I do to obtain the data of the Category column non clickable?
> I don't have find a solution in the Syntax of elogd.cfg  
> (http://midas.psi.ch/elog/config.html)

What do you mean by "non-clickable column"? The column header for sorting, or
the column contents which brings you to the single entry page? For both of
them, there is no way right now to obtain that. Why do you want it?