Home |
Search |
Today's Posts |
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Not being a trained programmer, I was just wondering if it is good practice
to write all the code in the form code section or is it better to jump from the form code to a module to do the work after clicking on a command button on the form ?? -- Les |
#2
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
On Jun 28, 1:02 am, Les wrote:
Not being a trained programmer, I was just wondering if it is good practice to write all the code in the form code section or is it better to jump from the form code to a module to do the work after clicking on a command button on the form ?? -- Les Being a self-taught (although Microsoft certified - FWIIW) trainer, I usually tell people to place their shared code in the module, and place form-specific code in the form. That way they can simply move the form to another project without having to take the module as well. Less code bloat and more modular are my catchcries. - David |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
sharing variables between form and module code | Excel Programming | |||
Design Best Practices: Form Control Code in Worksheet or Module | Excel Programming | |||
Sheet code module question | Excel Programming | |||
Updating form labels from code in a module | Excel Programming | |||
Copy form and code question | Excel Programming |