This is one of those cases where posting a couple of lines between CODE tags would really help.
You could use the > as a trap character to start the field after it occurs, but if its intermittent that wont help.
You could also just grab the >100 as a text field and use Val() to get the numeric value.
If the >100 field varies in width enough to knock other fields over along the line, perhaps an LSplit(Intrim()) would return what you need.
Olly has it right Chuck.
Your safest option, usually, is to forget about try to trap the field directly through the template and just grab the string and manipulate, it using 'slice and dice' techniques available with the Monarch Functions, to create a new calculated field ( Or maybe more than one calculated field for some challenges) in the table.
This is especially powerful where the field sizes in a report may not be as consistent as one would like from one report output to the next. Using slice and dice you can build in safety margins to ensure the future compatibility can be accomodated. It's very worthwhile to gain familiarity with the 'text' manipulation abilities of Monarch. Certain challenges become non-challenges when you can look at them form a different direction.