With ADOMD.Net, making the most minor changes to cubes results in applications throwing the above exception, with the message "The Cubes collection has been updated on the server". Users then need to restart their applications. In most cases there should not be any need for this, as the sorts of changes we are likely to make (such as adding member properties to dimensions) don't really change the cube metadata significantly. Certainly not to the extent that user queries would be affected. Is there any way to prevent this behaviour, or work around it? Putting try/catch blocks in every place where cube metatadata is queried in order to catch this exception and reopen the connection would be overkill. Thanks, Peter
