Not really...
The thing is I have to let some users the capacity of changing the content of that option list.. I was hoping there could be a different way for 
them then to edit the cfg file...

That why I came up at first ask if it could be possible to load an Option list from the content of another logbook... that way I could have made 
up some sort of "worker" logbook that would have feed the main logbook Attribute "workers" options list.


> Forget scripting under Windows, this is painful and not really working. Wrong OS for that.
> 
> But have you considered conditional attributes? With this you can load different option lists straight from the elogd.cf file. Use something 
like this:
> 
> Attributes ..., List, Person
> 
> Options List = List A{1}, List B{2}
> {1} Options Person = Person a1, Person a2, ...
> {2} Options Person = Person b1, Person b2, ...
> 
> So if you choose either "List A" or "List B", you get a different set of persons. Is it that what you want?
> 
> /Stefan
> 
> 
> > a) I couldn't make shell command to execute while elogd was running as a service (I'm running windows and $shell was just returning weird 
stuff ); shell script was 
> > working only when I launch elogd.exe from a command line:
> > 
> > -elogd as a Service running the following : Subst Infographiste = $shell(dir c:\) 
> > will return : Shell execution not enabled via -x flag
> > 
> > -modifying the Windows Service to add "-X" and running the following :Subst Infographiste = $shell(dir c:\) 
> > will return : a empty attribute
> > 
> > -running elogd "-x" from a command line, the following : Subst Infographiste = $shell(dir c:\) 
> > will return : the dir result..
> > 
> > (I also tried to change under witch user the service was running..)
> > 
> > b) I just couldn't figure how to build that script....
> > 
> > But that would be so nice ! I can see so many situations where I could use such a scenario (loading options from another logbook or from a 
txt/csv file 
> > somewhere...)
> > 
> > Thanks,
> > 
> > :)