I have a number of ATLAS and other ASP.NET AJAX samples up here:

http://www.west-wind.com/presentations/scriptcallbacks/sample/default.aspx

They're a little dated, as I've updated them since, but the base functionality is all in place...

+++ Rick ---

>Rick,
>
>Thanks. I have two grids, each in their own UpdatePanel and it is running the queries behind both grid anytime anything happens anywhere on the page. Could you be persuaded to give a bit of sample code that demonstrates what you are talking about with the low-level Web Service stuff?
>
>I'm working on a portal front-end for a data-warehouse. So the queries will process LOTS of data, but return only small summaries of it. The data does not change throughout the day. Based on that, I thought it made more sense to query the data once. Then, if the user just wanted to resort the view of the data they saw, I could just resort that data instead of requerying from the source again.
>
>Based on this type of application, would you still disagree with this approach?
>
>TIA,
>Chad
>
>>Chad,
>>
>>ATLAS isn't all about UpdatePanel although most people will go there first. UpdatePanel is configurable to determine when it updates with its Mode property. However, there's what I consider a design flaw in that any event inside of an update panel will cause that panel to be updated whether it needs to or not. Microsoft is still looking into that scenario as far as I know.
>>
>>You can do much more low level work with ATLAS if you choose. The Web Service functionality in particular is great for doing raw data access and updating page content - I tend to use that more than anything else in ATLAS but it's a little more work, but it also gives you full control over the processing on both the client and the server.
>>
>>+++ Rick ---