All
Here is a interesting problem that I would love to debug.
I have a workbook that use to run great on a user's machine. However, now that same machine's Excel blows up when this particular file is opened. As a matter of fact any version old or new of this file gives up the Ghost. Funny thing is this tool is used on about 100 other machines with no issues.
I pulled the file to several other machines and verified the file opens up no problem and works fine. It appears to only be her machine that has been stricken.
So to try and debug something at all - I went into the workbook OPEN procedure which was the only thing I could imagine causing the blow up and placed a stop at the beginning of that code and then retried the file on her machine to try and debug what was going on. Opening the workbook stopped the code at the workbook OPEN and I started stepping through the code. Guess what - the code made it all the freaking way though no problem. Hmmmm... well that made no sense. I was hoping to be led to something.
So I remark out the stop and save off the workbook and ran it with the only thing having changed was the addition of the stop comment and viola the thing works.
Thinking something might have been unclogged (what that something is I have no idea) I tried running the tool again sans new comment. Excel once again gives up the ghost. I run the code with the stop comment and it opens no problem. So I am really scratching my head now. All I did was add in a freaking comment to the code. I mean REALLY!!!!
At any rate I am somewhat happy - after all I did place a very important comment in the code and the dang thing now at least opens without Excel giving up the ghost so YAY ME! the thing now works. (So I think)
But no... I then attempt to run the main meat of the workbook and low and behold the code acts like it is skipping code chunks and stuff not running when it is suppose to run and items happening without a care for waiting for code to complete before running the next line. I mean whole snippets of code are not being done. Example - if I connect the workbook to another spreadsheet to read data from it, all I get is the prompt saying complete, but nothing is being read from that spreadsheet.
As mentioned this code is used throughout the group and runs on about 100 machines, but this one user's machine is all of a sudden stricken with something crazy. After all - 3 months ago it was running fine on this same machine. I checked for recent installs of items that might have killed something, but can't see anything. We also tested her previous work done with this workbook using the same files she still has archived from that project and now it too gives up the ghost. Last March everything was great.
Shooting in the dark - Excel 2007 has been reinstalled on her machine, but that fixed nothing and it still giving up the ghost when that most vital comment is not added.
Has anyone ever seen or even heard of something like this and barring a complete system refresh are there any solutions?
FM3
Here is a interesting problem that I would love to debug.
I have a workbook that use to run great on a user's machine. However, now that same machine's Excel blows up when this particular file is opened. As a matter of fact any version old or new of this file gives up the Ghost. Funny thing is this tool is used on about 100 other machines with no issues.
I pulled the file to several other machines and verified the file opens up no problem and works fine. It appears to only be her machine that has been stricken.
So to try and debug something at all - I went into the workbook OPEN procedure which was the only thing I could imagine causing the blow up and placed a stop at the beginning of that code and then retried the file on her machine to try and debug what was going on. Opening the workbook stopped the code at the workbook OPEN and I started stepping through the code. Guess what - the code made it all the freaking way though no problem. Hmmmm... well that made no sense. I was hoping to be led to something.
So I remark out the stop and save off the workbook and ran it with the only thing having changed was the addition of the stop comment and viola the thing works.
Thinking something might have been unclogged (what that something is I have no idea) I tried running the tool again sans new comment. Excel once again gives up the ghost. I run the code with the stop comment and it opens no problem. So I am really scratching my head now. All I did was add in a freaking comment to the code. I mean REALLY!!!!
At any rate I am somewhat happy - after all I did place a very important comment in the code and the dang thing now at least opens without Excel giving up the ghost so YAY ME! the thing now works. (So I think)
But no... I then attempt to run the main meat of the workbook and low and behold the code acts like it is skipping code chunks and stuff not running when it is suppose to run and items happening without a care for waiting for code to complete before running the next line. I mean whole snippets of code are not being done. Example - if I connect the workbook to another spreadsheet to read data from it, all I get is the prompt saying complete, but nothing is being read from that spreadsheet.
As mentioned this code is used throughout the group and runs on about 100 machines, but this one user's machine is all of a sudden stricken with something crazy. After all - 3 months ago it was running fine on this same machine. I checked for recent installs of items that might have killed something, but can't see anything. We also tested her previous work done with this workbook using the same files she still has archived from that project and now it too gives up the ghost. Last March everything was great.
Shooting in the dark - Excel 2007 has been reinstalled on her machine, but that fixed nothing and it still giving up the ghost when that most vital comment is not added.
Has anyone ever seen or even heard of something like this and barring a complete system refresh are there any solutions?
FM3
