You could try to reduce the character count by reindenting using tabs instead of spaces.

However, step back and think about why the 30 kB limit exists.

• You could consider it a kind of commentary on your question. What volunteer, working for fake Internet points, would want to read such a long question? Furthermore, would the question be too broad to be coherent? You've got registry-interfacing code, database-interfacing code, connection pooling support, authentication code, … Could you make several questions, each focusing on a function or two, on just the problematic parts?

• You could consider it a kind of commentary on your code. For example, is there too much repeated code?

• You could consider it a kind of commentary on the verbosity of the vba language.

You could try to reduce the character count by reindenting using tabs instead of spaces.

However, step back and think about why the 64 kiB limit exists.

• You could consider it a kind of commentary on your question. What volunteer, working for fake Internet points, would want to read such a long question? Furthermore, would the question be too broad to be coherent? You've got registry-interfacing code, database-interfacing code, connection pooling support, authentication code, … Could you make several questions, each focusing on a function or two, on just the problematic parts?

• You could consider it a kind of commentary on your code. For example, is there too much repeated code?

• You could consider it a kind of commentary on the verbosity of the vba language.