software

I have a classic asp application that routes it's output to Excel via Internet Explorer.
It's worked for 6 years without a problem. Last week some of my users upgraded to Excel 2003. Now the spreadsheet won't be created. The code still works on Excel 2000 but on the new machines a window appears but it closes before Excel can be seen.

The code in the script looks like this...

Case quot;Excelquot;
Response.ContentType=quot;application/vnd.ms-excelquot;

After searching this newsgroup i've added the following lines to the code but they don't seem to fix the problem...
Response.Buffer = True
Response.charset = quot;quot;

This code sample in this knowledgebase article works on both Office 2000 and 2003 machines, but i tried to tailor it to my script without luck. Any ideas?
support.microsoft.com/default...;en-us;Q271572Hello,
I am taking a wild punt here, in other words, I am guessing...
Maybe you need to declare quot;everythingquot;
strings, objects etc

I believe (have heard? [have read?]) that EXCEL 2003 needs just about
quot;everythingquot; to be dimmed in one way or another.

also, if you are referencing an object like a textbox,label, shape, you have
to use its extension-type.
..caption, .text etc

eg: instead of
if textbox1=strwhat then
....
you use
if textbox1.text=strwhat then
....

Also, I do not know if you use the Left or Right function but you be better
to use the global Mid Function.

Hopes this help otherwise please ignore my ramblings ....
quot;David Alexanderquot; wrote:

gt; I have a classic asp application that routes it's output to Excel via Internet Explorer.
gt; It's worked for 6 years without a problem. Last week some of my users upgraded to Excel 2003. Now the spreadsheet won't be created. The code still works on Excel 2000 but on the new machines a window appears but it closes before Excel can be seen.
gt;
gt; The code in the script looks like this...
gt;
gt; Case quot;Excelquot;
gt; Response.ContentType=quot;application/vnd.ms-excelquot;
gt;
gt; After searching this newsgroup i've added the following lines to the code but they don't seem to fix the problem...
gt;
gt; Response.Buffer = True
gt; Response.charset = quot;quot;
gt;
gt; This code sample in this knowledgebase article works on both Office 2000 and 2003 machines, but i tried to tailor it to my script without luck. Any ideas?
gt; support.microsoft.com/default...;en-us;Q271572
gt;

Thanks for your guess, i think the culprit was XP SP2 or at the very least a security setting. By adding our site to the list of trusted Local Intranet Sites, the problem was corrected. gt;gt;gt; osoft.comgt; 2/22/06 8:58:27 PM gt;gt;gt;

Hello,
I am taking a wild punt here, in other words, I am guessing...
Maybe you need to declare quot;everythingquot;
strings, objects etc

I believe (have heard? [have read?]) that EXCEL 2003 needs just about
quot;everythingquot; to be dimmed in one way or another.

also, if you are referencing an object like a textbox,label, shape, you have
to use its extension-type.
..caption, .text etc

eg: instead of
if textbox1=strwhat then
....
you use
if textbox1.text=strwhat then
....

Also, I do not know if you use the Left or Right function but you be better
to use the global Mid Function.

Hopes this help otherwise please ignore my ramblings ....
quot;David Alexanderquot; wrote:

gt; I have a classic asp application that routes it's output to Excel via Internet Explorer.
gt; It's worked for 6 years without a problem. Last week some of my users upgraded to Excel 2003. Now the spreadsheet won't be created. The code still works on Excel 2000 but on the new machines a window appears but it closes before Excel can be seen.
gt;
gt; The code in the script looks like this...
gt;
gt; Case quot;Excelquot;
gt; Response.ContentType=quot;application/vnd.ms-excelquot;
gt;
gt; After searching this newsgroup i've added the following lines to the code but they don't seem to fix the problem...
gt;
gt; Response.Buffer = True
gt; Response.charset = quot;quot;
gt;
gt; This code sample in this knowledgebase article works on both Office 2000 and 2003 machines, but i tried to tailor it to my script without luck. Any ideas?
gt; support.microsoft.com/default...;en-us;Q271572
gt;