rgmatthes
04-01-2010, 01:03 PM
I have a master macro doing lots of things, and it takes about 3 minutes to run. The macro itself runs just fine, everything works. But while it is running, users can't do anything else in any Office application. Outlook freezes, Excel and Word are useless... and I'd like to fix this if possible.
...but I have no idea where to start! Is there any way to restrict how much processing power macros can use up so my users don't have to just wait around until the macro is finished to check their e-mail?
I don't think this is a code issue... maybe a "coding structure" problem? So here are some details:
I'm running Win7 and Office 2010 (which is nice, btw).
I have three forms and one module in my project. Form 1 collects info and saves it to variables, which is used to auto-generate some of the fields in the next form, form 2. When the user completes form 2, form 3 activates, which makes a series of calls to various subroutines stored in the module. There are 14 subroutines in all, and each is ran one after the other with calls. These subroutines manipulate the active file in various ways, drawing upon the variables from forms 1 and 2. When all 14 subroutines are done, parts of form 3 fill themselves out to display a few stats, and a button makes itself visible for exiting.
Any ideas? THANKS A MILLION!
:beerchug:
...but I have no idea where to start! Is there any way to restrict how much processing power macros can use up so my users don't have to just wait around until the macro is finished to check their e-mail?
I don't think this is a code issue... maybe a "coding structure" problem? So here are some details:
I'm running Win7 and Office 2010 (which is nice, btw).
I have three forms and one module in my project. Form 1 collects info and saves it to variables, which is used to auto-generate some of the fields in the next form, form 2. When the user completes form 2, form 3 activates, which makes a series of calls to various subroutines stored in the module. There are 14 subroutines in all, and each is ran one after the other with calls. These subroutines manipulate the active file in various ways, drawing upon the variables from forms 1 and 2. When all 14 subroutines are done, parts of form 3 fill themselves out to display a few stats, and a button makes itself visible for exiting.
Any ideas? THANKS A MILLION!
:beerchug: