Intersoft Community - WebCombo - WebCombo additional search columns

WebCombo additional search columns

dbar@diasfalisis.gr — Wed, 12 Aug 2015 16:42:37 GMT

Thanks for your reply,

Nice workaround. But the fact remains: The component is not working correctly under all circumstances.

The problem is that in our project, the additional fields are not known during compile-time. Therefore a significant amount of work must be done to overcome this issue.

WebCombo additional search columns

yudi — Tue, 11 Aug 2015 07:37:49 GMT

I created a simple sample of WebCombo and get the same result. When string value is entered, it seems that filtering fail and all records are shown in the result box of WebCombo.

You may try to use requery approach. This approach allows developer to write their own code for manual data retrieving. I followed this knowledge base and modify the query text into the following: "Select TOP 15 * From Categories Where (CategoryName Like 'con%') OR (Description Like 'con%')".

In your case you can use your own Where clause by adding ID and ITEM field.

I enclose my simple sample as attachment. Hope this helps.

WebCombo additional search columns

dbar@diasfalisis.gr — Fri, 07 Aug 2015 06:53:41 GMT

We are using WebCombo in out project integrated with WebGrid. We recently encountered an issue concerning the AdditionalSearchFields.

Product Info: WebCombo 6.0.7200, WebGrid 9.0.7200

In our scenario, the DataValueField and DataTextField are set to the first column named ID which is of integer type and the AdditionalSearchFields property points to a single field named ITEM which is nvarchar and the corresponding record values contain both integer and string values.

As long as numeric values are entered and searched, filtering works fine. All records containing the search value either on ID or on ITEMCODE are shown correctly. If a string value is entered that exists in column ITEM then it seems to fail to filter the rows and ALL records are presented in the combo box list just as if not filter is entered.

I tried a test scenario in which the DataValueField and the column(s) mentioned in AdditionalSearchFields are all of string type and it works fine. The problem only appears when there is datatype inconsistency between as in my true scenario.

Thanks in advance,

Dimitris