Has anyone experienced searching with Autocomplete ON, showing the correct value in the search field, but failing to find the record?  There is only ONE entry for each value, and using wildcard or simple searches the value is found.  The value was even erased and re-typed into the record field in question but there is still a failure on selected records (not all records).

Hammer wrote on Apr 23^rd, 2008 at 2:28am:

Yes, I have also experienced this when there is an ampersand (&) in the field. Put a backslash (\) before the special characters in Search mode.

I reviewed the special characters section in the manual regarding search.  I certainly understand the power in use of special characters (used them a lot in Q&A) and of multiple expressions.  However, with trend to make Sesame even more 'user friendly' and allow for SPECIFIC use of power options, it would seem worthwhile to reconsider how some or all of the 'special characters' are used.  The ampersand is an extremely common character in company names and other business entries.  Since a simple search recognizes an exact entry with this character but a retrieve spec search does not, there seems to be room for other options.  One would be for Sesame to consider an EXACT match (especially created by autocomplete) containing this character to be a valid match in favor of a non-match of expressions joined by AND.