Forum Discussion
BenPonder
7 years agoQrew Trainee
solution I'm going with then is to change my [standard] field to a numeric and enter everything as a decimal (boolean are 1 and 0, 99.95% is 0.9995, etc.) and using mid(totext([standard])) to grab digits at certain places and insert the "." and "%" where appropriate.
(I am of course using a case function for boolean, integer or percentage, just working on the percentage part now)
The problem I'm running into now is that the system isn't keeping leading/trailing zeroes, so percentages that are single digit or have no value after the inserted decimal point will not show up properly. Is there a way to tell Quickbase that I need to keep all the leading/trailing zeroes on a field?
(I am of course using a case function for boolean, integer or percentage, just working on the percentage part now)
The problem I'm running into now is that the system isn't keeping leading/trailing zeroes, so percentages that are single digit or have no value after the inserted decimal point will not show up properly. Is there a way to tell Quickbase that I need to keep all the leading/trailing zeroes on a field?
- AlexCertificati7 years agoQrew CadetNo way that I know of to format a number field to avoid trimming zeroes. You could write all that logic into your totext formula, to gauge the length of the numeral before formatting it.
You could also reverse the relationship and make the [standard] field text, which will retain your string exactly as entered, use the totext([standard]) formula for [display], and write the pass/fail calculations as tonumber([display]).