Sudden Excel Problem after XP SP2 install
 

First of all, I look to this site ALOT and find tons of useful
information here. Thanks!

Here's my problem:

User base has Office 2002 and just received an XP Service Pack 2
install. Suddenly, when using Excel, they are experiencing a generic
'Microsoft Excel has encountered a problem and needs to close...'.
There have been no other recent updates to the spreadsheets.

The spreadsheets they are using all get this error when they click on
an ActiveX button that runs code. The code gathers data from the
spreadsheet and creates a set of xml that then gets sent to a service
on our server.

We found a work around (a real icky one). When we go into the VBE and
select Tools... References... Then 'uncheck' any one of the
references. Click OK. Then, go right back into Tools... References...
and 'check' the same reference. Click OK. Once this has been done,
the spreadsheet works fine. However, this has to be done to EACH
spreadsheet. NOT GOOD. Also, this is not something we want the users
to have to do.

Any idea what caused this to begin with?

Any idea what actually happens when you go through the Tools...
References... dialog? It seems like 'something' get 'recalibrated' in
some way. If we can find out what is happening, maybe that would lead
us to a way to fix this.

HELP!!!

Sudden Excel Problem after XP SP2 install
 

Lisa,

Can't answer your question directly, but there were many things I found
several years back that contributed to Excel crashes.

1. Some folders have too much stuff in them -
Temp Folders, especially the ones holding internet Temp files
Recycle Bin
some mail folders
sometimes excess number of unread messages in the newsgroup.
2. Code conflicts -
Have a variable declared as Public and than the save variable
declared as Private or Dim
Using Excel Words as Names in the worksheet and/or in code. I check
this by highlighting
the word and hitting F1. If it is safe to use, Excel won't find
anything in help.
Modules and/Code with the same exact name.
Undetected errors in code
3. Use the compiler in the VBE to check your code. It helps to have Option
Explict at the top of
all modules.
4. Download and use the code cleaner at this site:
http://www.appspro.com/Utilities/CodeCleaner.htm
--
steveB

Remove "AYN" from email to respond
"LisaKan" wrote in message
ups.com...
First of all, I look to this site ALOT and find tons of useful
information here. Thanks!

Here's my problem:

User base has Office 2002 and just received an XP Service Pack 2
install. Suddenly, when using Excel, they are experiencing a generic
'Microsoft Excel has encountered a problem and needs to close...'.
There have been no other recent updates to the spreadsheets.

The spreadsheets they are using all get this error when they click on
an ActiveX button that runs code. The code gathers data from the
spreadsheet and creates a set of xml that then gets sent to a service
on our server.

We found a work around (a real icky one). When we go into the VBE and
select Tools... References... Then 'uncheck' any one of the
references. Click OK. Then, go right back into Tools... References...
and 'check' the same reference. Click OK. Once this has been done,
the spreadsheet works fine. However, this has to be done to EACH
spreadsheet. NOT GOOD. Also, this is not something we want the users
to have to do.

Any idea what caused this to begin with?

Any idea what actually happens when you go through the Tools...
References... dialog? It seems like 'something' get 'recalibrated' in
some way. If we can find out what is happening, maybe that would lead
us to a way to fix this.

HELP!!!

Sudden Excel Problem after XP SP2 install
 

Lisa,

(sent too quickly)

Make sure that your computer is clean: viruses and such.
Do a disc check and defrag (I use Norton Disc Doctor and Speed Disc)

