Currently, we are opening Excel files using the Response option:

Response.ContentType="application/x-msexcel";
Response.AddHeader("Content-Disposition", "attachment; filename=" + localFileName);
Response.WriteFile(fileName);
Response.Flush();
Response.Close();

filename is the actual Excel file (contains a macro) and localFileName is asuggested name for saving the data file produced.

I am looking at allowing the called Excel to take in command line parameters using a GetCommandLine function in the Excel VBA (have tested Excel code tp do this and can read the full command line) but have not found a way of changing the C# code above to pass this through. Unfortunately, we are stuck with Framework 1.1 for the time being so need a solution that is compatible. Any ideas?

Cheers

Mark

"stainless" <(E-Mail Removed)> wrote in message
news:ea7879c6-ecaf-4a49-a6a5-(E-Mail Removed)...

> Currently, we are opening Excel files using the Response option:

Actually, you're not opening them, you're transmitting them.

> Response.ContentType="application/x-msexcel";
> Response.AddHeader("Content-Disposition", "attachment; filename=" +
> localFileName);
> Response.WriteFile(fileName);
> Response.Flush();
> Response.Close();

> filename is the actual Excel file (contains a macro) and localFileName is
> a suggested
> name for saving the data file produced.

> I am looking at allowing the called Excel to take in command line
> parameters using
> a GetCommandLine function in the Excel VBA (have tested Excel code tp do
> this
> and can read the full command line) but have not found a way of changing
> the C# code
> above to pass this through. Unfortunately, we are stuck with Framework 1.1
> for the time
> being so need a solution that is compatible. Any ideas?

I doubt this will ever happen, regardless of the .NET framework version.
There may not even be an equivalent of a command line on the client side,
and I also doubt that there's any mechanism to specify switches for it even
if it exists.

Simply put, executing a program to handle the received file is up to the
client (the browser), and has nothing to do with .NET.