Macro Enabled Workbook Locks Up and CPU spikes

[vbaNumpty]

I am having an issue that is hard to reproduce with a workbook I created. Essentially it is an order entry system that is done through the use of userforms. Users can enter orders, and retrieve existing order entries and edit them.

Now sometimes, and I can't say for certain if it's when the file remains open and is used over an extended period of time, it locks up or gets very slow and it takes ages to open userforms or close them. Sometimes it necessitates the task manager to force close excel as it becomes unresponsive. Afterwards when you open the file again it has no issues and works just fine with no lag.

I don't know if it's a memory thing or what, but the CPU Usage shoots up when it starts locking up and goes back down when I force close excel. Is there something I can add to my VBA that would help prevent the slowing/locking up from happening? It's quite frustrating to have to tell the users to close the file every so often to avoid it occurring.

 

[Zot]

I think you should provide the code for helper to see if there is problem with the code itself. Probably there is something looping that eats up the memory.

 

[vbaNumpty]

I think you should provide the code for helper to see if there is problem with the code itself. Probably there is something looping that eats up the memory.

There is a lot of code across multiple userforms and modules, is there an easy way to provide all the code?

 

[Zot]

There is a lot of code across multiple userforms and modules, is there an easy way to provide all the code?

That is going to be a problem.

Check if you have any object created and try set it to Nothing at the end of routine. I guess you have to follow execution flow and see anything looping non-stop.

Yes, I have code that span over many other subroutines and it is not easy to pin point.I have to pause stage by stage to debug.

Sorry, I cannot help you much on this.

 

[vbaNumpty]

That is going to be a problem.

Check if you have any object created and try set it to Nothing at the end of routine. I guess you have to follow execution flow and see anything looping non-stop.

Yes, I have code that span over many other subroutines and it is not easy to pin point.I have to pause stage by stage to debug.

Sorry, I cannot help you much on this.

no worries thanks for your input. If it was reproducible it would be much easier to diagnose, but it appears to have no set cause and will sometimes randomly happen. Other times it never does.