I have a logbook with an attribute that has a number of fixed values. I 
use MOptions to prevent typos when entering and allow multiple "keywords".
When searching the users can only search on one keyword.
Is there any way to search on multiple values (AAA|BBB|CCC)? If I do not 
use MOption, they can do this, but the users entering logs may mistype the 
keywords.

> I have a logbook with an attribute that has a number of fixed values. I 
> use MOptions to prevent typos when entering and allow multiple "keywords".
> When searching the users can only search on one keyword.
> Is there any way to search on multiple values (AAA|BBB|CCC)? If I do not 
> use MOption, they can do this, but the users entering logs may mistype the 
> keywords.

Even with Moptions, you can put into the "Text:" line

(AAA|BBB|CCC)

and click on "Search text also in attributes". This is a valid regular
expression with searches for AAA or BBB or CCC. Unfortunately you still can
mistype the values. If I would add check boxes in the find page, it would not
be clear if one searches for an "AND" of several values or an "OR" (Most people
would probably think that they want an "AND" because this happens if they
restrict several attributes).

> > I have a logbook with an attribute that has a number of fixed values. I 
> > use MOptions to prevent typos when entering and allow multiple "keywords".
> > When searching the users can only search on one keyword.
> > Is there any way to search on multiple values (AAA|BBB|CCC)? If I do not 
> > use MOption, they can do this, but the users entering logs may mistype the 
> > keywords.
> 
> Even with Moptions, you can put into the "Text:" line
> 
> (AAA|BBB|CCC)
> 
> and click on "Search text also in attributes". This is a valid regular
> expression with searches for AAA or BBB or CCC. Unfortunately you still can
> mistype the values. If I would add check boxes in the find page, it would not
> be clear if one searches for an "AND" of several values or an "OR" (Most people
> would probably think that they want an "AND" because this happens if they
> restrict several attributes).

Yes, I can use the Text: search, but I still have the mistyping problem. (My 
field values are like "ENA, ETB, HRES, etc.) -- Easy to have a typo.

Currently there is a dropdown when searching for MOption fields. Maybe you could 
allow multiple selections in the dropdown. This to me is an "OR" search.

> Currently there is a dropdown when searching for MOption fields. Maybe you could 
> allow multiple selections in the dropdown. This to me is an "OR" search.

Multiple selections are not possible in HTML, only a single value can be selected at
a time.

> > Currently there is a dropdown when searching for MOption fields. Maybe you could 
> > allow multiple selections in the dropdown. This to me is an "OR" search.
> 
> Multiple selections are not possible in HTML, only a single value can be selected at
> a time.

Try: (From monster.com)
<SELECT NAME="lid" multiple size="5">
<OPTION VALUE=""> ------- Select all -------- </OPTION>
<OPTION VALUE="323">Alabama-Anniston</OPTION>
<OPTION VALUE="324">Alabama-Birmingham</OPTION>
<OPTION VALUE="325">Alabama-Mobile/Dothan</OPTION>
<OPTION VALUE="328">Alabama-Montgomery</OPTION>
...
</SELECT>

Although this may not be supported in all browsers. (I think recent versions of 
Netscape and IE support it)

<SELECT NAME="lid" multiple size="5">

Oh, nice, I didn't know of that. However, I prefer to have multiple options to be selected
with individual check boxes, this saves more vertical window space. So I added that
functionality to the find page. If more than one option of a MOptions attribute are
selected, they are or'ed together during the search. You can try that in this forum with
the "OS" for example.

Just compiled 1.410 and have run into an issue that *may* have been
introduced in 1.393.

Config file directives such as "Welcome title" could be very long strings. 
After compiling 1.410, our "Welcome title" is truncated and, while I haven't
counted the actual chars, I suspect that the truncation happens at 1024
characters.  The procedure 'getcfg' has a declared passed paramater "int
vsize". 

I haven't looked to see if this effects any other large configuration
strings that are managed by "getcfg" but this procedure is perhaps the most
popular one by far in elog.

> Just compiled 1.410 and have run into an issue that *may* have been
> introduced in 1.393.
> 
> Config file directives such as "Welcome title" could be very long strings. 
> After compiling 1.410, our "Welcome title" is truncated and, while I haven't
> counted the actual chars, I suspect that the truncation happens at 1024
> characters.  The procedure 'getcfg' has a declared passed paramater "int
> vsize". 

Actually before 1.393 you got a buffer overflow if any string in the
configuration file was longer than 500 chars, so it's a miracle that your elogd
did not crash on the long Welcome Title. I added the "vsize" parameter to avoid
such crashes. To satisfy your need for a long Welcome title, I increased the
string size for that particular case to 10000 chars. Hope this is enough.