It's not an option I would choose. I put numbers in number fields and text in text fields. A calculation field can be used to display the formatted value with specified currency symbol while a number field referenced in the calculation can be edited to manage the numeric value.
I can't imagine another reason why number field can have text value, that is user can enter currency symbol. But I think this is most bad decision on first time FM is developed.
1 of 1 people found this helpful
There IS a quirk (that can be leveraged, should you so desire). IF you have a number field and allow text, the sorting is different than if the field is text.
numbers (numerical order, leading 0's ignored)
text (case and alpha ignored, uses creation order)
This may be advantageous when you need a numerical sort (and do not have fixed width characters):
(text - alpha - sorting):
Just FYI, make no assumptions, do what you will with the information.
Check numbers, postal codes - I typically have as text but there may be a need for numerical sorting. (clients ask for all kinds of things!)
I would not put the symbol in the number field. Instead either use a text field with the symbol or use the field set up in the inspector display the symbol.
Or a combination of the two by using the hide field when option in the inspector data field. Stack a set of the number fields on top of each other set up for each symbol and use a Hide formula of PatternCount ( symbolefield; "desired symbol here" ) = 0. This should show the correct version.
Note that no one has said that it is unsafe to put text into a number field.
FileMaker's "loose" data typing can lead to confusing text, numeric and other data types when sorting or setting up a calculation. That's the main danger to mixing text and numbers in the same field.
Including a currency symbol with a number seems pretty low risk.