Solved: Opening a Form/Report with a large code Module

[philfer]

Hello,

If one has a form or report that has a lot of code attached, and which Access must load each time it opens the form/report which could slow it down is it easier/smoother to put the code into a general module that Access will load at startup and keep loaded and call the procs from the form/report module reducing the amount of code in these modules and speeding up the opening of the form/report

Does anyone have experience of this issue?

Cheers
Phil

[orange]

Hello,

If one has a form or report that has a lot of code attached, and which Access must load each time it opens the form/report which could slow it down is it easier/smoother to put the code into a general module that Access will load at startup and keep loaded and call the procs from the form/report module reducing the amount of code in these modules and speeding up the opening of the form/report

Does anyone have experience of this issue?

Cheers
Phil

Is it a lot of code, or reading a lot of data that is the issue?
Have you tried to experiment and see if there is a performance difference?

[OBP]

All I can say is why do you need that much code?
IF you have that much code that it slows down the opening of the Form, then putting in a Mudule would obviously help because it would only be loaded one and called as required.
But one major advantage that you will lose is when copying/Importing the form you won't have a copy/Import of the Code, you would have to remember to copy/Import the Module as well.