When creating a custom valuelist (where you type the values to appear in the list) it will automatically “sense” these at text types, even if you type numbers in the list. For just browsing text, no problem, but if you use a checkbox in find mode, it will add wildcards to your selection as if it were a text field.
The senario is that you select a checkbox containing a number in entry mode, use the same form in find mode and select the exact same checkbox, then it will not return any records in the found set. After adding the field in just a normal textbox mode, I was able to see that it was adding wildcards to the number (stored in a INTEGER field on the backend database) causing it to fail.
Luckily in my case, it was a quick fix because it was a boolean field that I was trying to fill. I was clued in by another developer that a null valuelist attribute on a checkbox will automatically fill zero on uncheck and 1 on check, so to fix my problem, I removed the valuelist. But what if I wanted to actually fill numeric values.
I realize that you could put in a dummy table and fill in integer values to work around the issue, but I feel you should not have to do this.
I placed this in the bug forum because of its effect on the product.