> Have tried to use "Menu commands =" to list menu commands available as per:
> "Menu commands = List, Back, New, Edit, Delete, Find, Config, HELP, Logout"
> 
> but it does not seem to work; with command above I get default menu 
> structure.
> 
> Using:
> "Find Menu commands = List, Back, New, Edit, Find, Delete, Config, Logout, 
> HELP"
> 
> I get the menu I want.
> Q what's the difference?????

"Find menu commands" apply to the LIST of entries, while "Menu commands" apply
to the page where a SINGLE entry is shown. I know that "Find menu commands" is
a misleading name, but it's historical, I should change it to "Menu commands"
and change the other to "Entry menu commands", does that make more sense?

> I can export the Attributes I define easily and the Subject. Can't seem to 
> export the Entry Date and the Text fields.

I added at least the date and message ID to the CSV export. New version under CVS.

> I can export the Attributes I define easily and the Subject. Can't seem to 
> export the Entry Date and the Text fields.

The XML export contains both the Entry Date and Text fields. In CSV format,
it's hard to export the Text field since it can span several lines, which would
break the CSV format (one line per entry). Or do you know how multi-line
entries can be encoded in CSV?

I can export the Attributes I define easily and the Subject. Can't seem to 
export the Entry Date and the Text fields.

Help.

Have tried to use "Menu commands =" to list menu commands available as per:
"Menu commands = List, Back, New, Edit, Delete, Find, Config, HELP, Logout"

but it does not seem to work; with command above I get default menu 
structure.

Using:
"Find Menu commands = List, Back, New, Edit, Find, Delete, Config, Logout, 
HELP"

I get the menu I want.
Q what's the difference?????

> > 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.

> Only the sorting (of the entry mask!) is missing! :)

Ok, I put that on my wish list. So once the second or third person asks for it, I will
implement it (;-)

> > 'sort attributes' sorts the logbook entries when they are displayed.  Or?
> 
> Right
> 
> > What I want is to rearrange the entry mask.  E.g. if 'Entry type' article is
> > selected then the attributes 'Author', 'Journal', 'Title', and 'Year' 
> > should be listed first, as they are required for this bibtex entry type.
> > Is it possible with the current elogd version to also sort (rearrange) the 
> > attributes in the entry mask?  If yes, how?  
> 
> Attributes are shown in the order you specify them in the config file, so what about
> 
> Attributes = Entry type, Author, Journal, Title, Year     ???

Because for 'Entry type'='InProceedings' one needs:
'Author', 'Title', 'Booktitle', 'Year', 'Volume', 'Number'.
So, depending on the entry type that was chosen the entry mask should change,
with the required fields first and the not valid fields should not be shown
at all, which can nicely be done with the 'hidden attributes' config option.
Only the sorting (of the entry mask!) is missing! :)