I have tried to structure my standard modules with the following in mind:
keep procedures that will be called at a specific time together (for ex: start-up procs) in order to spread out the 'apparent' load time
keep related procedures together
keep larger, specialized procedures that may never be called separate (in their own module)
if the above three can be followed, keep the same type of procedure together (ex: msgs that are reused) so that they are easy to find and edit
keep specialized procedures separate for code maintenance
keep frm/rpt procedures that are only called when that frm/rpt is open, on the frm/rpt --even if public-- so that they are not kept in memory
I don't know very much about how modules are loaded in the context of memory usage, so do you have any advice or comments on the best way to structure things?
And also, in my GlobalVars module (storing public vars and constants), I have included a function that sets any temp vars (gets called during startup), because they are used in the same way. Does this sound okay?
I realize that this may be a matter of personal preference, but any advice would be much appreciated.
Thanks in advance :)
PS (not using any custom class modules yet)