Macro stops running at an unexpected time
 

I've been running this macro for some time and am having this problem today.
I define a worksheet that I'm acting on as EngWS. In the procedure I'm
using, I don't have a reference to the workbook so when I save it, I use

EngWS.Parent.Save.

Today, once it gets to that line, execution just stops. I'm running this
out of an Add-In if that provides any more clues. FWIW, the file I'm working
on is saved on my desktop.

Has anyone seen this problem before and what do I do?

Thanks,
Barb Reinhardt

Macro stops running at an unexpected time
 

OK, now it's working and I've change nothing. There are gremlins in my
system today. I've had one problem after another.

Thanks,
Barb Reinhardt

"Barb Reinhardt" wrote:

I've been running this macro for some time and am having this problem today.
I define a worksheet that I'm acting on as EngWS. In the procedure I'm
using, I don't have a reference to the workbook so when I save it, I use

EngWS.Parent.Save.

Today, once it gets to that line, execution just stops. I'm running this
out of an Add-In if that provides any more clues. FWIW, the file I'm working
on is saved on my desktop.

Has anyone seen this problem before and what do I do?

Thanks,
Barb Reinhardt

Macro stops running at an unexpected time
 

That was us. We sent Morgo the Friendly Drelb to help you.



--
Time is just the thing that keeps everything from happening all at once


"Barb Reinhardt" wrote:

OK, now it's working and I've change nothing. There are gremlins in my
system today. I've had one problem after another.

Thanks,
Barb Reinhardt

"Barb Reinhardt" wrote:

I've been running this macro for some time and am having this problem today.
I define a worksheet that I'm acting on as EngWS. In the procedure I'm
using, I don't have a reference to the workbook so when I save it, I use

EngWS.Parent.Save.

Today, once it gets to that line, execution just stops. I'm running this
out of an Add-In if that provides any more clues. FWIW, the file I'm working
on is saved on my desktop.

Has anyone seen this problem before and what do I do?

Thanks,
Barb Reinhardt