neq trouble!

[Jeff Spall]

Hi, I've just been having real problems with a very simple search, to find any employee who doesn't have our normal 25-day holiday entitlement.

I had this button:

<FORM ACTION="FMPro" METHOD="post">

<INPUT TYPE="hidden" NAME="-DB" VALUE="Master_contact_list">

<INPUT TYPE="hidden" NAME="-Lay" VALUE="Layout1">

<INPUT TYPE="hidden" NAME="-format" VALUE="search_results.htm">

<INPUT TYPE="hidden" NAME="-error" VALUE="search_error.htm">

<INPUT TYPE="hidden" NAME="-SortField" VALUE="surname">

<INPUT TYPE="hidden" NAME="-SortOrder" VALUE="Ascending">

<INPUT TYPE="hidden" NAME="-max" VALUE="20">

<INPUT TYPE="hidden" NAME="-op" VALUE=neq>

<INPUT TYPE=hidden NAME="holiday_entitlement" VALUE=25>

........which absolutely failed to work.

I tried substituting

<INPUT TYPE="hidden" NAME="-op" VALUE=ne>

and even in desperation:

<INPUT TYPE=hidden NAME="holiday_entitlement" VALUE="25">

OK so after half an hour I gave up and used the seriously Klunky workaround:

<FORM ACTION="FMPro" METHOD="post">

<INPUT TYPE="hidden" NAME="-DB" VALUE="Master_contact_list">

<INPUT TYPE="hidden" NAME="-Lay" VALUE="Layout1">

<INPUT TYPE="hidden" NAME="-format" VALUE="search_results.htm">

<INPUT TYPE="hidden" NAME="-error" VALUE="search_error.htm">

<INPUT TYPE="hidden" NAME="-SortField" VALUE="surname">

<INPUT TYPE="hidden" NAME="-SortOrder" VALUE="Ascending">

<INPUT TYPE="hidden" NAME="-max" VALUE="20">

<INPUT TYPE="hidden" NAME="-LOP" VALUE=OR>

<INPUT TYPE="hidden" NAME="-op" VALUE=lt>

<INPUT TYPE=hidden NAME="holiday_entitlement" VALUE=25>

<INPUT TYPE="hidden" NAME="-op" VALUE=gt>

<INPUT TYPE=hidden NAME="holiday_entitlement" VALUE=25>

....which does the job straight off.

What's wrong with my 'not equals' operator???

thanks, jeff

[Garry Claridge]

Jeff,

After using "neq", have you been able to go to the database and check "Modify Last Find" to see what FM actualy did?

Good Luck.

Garry

[Jeff Spall]

Hi, it's hard to look at the database direct, because it's remote on the webserver, but the search result I got was all 250-plus records, which could even have been an 'eq' as they were then all set to '25'

Shouldn't it just work - the less than/more than one does!??

....and guess what - a tried it as a url:

http://mydomain.com/myfolder/FMPro?-db=master_contact_list&-format=search_results.htm&-error=search_error.htm&-max=20&-op=neq&holiday_entitlement=25&-find

..........and it works, so I guess I'l forget the submit button, but I still can't figure out what's wrong with the original.

jeff

[Garry Claridge]

RE: I still can't figure out what's wrong with the original

Sun-Spots

All the best.

Garry

[Steve T.]

Umm.. I'm hardly an expert compared to you two, but does 'neq' require quotes, i.e.

<INPUT TYPE="hidden" NAME="-op" VALUE="neq">

since I see all other VALUE= commands need them in your FORM. Sorry if I'm being lame... sometimes it's the simple things that are overlooked and I'm only guessing. If it's not the quotes, try re-typing... maybe there's gremlin characters or something.

Newbily, yours... ST

[Jeff Spall]

Hi, I think i'll give that a try, 'cos its REALLY frustrating, and i think you might have hit the answer, but annoyingly the lt and gt ones work

grrrrrrrrrr

jeff

[andyjohnson]

Did putting neq in quotes work, then?

I found a workaround in my own search by allowing the user to select "equals" or "not equals" in a manual selection.

<select NAME="-OP">

<option VALUE=eq SELECTED>equals

<option VALUE=neq>not equals

</select>