J
Joy M
Hi -
Just wondering if anyone has any helpful hints on organizing code in the
VBE.
Is it a good idea to keep all procedures that are called by a module within
the module?
I read that this way the code is behind the form that uses it, which makes
sense to me.
Two things that I do are: use the shortcut menu to find Last Position.
Shift + F2 takes you from a call statement to the procedure.
Ctrl + Shift + F2 returns you to the call statement.
I still find it unwieldy. I keep my Form event procedures at the top and my
cmdButtons
at the bottom of the module.
If you are entering data in a form, the control event logic is in the same
order as the user encounters them on the form.
Right now I am in a big loop, which calls procedures which calls other
procedures.
Yes I put comments before each procedure. But it is all starting to look
the same.
Just wondering what you 'experienced' people do to 'tame the beast'.
Thanks!
Joy
Just wondering if anyone has any helpful hints on organizing code in the
VBE.
Is it a good idea to keep all procedures that are called by a module within
the module?
I read that this way the code is behind the form that uses it, which makes
sense to me.
Two things that I do are: use the shortcut menu to find Last Position.
Shift + F2 takes you from a call statement to the procedure.
Ctrl + Shift + F2 returns you to the call statement.
I still find it unwieldy. I keep my Form event procedures at the top and my
cmdButtons
at the bottom of the module.
If you are entering data in a form, the control event logic is in the same
order as the user encounters them on the form.
Right now I am in a big loop, which calls procedures which calls other
procedures.
Yes I put comments before each procedure. But it is all starting to look
the same.
Just wondering what you 'experienced' people do to 'tame the beast'.
Thanks!
Joy