When do you get the error -- when you are running the code or just
sitting in the workbook? If it happens when you are running the code,
try stepping through the code and posting the section that caused the
error.

Thx,
JP


On Jan 20, 12:30*am, Greg Wilson
wrote:
I have a project with a relatively large amount of code. I now often get the
message: "Excel has encountered a problem and needs to close. We are sorry
for the inconvenience." I have used Rob Bovey's Code Cleaner several times to
no avail. I have no OLE objects in the project. It doesn't happen
often/reliably enough to try process of elimination, selectively commenting
out code and testing if it still happens. So I cannot source the problem.

I think it only happens after working on the code, and if I get it to go
away and don't do any more work on it, it may be OK. At least once, I made
the problem go away by just opening a code module and closing it without
making a single change. Weird?

Moday is the grand debut !!!

Hoping someone can provide a list of the usual suspects or has some good
suggestioins.

Much appreciative.

Greg *

Thanks JP for responding. It happens on opening the wb. The Debug toolbar's
Compile VBAProject finds no syntax errors in the project. The Workbook_Open
event only does a few things, all of which are correct. The problem only
happens occasionally. This makes me think it's due to some form of
corruption. See my post to Jim.

Thanks again.

Greg

"JP" wrote:

When do you get the error -- when you are running the code or just
sitting in the workbook? If it happens when you are running the code,
try stepping through the code and posting the section that caused the
error.

Thx,
JP


On Jan 20, 12:30 am, Greg Wilson
wrote:
I have a project with a relatively large amount of code. I now often get the
message: "Excel has encountered a problem and needs to close. We are sorry
for the inconvenience." I have used Rob Bovey's Code Cleaner several times to
no avail. I have no OLE objects in the project. It doesn't happen
often/reliably enough to try process of elimination, selectively commenting
out code and testing if it still happens. So I cannot source the problem.

I think it only happens after working on the code, and if I get it to go
away and don't do any more work on it, it may be OK. At least once, I made
the problem go away by just opening a code module and closing it without
making a single change. Weird?

Moday is the grand debut !!!

Hoping someone can provide a list of the usual suspects or has some good
suggestioins.

Much appreciative.

Greg