Wildcard-free search logic - default has changed in version 10

[wigchert]

Are you aware that the search logic in QV10 has changed. When clicking on the header of a list box the user now doesn't get automatically the wildcards in his input field. If wildcards are needed, these have to be entered manually.

This can be changed in the settings of the list box. Default search option is without wildcard (now called 'normal') and this can be overwritten by setting the default search mode to "Use Wildcar Search" in the properties of the (each!) list box.

May be there are good reasons to change this default, but for the reports already delivered in previous versions this may become a lot of work to change the settings of each list box to the other search option (that the users are used to now).

Or is there a better / more clever way to change this setting for all list boxes in a document?

[Qlik_Trigg]

The appearance may have changed but normal mode aims to free the user from typing wildcard characters. Normal mode equates to searching for any string in the target that begins with the typed characters. So typing 'Jo' in Normal mode actually executes a 'Jo*' search. Further Normal Mode also OR's values separated by spaces. So typing 'Jo Tr' as your search string in Normal Mode is equivalent to 'Jo* OR Tr*'. Why the change? Well in most search engines today you dont ask your users to use wildcard characters, you just want them to search for what they know. And that is what we've gone for with V10 search.

If your users wish to return to wildcard mode, and your list boxes use 'default', change Settings > User Preferences to 'Wildcard' rather than each document.

[wigchert]

John, thank you for your reply, helps me to understand the rational behind this change.

For quite some cases the wildcard-default turns out very handy.

Bit worried that changing the default in the User Preferences will not be sufficient for the users who use my reports over the Access Point (JavaZFP).