Attributes = Category, RB

Options Category = Cat1{1}, Cat2{2}

{1}Options RB = a,b,c,d...

{2}Options RB = e,f,g,h,...

this is then also easier to handle, as compared to select a value from a very long list.

You need a C compiler to compile Elog under Windows. If you don't have one, I would suggest to follow the advice to use conditional attributes. This does not require a recompilation of Elog.

Attributes = Category, RB

Options Category = Cat1{1}, Cat2{2}

{1}Options RB = a,b,c,d...

{2}Options RB = e,f,g,h,...

this is then also easier to handle, as compared to select a value from a very long list.

Stefan,

Thanks for that advice. I have made that change to the elogd.c file, but the only problem I don't know how to compile Elog to make that change take effect. I did the stop and restart of the elog  service in windows, but that made no difference. How do I compile ELog? Sorry for my ignorance, but I am fairly new to Elog.

The number of 100 options is defined in elogd.c with

#define MAX_N_LIST  100

You could try to increase this to 200, but I have no idea if you will hit some other memory limit then. So what about conditional attributes? You subdivide your list into several smaller lists, like

Attributes = Category, RB

Options Category = Cat1{1}, Cat2{2}

{1}Options RB = a,b,c,d...

{2}Options RB = e,f,g,h,...

this is then also easier to handle, as compared to select a value from a very long list.

Unfortunately this is not possible at the moment. You would have to use the menu command "copy to" and enable it for the admin user. Then you create your entry, and click on "copy to" once for each location you want to copy this entry.

I am setting this up as instrument log in a multi-hospital system, where there will be multiple instruments, in multiple departments, at multiple facilities.

I am using the "Top Group" function to keep the books separate so operators from one instrument/department/facility don't contaminate another instrument/department/facility's logbook.

What I am wondering is there someway to set it up so that a system wide manager could post a message to 5 individual logbooks for 5 identical instruments at 5 different locations all at once (one ELOG server)?

I hope this made sense.  Thank you for your help.

Hello everyone, I am new to the forum.

I currently have an attribute which is a list. From this drop down menu, I can only access around 100 options (ELog restriction I think). How can I extend my drop down list to say 200?

Example:

Attributes = RB

Options RB = a, b, c, ...,etc.

Thanks,

Paul

> > The only caveat is that
> > when you edit an entry, the "Last Edit" is displayed really in seconds since 1970, but I will
> > fix this in the next release.
> 
> I just fixed this in SVN revision #2010. If you would have filled out which operating system you use
> with elog, I could tell you how to upgrade.

Thank you for pointing out the method to identify Last Edit as a datetime type so that it will sort properly. I now have created Last Edit in several 
preexisting logbooks. 

I want to use 
Start page = ?rsort=Last Edit
to set the default sorting of each logbook to be by Last Edit. 

However, all of the entries made before I added Last Edit have no value for that field, so they are all grouped together at the end of the sort. So I 
decided to go through the older entries and set Last Edit equal to the original entry date, as a starting value.

I tried to use the command
Subst on edit Last Edit = $entry time
but it gives a "-" for the Last Edit value when I edit an entry. 

I think this is because $entry time is not a variable supported by Subst. Can you add that support, or else tell me if you know a better way to go about 
doing what I'm attempting? Is there perhaps a way to globally process a group of entries in a logbook and set one attribute's value to be equal to 
another's?

Thanks

> Have you tried the RSS Title option?

doh ... thanks, works perfectly (well apart from the lost end-of-lines in the text portion)