The current implementation of the print feature is somewhat annoying for end users. Since it relies on the querystring, it loses the view-state, which means users must re-apply whatever sorting and paging to get the view they once had. Also, since the skin and container styles aren't applied, the printable version is actually uglier than one might want.

Has anyone worked around any of these issues? Not sure if there's an easy work-around to accomplish some of these tasks in a better way. If I have to implement printing in custom modules to keep the view-state, I will, but I'm hoping there's a way around it that someone else has found. Any help is appreciated!

---

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com

This has always been a thorn in my side. I usually end up creating my own print button in the module and popping up the page in the print container and rerunning whatever logic I need to. Uggghhh

Major opportunity for enhancement

---

Erik Hinds
Risdall Marketing Group
#1 Web Design Agency in the World

www.risdall.com | www.risdall.net | erik AT risdall DOT-COM