Do not store large records in viewstate. The reason is that viewstate
round-trips on every postback so you will be lugging around these 1000
records to and fro. Store little strings. If you have the index as a string,
then that is fine. If you intend to store all the records, consider session
or cache.
Regards
Alvin Bruney
> Hi!,
> First I will explain what i am doing.
>
> Basically i have two pages.
> 1) List all the records he has to do work, and he can sort by anyfield.
> 2) When he clicks on one of the records in the list of records, he will redirected to a page, to that perticular record, where he can also work them
in that sort order. by Clicking next, prev, last, first.
> I am creating a array of primarykey, when he enters into the work page. Saving that in viewstate. And when he clicks next or last, i will get that
primarykey from the array and query against database. One user can have
1000s of records.
> But i read that viewstate can't be used for large memories...
>
[quoted text clipped - 3 lines]
>
> Reddy