My office uses an in-house SQL application to handle a lot of our day-
to-day financial functions. One of the tasks performed on a regular
basis is the export of a given table from this applicaiton into Excel
format. Several of my users have recently noticed that when they
attempt to open the file generated thusly, Excel crashes. (Usually not
the rest of the computer, just Excel.) It restarts and recovers the
files it had open, but there's a tendency for recovered files to have
weird formatting more often than not.

We had originally assumed this had something to do with the date
issues the Daylight Savings patch had caused, but we're past DST now
and all machines involved are patched.

We're using Excel 2003, patched with updates available as of 2/24/07,
and the SQL version involved is SQL Server 2005 SP1. If anyone has
suggestions as to what's going on, since the Event Log gives a couple
of hexadecimal numbers and can't seem to find related info for this
particular error, I'd be much obliged.

Thanks.

The first question I would have is: how large is the table being exported
into Excel and how much RAM do the computers in question have?

Dave
--
A hint to posters: Specific, detailed questions are more likely to be
answered than questions that provide no detail about your problem.


" wrote:

My office uses an in-house SQL application to handle a lot of our day-
to-day financial functions. One of the tasks performed on a regular
basis is the export of a given table from this applicaiton into Excel
format. Several of my users have recently noticed that when they
attempt to open the file generated thusly, Excel crashes. (Usually not
the rest of the computer, just Excel.) It restarts and recovers the
files it had open, but there's a tendency for recovered files to have
weird formatting more often than not.

We had originally assumed this had something to do with the date
issues the Daylight Savings patch had caused, but we're past DST now
and all machines involved are patched.

We're using Excel 2003, patched with updates available as of 2/24/07,
and the SQL version involved is SQL Server 2005 SP1. If anyone has
suggestions as to what's going on, since the Event Log gives a couple
of hexadecimal numbers and can't seem to find related info for this
particular error, I'd be much obliged.

Thanks.