Not sure this is the best way to resolve this but it works. Let me know if you have other ideas.
I am using this on a list view. I duplicated the number field and made it text with an auto enter calculation of the number field I want to find. I then hung the new field off the edge of the layout and cleared its formatting and bumped the text over with an indent of 50. This way the field is on the layout but not visible. Works great but created a little clutter with adding the new field.
Quick Find does search number fields. Make sure the field in question is "Included for Quick Find” in the Inspector.
If I set the global field I created to a number type then it works on number fields and not text fields. The workabound above is working well.
Paul Webb wrote:
If I set the global field I created to a number type […]
That's not what I said in my post.
[…] The workabound above is working well.
Well, then …sorry for interrupting.
Ok, so I completely misread your original post. Thought you said it does NOT search number fields.
The field in question has the appropriate checkbox on but since the field types do not match it does not search the needed field.
I didn't mean for that to come across nasty.
OK, never mind. Two things:
1. Most of the times, FileMaker doesn't care about data type, at least not between numbers and strings – it's a sort of duck typing: it works, or it doesn't. It's up to the developer to make sure it does work.
Try to multiply the contents of a text field; Filemaker does an implicit GetAsNumber() and gives it a shot, and there will be a result, though it might be 0.
btw, in my sample file, change the type of the global to Number, then try to find text …
2. I thought that maybe you expect a search in a number field to work like in a text field, but it doesn't. "Lazy" will find "A lazy", "the lazy" and "Lazybones", but 9 will only find 9, not 96, and not 69. And according to the FM12 Help, the Quick Find feature supports no operators except match phrase (""), so you can't find "lazy" by searching for "*azy", and you wouldn't find 9 in a calculated text version of 69 (if that even makes sense).
Have a look at this, maybe it clears things up (it was instructional for me, anyways).
Thanks. That makes sense. I appreciate the detail.