"Downloading" datagrids

[spammy]

Hi all,

I have developed a pretty straightforward web app which displays the results
of a query in a datagrid.

I want to provide a "Download as csv" link, but want to generate this
without having to requery the database.

What's the best way to persist the underlying datatable? It's running on an
intranet and even then not that often. The datatable is around 1000 rows.

Current ideas include passing in viewstate, storing in session or generating
a temp file to serve. What are the pros and cons, and if possible
implementation tips?

Spammy

[Kostadin Kostov]

For an intranet solution maybe ViewState is the better approach, as it passes
the data "through the wire".
The session variables reside in the memory and are better approach when
connection overheat is to be avoided.
I would recommend using ViewState!

Hope that helps!
Regards,
Kostadin Kostov

"spammy" wrote:

Hi all,

I have developed a pretty straightforward web app which displays the results
of a query in a datagrid.

I want to provide a "Download as csv" link, but want to generate this
without having to requery the database.

What's the best way to persist the underlying datatable? It's running on an
intranet and even then not that often. The datatable is around 1000 rows.

Current ideas include passing in viewstate, storing in session or generating
a temp file to serve. What are the pros and cons, and if possible
implementation tips?

Spammy

[Ersin Gençtürk]

If performance is not critacal for your application you can generate cvs
file using guid filenames each time you generate datagrid.So you only need
to put a link to that generated cvs file.However , you have to write some
delete code in the session_end to delete unnecessary generated cvs files.

"spammy" <[e-mail]> wrote in message
news:38*************@individual.net...

Hi all,

I have developed a pretty straightforward web app which displays the results of a query in a datagrid.

I want to provide a "Download as csv" link, but want to generate this
without having to requery the database.

What's the best way to persist the underlying datatable? It's running on an intranet and even then not that often. The datatable is around 1000 rows.

Current ideas include passing in viewstate, storing in session or generating a temp file to serve. What are the pros and cons, and if possible
implementation tips?

Spammy

[Deasun]

Just taught you might be interested in this;
Infragistics WebGrid control comes with a ExcelExportor.
One line of code with export all data in the grid, even if your using pages,
to the clients PC. It pops up the save as dialog for them.
Real basic, drop the grid on page and the exportor and a btn/btnlink.
Under the btn put the one line of code and your done. Works great :)

Also note for the webgrid make sure you use pages and set page to have no
more then 200 rows at a time. Else speed gets hit real bad.

Also sense your in a intranet take a look at SmartClients. Using their
wingrid here is just awesome. Built in filters, sorting and a few
calculation summarys.

Ok will stop rant now :). It is good though. :)

Deasun
http://www.tirnaog.com

"spammy" wrote:

Hi all,

I have developed a pretty straightforward web app which displays the results
of a query in a datagrid.

I want to provide a "Download as csv" link, but want to generate this
without having to requery the database.

What's the best way to persist the underlying datatable? It's running on an
intranet and even then not that often. The datatable is around 1000 rows.

Current ideas include passing in viewstate, storing in session or generating
a temp file to serve. What are the pros and cons, and if possible
implementation tips?

Spammy

[spammy]

That sounds ideal I guess. I'm not too sure how sessions work though - when
would they expire? I mean suppose the user is reading the onscreen report
(which takes 30 mins), would the csv still be available, or would the
session end code fire?

Viewstate is still an option. I havn't heard anything against using a
session variable though...

Spammy

"Ersin Gençtürk" <ers[spam]@gencturk.org> wrote in message
news:uK**************@tk2msftngp13.phx.gbl...

If performance is not critacal for your application you can generate cvs
file using guid filenames each time you generate datagrid.So you only need
to put a link to that generated cvs file.However , you have to write some
delete code in the session_end to delete unnecessary generated cvs files.

"spammy" <[e-mail]> wrote in message
news:38*************@individual.net...

Hi all,

I have developed a pretty straightforward web app which displays the

results

of a query in a datagrid.

I want to provide a "Download as csv" link, but want to generate this
without having to requery the database.

What's the best way to persist the underlying datatable? It's running on

an

intranet and even then not that often. The datatable is around 1000 rows.
Current ideas include passing in viewstate, storing in session or

generating

a temp file to serve. What are the pros and cons, and if possible
implementation tips?

Spammy

[Ersin Gençtürk]

you can adjust your application's session time out in your web.config
file.If you want you can adjust it for 30 mins.

"spammy" <[e-mail]> wrote in message
news:38*************@individual.net...

That sounds ideal I guess. I'm not too sure how sessions work though - when would they expire? I mean suppose the user is reading the onscreen report
(which takes 30 mins), would the csv still be available, or would the
session end code fire?

Viewstate is still an option. I havn't heard anything against using a
session variable though...

Spammy

"Ersin Gençtürk" <ers[spam]@gencturk.org> wrote in message
news:uK**************@tk2msftngp13.phx.gbl...

If performance is not critacal for your application you can generate cvs
file using guid filenames each time you generate datagrid.So you only need

to put a link to that generated cvs file.However , you have to write some delete code in the session_end to delete unnecessary generated cvs files.
"spammy" <[e-mail]> wrote in message
news:38*************@individual.net...

Hi all,

I have developed a pretty straightforward web app which displays the

results

of a query in a datagrid.

I want to provide a "Download as csv" link, but want to generate this
without having to requery the database.

What's the best way to persist the underlying datatable? It's running

on an

intranet and even then not that often. The datatable is around 1000

rows.
Current ideas include passing in viewstate, storing in session or

generating

a temp file to serve. What are the pros and cons, and if possible
implementation tips?

Spammy

[Elton Wang]

Suppose a user keeps browser open and does something else,
after a half hour then click file link. Since the file was
deleted, an error will come out. How to you think this
situation?

Elton Wang
el********@hotmail.com

-----Original Message-----
If performance is not critacal for your application you can generate cvsfile using guid filenames each time you generate datagrid.So you only needto put a link to that generated cvs file.However , you have to write somedelete code in the session_end to delete unnecessary generated cvs files.
"spammy" <[e-mail]> wrote in message
news:38*************@individual.net...

Hi all,

I have developed a pretty straightforward web app which displays the

results

of a query in a datagrid.

I want to provide a "Download as csv" link, but want to

generate this without having to requery the database.

What's the best way to persist the underlying datatable? It's running onan

intranet and even then not that often. The datatable is

around 1000 rows.
Current ideas include passing in viewstate, storing in session orgenerating

a temp file to serve. What are the pros and cons, and

if possible implementation tips?

Spammy

.