Because the max. value should ONLY apply to that one field, that is highlighted in red.
Sorry, still not clear. What Excel considers a column is a field in db tables. So your comment may mean also every row below 30 in "A1" (50,60,50,30,20,40...) also cannot exceed some value. Or to you, "field" might mean that one intersection (cell) of row/column (in db speak, record/field) which just happens to be 30...
Unfortunately I can't really change anything about the spreadsheet design, as a spreadsheet similar to the one I screenshotted is part of a videogame. And I would like to implement that max. value so that the value assigned to certain people within that video game doesn't go any further than that.
Such justifications are seldom really true and are the result of not knowing how to create something that is properly normalized but still works in the end. That type of design usually presents data input and retrieval issues on an on-going basis. If properly normalized that issue goes away. Then you present the data in a spreadsheet format by using crosstab queries. 'Nuff said by me on the topic.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.