By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,984 Members | 1,092 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,984 IT Pros & Developers. It's quick & easy.

Print friendly page

P: n/a
Hi,

I have a asp .net/VB web app that does the typical submitting and
retrieving from a SQL database. I am lost as to how I should create a
print friendly page for the data. Here is the situation. The user is
looking at a page with Text, asp .net controls, and buttons. I want
the user to be able to hit a print friendly button and a new window
will open, but this new window will have only plain text. Database
fields -- and database values. I need to build this page somehow, and
it would be great if I could reference the values in the exisiting
form instead of calling to the database again. Right?

Thanks all.
Nov 18 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
This is the sort of place where session comes handy. Store the data that you
would like to reuse in Sessio object(s) and then load your printer friendly
page.
server side printer friendlly code.. read those session values and off you
go

--

Regards,

Hermit Dave
(http://hdave.blogspot.com)
"Matt Mercer" <ma******@bellsouth.net> wrote in message
news:37**************************@posting.google.c om...
Hi,

I have a asp .net/VB web app that does the typical submitting and
retrieving from a SQL database. I am lost as to how I should create a
print friendly page for the data. Here is the situation. The user is
looking at a page with Text, asp .net controls, and buttons. I want
the user to be able to hit a print friendly button and a new window
will open, but this new window will have only plain text. Database
fields -- and database values. I need to build this page somehow, and
it would be great if I could reference the values in the exisiting
form instead of calling to the database again. Right?

Thanks all.

Nov 18 '05 #2

P: n/a
Also,

You dont have to store those values in session unless ans until the user
clicks the "print friendly button".
You cant handle that in the click event handler. And, after loading the
other page with the session stored information you can Remove those values
created in session. Just to keep everything cleaned up.

Just a thought.

Jeff B
je***@aaon.com
"Hermit Dave" <he************@CAPS.AND.DOTS.hotmail.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
This is the sort of place where session comes handy. Store the data that you would like to reuse in Sessio object(s) and then load your printer friendly page.
server side printer friendlly code.. read those session values and off you
go

--

Regards,

Hermit Dave
(http://hdave.blogspot.com)
"Matt Mercer" <ma******@bellsouth.net> wrote in message
news:37**************************@posting.google.c om...
Hi,

I have a asp .net/VB web app that does the typical submitting and
retrieving from a SQL database. I am lost as to how I should create a
print friendly page for the data. Here is the situation. The user is
looking at a page with Text, asp .net controls, and buttons. I want
the user to be able to hit a print friendly button and a new window
will open, but this new window will have only plain text. Database
fields -- and database values. I need to build this page somehow, and
it would be great if I could reference the values in the exisiting
form instead of calling to the database again. Right?

Thanks all.


Nov 18 '05 #3

P: n/a
true again.. but if he just wants to make one call he will need to set it
before the current page is rendered.
well viewstate can also be used. but i agree on clean up... remove
everything you are not using

--

Regards,

Hermit Dave
(http://hdave.blogspot.com)
"Jeff B" <je*******@hotmail.com> wrote in message
news:es**************@tk2msftngp13.phx.gbl...
Also,

You dont have to store those values in session unless ans until the user
clicks the "print friendly button".
You cant handle that in the click event handler. And, after loading the
other page with the session stored information you can Remove those values
created in session. Just to keep everything cleaned up.

Just a thought.

Jeff B
je***@aaon.com
"Hermit Dave" <he************@CAPS.AND.DOTS.hotmail.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
This is the sort of place where session comes handy. Store the data that

you
would like to reuse in Sessio object(s) and then load your printer

friendly
page.
server side printer friendlly code.. read those session values and off you go

--

Regards,

Hermit Dave
(http://hdave.blogspot.com)
"Matt Mercer" <ma******@bellsouth.net> wrote in message
news:37**************************@posting.google.c om...
Hi,

I have a asp .net/VB web app that does the typical submitting and
retrieving from a SQL database. I am lost as to how I should create a
print friendly page for the data. Here is the situation. The user is
looking at a page with Text, asp .net controls, and buttons. I want
the user to be able to hit a print friendly button and a new window
will open, but this new window will have only plain text. Database
fields -- and database values. I need to build this page somehow, and
it would be great if I could reference the values in the exisiting
form instead of calling to the database again. Right?

Thanks all.



Nov 18 '05 #4

P: n/a
how about creating a printer friendly stylesheet. When the user clicks print
you use the printer friendly styelsheet.
why save anything in session, use a new CSS.

http://www.411asp.net/ has some examples on this

"Hermit Dave" wrote:
true again.. but if he just wants to make one call he will need to set it
before the current page is rendered.
well viewstate can also be used. but i agree on clean up... remove
everything you are not using

--

Regards,

Hermit Dave
(http://hdave.blogspot.com)
"Jeff B" <je*******@hotmail.com> wrote in message
news:es**************@tk2msftngp13.phx.gbl...
Also,

You dont have to store those values in session unless ans until the user
clicks the "print friendly button".
You cant handle that in the click event handler. And, after loading the
other page with the session stored information you can Remove those values
created in session. Just to keep everything cleaned up.

Just a thought.

Jeff B
je***@aaon.com
"Hermit Dave" <he************@CAPS.AND.DOTS.hotmail.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
This is the sort of place where session comes handy. Store the data that

you
would like to reuse in Sessio object(s) and then load your printer

friendly
page.
server side printer friendlly code.. read those session values and off you go

--

Regards,

Hermit Dave
(http://hdave.blogspot.com)
"Matt Mercer" <ma******@bellsouth.net> wrote in message
news:37**************************@posting.google.c om...
> Hi,
>
> I have a asp .net/VB web app that does the typical submitting and
> retrieving from a SQL database. I am lost as to how I should create a
> print friendly page for the data. Here is the situation. The user is
> looking at a page with Text, asp .net controls, and buttons. I want
> the user to be able to hit a print friendly button and a new window
> will open, but this new window will have only plain text. Database
> fields -- and database values. I need to build this page somehow, and
> it would be great if I could reference the values in the exisiting
> form instead of calling to the database again. Right?
>
> Thanks all.



Nov 18 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.