I am trying to understand what the point of different modules is. Is it just an organization thing?
If I take a function and move it to a new modules will there be errors? Anything I need to watch out for?
I am trying to understand what the point of different modules is. Is it just an organization thing?
If I take a function and move it to a new modules will there be errors? Anything I need to watch out for?
I use different modules for organisation - there may be other reasons that I am unaware of.
There won't be any problems moving functions to different modules - just make sure you do not have identical functions in different modules and you will be fine.
It does affect load/run times (although the difference is miniscule). A module is not loaded until the first time a function in that module is called, so theoretically if you have all of your functions in one module, with no form class modules, then that module will load once at startup and your database will run a bit faster, but like I said it is usually a very small, unnoticable difference. I usually have different modules for different functional areas of my program, for organization purposes, and if I'm troubleshooting, then I can look in one module depending on the area of the program I am dealing with. Personally, I don't like form class modules, so I put all my functionality in standard modules. Of course if you do that then you have to explicitly reference forms by name rather than using the "Me." shorthand, but I don't mind that, plus I can write a function that can be used by all my forms in one module instead of having to write it in the class module for each form. Ask twelve different Access gurus and you will get at least 23 different answers - your preference really.