On 2008 Sep 23, at 18:59, Tim Mansour wrote:
On 24/09/2008, at 5:51 am, Richard S. Russell wrote:
At the same time, I want to check to be sure that there are
absolutely no return characters. This should not be optional; I
want to PROHIBIT them 100% of the time.
For a condition such as that Richard you should be cleaning up the
data yourself, by performing an auto-enter calculation to strip
returns.
The data are not being auto-entered. They're being typed in by the
end users. Sometimes, out of habit, they indicate that they're done
typing in a field by hitting the "return" key instead of the "tab" key.
Unfortunately, FMP seems to provide me with only 1 validity-
checking opportunity, and it forces me to select either
"challenge" or "prevent".
Validate by calculation and set the calc to check all of the
conditions you want.
I am validating by calculation. The problem is that I can set the
"action on failure to validate" to either totally prohibit the value
from being entered at all OR to challenge the user to re-examine it,
with the possibility that the user will say it's OK despite the
possibility of a problem (such as the space in "Mary Beth"). I can't
figure out how to be a hard-ass on some things and offer gentle
guidance on others with what appears to be only the single "check by
calculation" validation method.
