You might consider setting up a value list for each of the allowed value range combinations. And a validation can require that the entered value be a member of that defined value list.
Wow... so in the valuelist I would have
6504 and so on??
I also use a decimal point sometims to have numbers inbetween like
Anyway to build this file auto? It will be huge! That's why I thought a calculation for the numbers to fall between a string would work best.
Please explain what makes your example list of ranges valid:
and then explain what ranges would be invalid.
If any range is valid as long as the first value is less than the second, a pretty simple validation field option can be set to reject ranges such as:
I would recommend that you use two fields for this with different validation calculations on each field. The first can require that the field not be empty. The second can require that it's value must be greater than the value in the first field...