What's a good rule of thumb for how much code you put into a form and what you should seperate and put into a module?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.


Your form should be treated as a single
object. Containing all methods and properties form that form.

A module is a collection of methods and properties you wish to use, or share, have available to a number of forms or modules.

see ya


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
I hesitate to give you a hard number on the amount of code that should go into a form.  Rather you should be looking at your coding techniques.  Are you coding as effeciently as possible? The more you code the more effecient you will become.  

A good example would be repetitiveness.  If you start repeating lines of code in various places, you should probably be looking at creating sub procedures or functions as the situation dictates.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic Classic

From novice to tech pro — start learning today.