Earlier quoted context omitted.
This approach is simple but does not scale. People did this long time ago, perhaps starting with SmallTalk in 80’s and VB/Delphi in 90’s. You need separation between components and data. For example you got a list of 1000 objects, each having 50 fields. You display 100 of them in a list at a time. Then you have a form to view the record and another to update it. You may also have some limited inline editing inside th…
can you elaborate on the 'don't scale part'? because apps in 90's don't see 'smaller' than webapps now
This code is a) hard to read and understand because logic is dispersed across event handlers and b) causes a lot of duplication. Over time codebase evolves into a mess.
This is not the only way to create a mess. But this one works every time.