Setting where calculated members in an OLAP cube should be processed

This post says:
"Because, for example, if your query return less then 1000 members by dimension in your query, all the data is retrieve to the client and the calculated members are calculated on the client side."

So actually the calculated members are by default calculated by the client. This explains why so much CPU is used on the client when there are a lot of calculated members.

To set the location for calculating the members to the server, you can use this parameter in the query string:
Execution Location=3

AutoAccept Sink for Exchange

The AutoAccept Sink for Exchange is a tool for Exchange 2000 that allows resource mailboxes to automatically accept/decline meeting requests based on a combination of factors. These factors include the free/busy status of the resource, whether the requestor is authorized, and many other configurable settings.

Using the Visual Studio .NET 2003 Debugger with ASP.NET Applications

A very annoing part of VS is debugging. Debugging always hangs after some steps... The article answers some of the questions around debugging. Except my solution still hangs after 3-5 steps...