Small enhancement:

Since this'll be used in multiple places and could easily need changes or updates in the future, add some custom code to the report. (Report/ReportPropertyies..., Code tab).

Then call this...

Mary,

What do you mean by "doesn't work". How are you testing it? (What software?)

Post the code for your action and I'll take a look. It'll be easier if you pull...

A couple of points:

First, you must make sure you've entered the values in the matrix on the group lines. Look for the cells with a green triangle on the top...

It would seem to me that you mkust change:

AND (dbo.Positions.Period = 200803)

to

AND (dbo.Positions.Period between 200704 and 200803)

To "calculate" the...

Which version of Excel and MSAS are you using?

For 2003, Data, Import External Data, New Database Query.

3rd tab (OLAP Cubes).

Create a data source (use the 9.0 driver for MSAS 2005).

Follow...

I guess I'll have to post the dissenting opinion. While I agree that any system of solution can be made overly complex and difficult to deal with if you incorporate...

Wait a minute. What was flagging this error? Was it MSAS or SQL Server. If it was SQL Server (while building a cube) then try this:

Change the number of connections...

Sounds like there's something dramitically wrong with your cube definitions. Without some more information, it's impossible to say. At this size, you should be able to pull in and process...

True, but I believe you need InfoPath Forms Services installed on your Web Server.

Check how the cascades / defaults are set up for the parameter on the report. It's easy to miss a little thing.

Infopath doesn't require Sharepoint, although it's a convenient platform to deploy the forms. You can easily deploy them to a share on the LAN, in particular if you're updating a...

No, but it was some time ago and I had full access to the box. I've ignored it since then.

That's normal operation. I believe it's related to the cache operations in MSAS. There's no virus involved here.

I think you can safely delete them if you really want to (I...

Ok, I'd need more information.

Check the SQL Statement (during the process) that is generating the error. Copy / paste it into Management Studio, execute it there and debug your issue.

Don't...

Try this (I think):

Catch the exception in your data pull, so that when it occurs you don't retrieve any rows at all. Then, on your output table, change the "NoRows"...