Agree. This is sort-of unbelievable. I just added one custom field for one particular new application form I was creating. This caused every single contact table on every form to have the new custom field enabled and displaying. Now I will need to edit at least 36 forms x at least two tables each for at least 72 table edits simply because a switch is not flipped to make the new field default to disabled. I fear it won't be fixed any time soon since this is going to a vote, and you'll have no idea of the ramifications until you find yourself in a position like mine. I agree with Rachel, if the only required field in a contact table is the last name field, then it is nonsensical to make any new custom field default to enabled/displaying on all tables - especially in already existing forms. So for example, the new field was Youth Worker Position, and I was creating a youth projects application form. Now every form asks the Youth Worker Position, but no other form deals with youth projects! Ugh.