I currently am running CF 8.0.1 on a Windows 2003 server, IIS 6.0 and SQL
Server 2000 in a production environment. I am testing this configuration on a
Windows Vista Business workstation. Everything seems to work as normal, except
for modules that create Excel spreadsheets that are viewed via the Web. I have
them coded using:

<cfheader name="Content-Disposition" value="inline; filename=#lcFile#.xls">
<cfcontent type="application/msexcel">

With a table definition, and cfloop to load the table.
This opens up in a Web page, with the option to open or save the file. Using
a Vista workstation, the table opens up in Excel, not using a Web page.
Although this probably is not an issue, the behavior is different. Does anyone
know: Is this the expected behavior? Is there a way to force it to behave the
same - opening up a Web browser page instead of Excel?

Any thoughts are appreciated.

Libby H wrote:
> This opens up in a Web page, with the option to open or save the file. Using
> a Vista workstation, the table opens up in Excel, not using a Web page.
> Although this probably is not an issue, the behavior is different. Does anyone
> know: Is this the expected behavior? Is there a way to force it to behave the
> same - opening up a Web browser page instead of Excel?
>
> Any thoughts are appreciated.
>

I don't think so, because I've got to believe at least some of this is
client controlled. I.E. it is going to depend on what version of Excel
is installed on the client, what browser they use and whether Excel is
registered as a plug-in for that browser or not.

With that much variability outside of the control of the web
application. Personally I would just leave it that you are delivering
Excel content. Then leave it up to the clients and their users to
determine how they utilize it when they receive it.