Search results for query: *

pbbriggs, I still have not found a solution to the problem. I saw that you posted on the thread I started in the VBA topic. I thought Dale's solution helped (it did increase the code speed immensely), but when I started working on the code some more, the same error came up again. It seems as...

I'd also like to add that the solution DaleWatson123321 offered makes use of the filter/database components of Excel. My previous solution used a looped call to the Find function, which is obviously much slower than using a powerful method like AdvancedFilter. Thanks again Dale!

I've actually never had any breakpoints in this macro and the DoEvents statement still allowed for the break. The problem is strange as somedays it will happen and somedays it won't. Dale provided extensive work on an alternate route which should avoid the problem.

The memory explanation would make some sence as the code needs time to catch up with itself and clear temporarily stored data. However, I don't see how there could be a memory constraint with 512 MB of ram. The code execution seems to be fast if the breaks didn't occur.

I'm not using the a STOP command anywhere. I can post the code in an hour or two. Its not too extensive.

Is it possible that you added the macro to the global template for all Excel workbooks?

I am continually receiving the error "Code execution has been interrupted" when trying to execute a filter I wrote for Excel in VBA. Every time I debug, the code has stopped in a different location. VBA Help implies that this halt was caused by the developer manually entering into...

Anyone have any ideas on this yet? I can submit code fragments (however, due to the nature of the problem, I'm not sure what I would submit) or any other information that might help. Thanks.

I am continually receiving the error "Code execution has been interrupted" when trying to execute a filter I wrote for Excel in VBA. Every time I debug, the code has stopped in a different location. VBA Help implies that this halt was caused by the developer manually entering into...