>SNIP
>If you want to do it server-side using a DataTable, you can:
>- re-create the DataTable in the Export method
>- persist the DataTable from an earlier method, and use that
>
>If the latter, I agree with Bonnie, using Session state is one way to persist the DataTable e.g.
>Session["MyDataTable"] = dt;
>
>// In your Export method:
>DataTable dt = (DataTable)Session["MyDataTable"];
>// need to explicitly cast the Session object back to a DataTable
You'll have to decide if saving the DataTable in Session state is reasonable (not too large, won't hang around too long) and also remember to destroy it when you're finished with it.
Thanks. It was the latter one, about Session state as Bonnie said. I knew all the previous ones. :)
