If you use the CrystalReportViewer control to perform both roles (report display and object model), ViewState persists both of them, and you do not need any additional persistence mechanisms.
Please make sure
-Not Using ViewState Compression
-Not Handling Viewstate optimizations in basepage class
-Page ViewState is enabled
You can also use Session, or Cache as replacement of ViewState
Here is the link
commented on Dec 31 2011 5:39AM