Also check you workbooks:
Excessive formatting, number of fonts, number of custom formats (that
you don't use),
too many formulas, query's, pivot tables, charts, forms, objects, etc.

And the list goes on.

Of course it could just be a conflict with the SP.

Good Luck!

--
steveB

Remove "AYN" from email to respond
"STEVE BELL" wrote in message
news:jzi%e.524$JY6.478@trnddc02...
Lisa,

Can't answer your question directly, but there were many things I found
several years back that contributed to Excel crashes.

1. Some folders have too much stuff in them -
Temp Folders, especially the ones holding internet Temp files
Recycle Bin
some mail folders
sometimes excess number of unread messages in the newsgroup.
2. Code conflicts -
Have a variable declared as Public and than the save variable
declared as Private or Dim
Using Excel Words as Names in the worksheet and/or in code. I
check this by highlighting
the word and hitting F1. If it is safe to use, Excel won't
find anything in help.
Modules and/Code with the same exact name.
Undetected errors in code
3. Use the compiler in the VBE to check your code. It helps to have
Option Explict at the top of
all modules.
4. Download and use the code cleaner at this site:
http://www.appspro.com/Utilities/CodeCleaner.htm
--
steveB

Remove "AYN" from email to respond
"LisaKan" wrote in message
ups.com...
First of all, I look to this site ALOT and find tons of useful
information here. Thanks!

Here's my problem:

User base has Office 2002 and just received an XP Service Pack 2
install. Suddenly, when using Excel, they are experiencing a generic
'Microsoft Excel has encountered a problem and needs to close...'.
There have been no other recent updates to the spreadsheets.

The spreadsheets they are using all get this error when they click on
an ActiveX button that runs code. The code gathers data from the
spreadsheet and creates a set of xml that then gets sent to a service
on our server.

We found a work around (a real icky one). When we go into the VBE and
select Tools... References... Then 'uncheck' any one of the
references. Click OK. Then, go right back into Tools... References...
and 'check' the same reference. Click OK. Once this has been done,
the spreadsheet works fine. However, this has to be done to EACH
spreadsheet. NOT GOOD. Also, this is not something we want the users
to have to do.

Any idea what caused this to begin with?

Any idea what actually happens when you go through the Tools...
References... dialog? It seems like 'something' get 'recalibrated' in
some way. If we can find out what is happening, maybe that would lead
us to a way to fix this.

HELP!!!

Sudden Excel Problem after XP SP2 install
 

Just remembered one other possibility -
the workbook might be corrupted.

--
steveB

Remove "AYN" from email to respond
"STEVE BELL" wrote in message
news:CFi%e.534$JY6.18@trnddc02...
Lisa,

(sent too quickly)

Make sure that your computer is clean: viruses and such.
Do a disc check and defrag (I use Norton Disc Doctor and Speed Disc)

Also check you workbooks:
Excessive formatting, number of fonts, number of custom formats (that
you don't use),
too many formulas, query's, pivot tables, charts, forms, objects, etc.

And the list goes on.

Of course it could just be a conflict with the SP.

Good Luck!

--
steveB

Remove "AYN" from email to respond
"STEVE BELL" wrote in message
news:jzi%e.524$JY6.478@trnddc02...
Lisa,

Can't answer your question directly, but there were many things I found
several years back that contributed to Excel crashes.

1. Some folders have too much stuff in them -
Temp Folders, especially the ones holding internet Temp files
Recycle Bin
some mail folders
sometimes excess number of unread messages in the newsgroup.
2. Code conflicts -
Have a variable declared as Public and than the save variable
declared as Private or Dim
Using Excel Words as Names in the worksheet and/or in code. I
check this by highlighting
the word and hitting F1. If it is safe to use, Excel won't
find anything in help.
Modules and/Code with the same exact name.
Undetected errors in code
3. Use the compiler in the VBE to check your code. It helps to have
Option Explict at the top of
all modules.
4. Download and use the code cleaner at this site:
http://www.appspro.com/Utilities/CodeCleaner.htm
--
steveB

Remove "AYN" from email to respond
"LisaKan" wrote in message
ups.com...
First of all, I look to this site ALOT and find tons of useful
information here. Thanks!

Here's my problem:

User base has Office 2002 and just received an XP Service Pack 2
install. Suddenly, when using Excel, they are experiencing a generic
'Microsoft Excel has encountered a problem and needs to close...'.
There have been no other recent updates to the spreadsheets.

The spreadsheets they are using all get this error when they click on
an ActiveX button that runs code. The code gathers data from the
spreadsheet and creates a set of xml that then gets sent to a service
on our server.

We found a work around (a real icky one). When we go into the VBE and
select Tools... References... Then 'uncheck' any one of the
references. Click OK. Then, go right back into Tools... References...
and 'check' the same reference. Click OK. Once this has been done,
the spreadsheet works fine. However, this has to be done to EACH
spreadsheet. NOT GOOD. Also, this is not something we want the users
to have to do.

Any idea what caused this to begin with?

Any idea what actually happens when you go through the Tools...
References... dialog? It seems like 'something' get 'recalibrated' in
some way. If we can find out what is happening, maybe that would lead
us to a way to fix this.

HELP!!!

Sudden Excel Problem after XP SP2 install
 

Hi Steve,

Was reading your help for Lisa. What do you think about the fact that Excel is the biggest, baddest spreadsheet on Earth, but we
have to jump through all of the hoops you mentioned just to make it work like it is supposed to? I have a client who is struggling
with a spreadsheet that has 45,000 rows. It does not have any arrays or any fancy stuff, just a lot of rows, not many columns. It
takes FOREVER to recalculate. Shouldn't the most advanced spreadsheet be able to handle all of the features it gives us, even if we
fill it completely up, including its "incredibly generous" 256 Columns? Just looking at your list of items which cause Excel to
throw a breaker is annoying. Microsoft owes us either complete functionality or disclosure that even with all the memory in the
world, Excel simply can't handle the things you mentioned. Do you agree?

Thanks,

Richard
--
RMC,CPA


"STEVE BELL" wrote in message news:jdj%e.615$JY6.484@trnddc02...
Just remembered one other possibility -
the workbook might be corrupted.

--
steveB

Remove "AYN" from email to respond
"STEVE BELL" wrote in message
news:CFi%e.534$JY6.18@trnddc02...
Lisa,

(sent too quickly)

Make sure that your computer is clean: viruses and such.
Do a disc check and defrag (I use Norton Disc Doctor and Speed Disc)

Also check you workbooks:
Excessive formatting, number of fonts, number of custom formats (that
you don't use),
too many formulas, query's, pivot tables, charts, forms, objects, etc.

And the list goes on.

Of course it could just be a conflict with the SP.

Good Luck!

--
steveB

Remove "AYN" from email to respond
"STEVE BELL" wrote in message
news:jzi%e.524$JY6.478@trnddc02...
Lisa,

Can't answer your question directly, but there were many things I found
several years back that contributed to Excel crashes.

1. Some folders have too much stuff in them -
Temp Folders, especially the ones holding internet Temp files
Recycle Bin
some mail folders
sometimes excess number of unread messages in the newsgroup.
2. Code conflicts -
Have a variable declared as Public and than the save variable
declared as Private or Dim
Using Excel Words as Names in the worksheet and/or in code. I
check this by highlighting
the word and hitting F1. If it is safe to use, Excel won't
find anything in help.
Modules and/Code with the same exact name.
Undetected errors in code
3. Use the compiler in the VBE to check your code. It helps to have
Option Explict at the top of
all modules.
4. Download and use the code cleaner at this site:
http://www.appspro.com/Utilities/CodeCleaner.htm
--
steveB

Remove "AYN" from email to respond
"LisaKan" wrote in message
ups.com...
First of all, I look to this site ALOT and find tons of useful
information here. Thanks!

Here's my problem:

User base has Office 2002 and just received an XP Service Pack 2
install. Suddenly, when using Excel, they are experiencing a generic
'Microsoft Excel has encountered a problem and needs to close...'.
There have been no other recent updates to the spreadsheets.

The spreadsheets they are using all get this error when they click on
an ActiveX button that runs code. The code gathers data from the
spreadsheet and creates a set of xml that then gets sent to a service
on our server.

We found a work around (a real icky one). When we go into the VBE and
select Tools... References... Then 'uncheck' any one of the
references. Click OK. Then, go right back into Tools... References...
and 'check' the same reference. Click OK. Once this has been done,
the spreadsheet works fine. However, this has to be done to EACH
spreadsheet. NOT GOOD. Also, this is not something we want the users
to have to do.

Any idea what caused this to begin with?

Any idea what actually happens when you go through the Tools...
References... dialog? It seems like 'something' get 'recalibrated' in
some way. If we can find out what is happening, maybe that would lead
us to a way to fix this.

HELP!!!

Sudden Excel Problem after XP SP2 install
 

Richard,

Every product I have ever owned had good features, bad features, annoying
features, etc... Look around any office and you will most likely see all
kinds of add-ons, tack-ons, work-arounds, etc. I have a great car with lots
of bells-n-whistles, but even this "could be better".

You see - we are both looking for something that is custom made for us, and
that would come at a great cost.

Having dabbled in building code within Excel I have learned to appreciate
what the "real" programmers go through.
No one can foresee every situation. And every innovation brings out another
"detour".

Microsoft is getting better at dealing with some of these. But at the same
time they take away some things that worked great. And now we have the
conflict of 2000 vs 2003. It's like we just can't win.

So my solution is to work with what I've got. And Excel is pretty powerful
for most of the stuff I work on. And I continually find ways and methods to
get around some of the difficulties.

Large workbooks with lots of formulas bog down real fast. The trick is to
simplify as much as possible (a pain). Sometimes you can have the code do
the calculations (instead of using formulas) and it can speed things up.

Yes it would be great to fill sheet after sheet with all kinds of "stuff"
and have Excel respond instantly - but you can't.
I could fill a book with all the things I want to do but am restricted (what
a bummer). Yet I remember all the things I can do and get excited.
Kind of like the cup that is half-full or half-empty...

Now you've got me started!

It's also like the guy who always came to his boss with all kinds of
problems. Than one day his boss told him not to come back until he had some
solutions to go with the problems.

It's not a perfect world...

Happy Exceling...

--
steveB

Remove "AYN" from email to respond
"R. Choate" wrote in message
...
Hi Steve,

Was reading your help for Lisa. What do you think about the fact that
Excel is the biggest, baddest spreadsheet on Earth, but we
have to jump through all of the hoops you mentioned just to make it work
like it is supposed to? I have a client who is struggling
with a spreadsheet that has 45,000 rows. It does not have any arrays or
any fancy stuff, just a lot of rows, not many columns. It
takes FOREVER to recalculate. Shouldn't the most advanced spreadsheet be
able to handle all of the features it gives us, even if we
fill it completely up, including its "incredibly generous" 256 Columns?
Just looking at your list of items which cause Excel to
throw a breaker is annoying. Microsoft owes us either complete
functionality or disclosure that even with all the memory in the
world, Excel simply can't handle the things you mentioned. Do you agree?

Thanks,

Richard
--
RMC,CPA


"STEVE BELL" wrote in message
news:jdj%e.615$JY6.484@trnddc02...
Just remembered one other possibility -
the workbook might be corrupted.

--
steveB

Remove "AYN" from email to respond
"STEVE BELL" wrote in message
news:CFi%e.534$JY6.18@trnddc02...
Lisa,

(sent too quickly)

Make sure that your computer is clean: viruses and such.
Do a disc check and defrag (I use Norton Disc Doctor and Speed Disc)

Also check you workbooks:
Excessive formatting, number of fonts, number of custom formats (that
you don't use),
too many formulas, query's, pivot tables, charts, forms, objects, etc.

And the list goes on.

Of course it could just be a conflict with the SP.

Good Luck!

--
steveB

Remove "AYN" from email to respond
"STEVE BELL" wrote in message
news:jzi%e.524$JY6.478@trnddc02...
Lisa,

Can't answer your question directly, but there were many things I found
several years back that contributed to Excel crashes.

1. Some folders have too much stuff in them -
Temp Folders, especially the ones holding internet Temp files
Recycle Bin
some mail folders
sometimes excess number of unread messages in the newsgroup.
2. Code conflicts -
Have a variable declared as Public and than the save variable
declared as Private or Dim
Using Excel Words as Names in the worksheet and/or in code. I
check this by highlighting
the word and hitting F1. If it is safe to use, Excel won't
find anything in help.
Modules and/Code with the same exact name.
Undetected errors in code
3. Use the compiler in the VBE to check your code. It helps to have
Option Explict at the top of
all modules.
4. Download and use the code cleaner at this site:
http://www.appspro.com/Utilities/CodeCleaner.htm
--
steveB

Remove "AYN" from email to respond
"LisaKan" wrote in message
ups.com...
First of all, I look to this site ALOT and find tons of useful
information here. Thanks!

Here's my problem:

User base has Office 2002 and just received an XP Service Pack 2
install. Suddenly, when using Excel, they are experiencing a generic
'Microsoft Excel has encountered a problem and needs to close...'.
There have been no other recent updates to the spreadsheets.

The spreadsheets they are using all get this error when they click on
an ActiveX button that runs code. The code gathers data from the
spreadsheet and creates a set of xml that then gets sent to a service
on our server.

We found a work around (a real icky one). When we go into the VBE and
select Tools... References... Then 'uncheck' any one of the
references. Click OK. Then, go right back into Tools... References...
and 'check' the same reference. Click OK. Once this has been done,
the spreadsheet works fine. However, this has to be done to EACH
spreadsheet. NOT GOOD. Also, this is not something we want the users
to have to do.

Any idea what caused this to begin with?

Any idea what actually happens when you go through the Tools...
References... dialog? It seems like 'something' get 'recalibrated' in
some way. If we can find out what is happening, maybe that would lead
us to a way to fix this.

HELP!!!