At risk of not answering the question at all...
You seem to have a business rule that says "this particular field should contain a maximum of N characters."
I would argue that both the database column's size and the textbox maximum length are separate consequences of this business rule. Fixing one from the other confuses correlation with causation.
In addition, enforcing this business rule by examining the maximum length of the database column has other effects:
you'll hit the database every time for what could otherwise be an in-memory validation operation;
if your business rule changes slightly (eg: N goes from 100 to 80 characters) then you need a schema-level change;
some databases working with variable-length character encoding like UTF8 only fuzzily define how many characters even fit in a given column;
more broadly, you're coupling the business rule to an implementation artifact - what if you later decide to use an object database?
I'm not suggesting that you don't sensibly size your database columns (you should), only that you decouple the business rule from the database implementation. If you can get away with a simple fixed-length-check in the application code, I would suggest that.
Edit having read your question a little more carefully, for your text field maximum lengths you need N ahead of validation. Nonetheless, this is still a business rule - can you write a MaximumLength
attribute for your field accessors and interrogate that?