>>When you say cached, what do you mean? How is that done?<

We do this for certain DataSets that don't change often and are used, among other things, for populating combos. We grab the data in the usual way at application start-up (through a Web Service), then we store an XML version of those DataSets locally on the workstation. If the codes haven't changed since the last time the app was started, then we don't even bother hitting the back-end to get the data, we just instantiate the DataSets and fill them with the XML that already exists locally. In addition to that, these DataSets have static methods in them so that they can be used everywhere in the app without filling the DataSet up each time we need it for combos.

Does that answer your question?

~~Bonnie

>
>
>
>>Yep, ok ... we do a similar thing (caching static datasets for combos/dropdowns). But, all the data is retrieved and cached at program startup ... and it still goes through a Web Service to get it. The UI still never accesses the data access layer directly, just the static datasets.
>>
>>~~Bonnie
>>
>>
>>>I use a helper class that deals with all the picklists. Afterwards, this static data is cached for future use. I use this approach for speed considerations, since i dont want to go thru n layers to get some static data.
>>>
>>>Vlad