June 17, 200916 yr I've used the > symbol in calculations to identify fields that have information, as in: Case(Home Address > 0; etc., but I've found that if the field starts with a parenthesis, it doesn't see that as greater than 0. Is there a simple way around this? Steve
June 17, 200916 yr Author Perfect . . . I had quite a few calculations in my database using < "0" and > "0" whether the field had anything in it. I've gone through now and changed them all to IsEmpty and not IsEmpty and all is working fine. Thank you for your quick reply. Steve
June 17, 200916 yr if the field starts with a parenthesis That's not a good naming practice. In fact FMP should have warned you about the use of certain characters in field names.
June 17, 200916 yr Hi Steve, I would also mention that < 0 and > 0 can break when used on TEXT fields. If the text is [color:blue]-22 Westinghouse then the > 0 will fail because the NUMBER is less than 0. And the < 0 will fail as well (if you think it indicates that the field is empty) because the -22 number will pass the < 0. I suspect that's why it failed ... "but I've found that if the field starts with a parenthesis, it doesn't see that as greater than 0", ie, because the address probably had a dash & number in it, instead of it being because it began with parenthesis (because that shouldn't make a difference in that Case() calculation) although I totally agree that you should never use invalid characters in data fields. Edited June 17, 200916 yr by Guest
June 17, 200916 yr That's not a good naming practice. I think it's the contents of the field, not its name.
Create an account or sign in to comment