Cache. Viewstate. Session.
I am not going to recommend one over the others without knowing more about
your application. You might also find that it is more efficient to simply
query from the persisted store each time.
If the built in .NET items are not working for you, there are other cache
solutions out there, like nCache from
www.alachisoft.com. Not recommending
that particular product, but it is one possiblity.
--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
*************************************************
| Think outside the box!
|
*************************************************
"Chris" <(E-Mail Removed)> wrote in message
news:9de82f65-0a1f-48b8-8103-(E-Mail Removed)...
Makes sense now. Good ol' hindsight. So what other options do I have
if I want to put this query in a dataset, but retain the information
in the dataset after postbacks?
On Mar 12, 10:09 am, "Mark Rae [MVP]" <m...@markNOSPAMrae.net> wrote:
> "Chris" <coz1...@gmail.com> wrote in message
>
> news:d3e20a20-0a61-4dee-89d6-(E-Mail Removed)...
>
> > Yep, you're correct.
>
> > I'm doing a 'Public Shared blahblah as new DataSet', inside the class.
>
> And that's the problem... Shared variables (static in C#) are shared
> across
> the entire application in ASP.NET...
>
> --
> Mark Rae
> ASP.NET MVPhttp://www.markrae.net