I feel your pain. So far, almost all functions in the mess I inherited are click handlers for buttons or other elements, the remaining few are called from one or the other click handlers. And the functions I've analyzed so far had no more than about 3000 lines after automatic indent and wrap cleanup.

I know C-style copypasta code from previous experience (see "You are too academic" in "Your code sucks"), where I had the luck that it was finally made somebody else's problem. Crappy code is one thing, but it becomes really nasty when documentation, editor and compiler don't agree about the language specification, and compiler and runtime have bugs that are triggered about daily in the production systems - like silently NOT executing SQL queries.

Looking back at "too academic", I should be quite happy with VBA. Yes, it is a messy basic, with clear origins in the 16 bit world (for loops become faster when you declare the loop ariable as integer, which limits the loop variable to 16 bit signed integers even on 64 bit systems), some default behaviours are plain weird, and the two variants of if-then-else (block form and line form, one with endif, one without) are annoying for my stupid little cleanup script. But at least it is a much cleaner language than that Hunchback-Gollum-Salvatore C derivate, and it does not prevent you from checking for errors.

Alexander