Dynamic change of the column size and location of a matrix

I have a report that has a matrix. That matrix can have from 2 to 16 columns dependinging on the dataset result. Right now I am forced to place this matrix on the left side of the report and make a column layout pretty narrow. When dataset has more than 13 or so columns it looks OK, but when dataset has only two or three columns it looks weird with a matrix sitting in the left corner with two or three narrow columns and a lot of empty space to the right.

Is it possible programmatically change the width of the columns depending on their number in the dataset?

Is it possible to move the location of the matrix (horizontally) depending on the number of columns in the dataset?

Thank you,

Simon.

Is it possible programmatically change the width of the columns depending on their number in the dataset?

No

Is it possible to move the location of the matrix (horizontally) depending on the number of columns in the dataset?

No

Curently, the RS object model doesn't support manupaluting the report definition at runtime. Please take a moment to put these on the wish list for a future release on connect.microsoft.com

|||Is the feature available yet or is it still a no go. I really need to be able to change the width of columns and the height of textboxes dynamically. Has anyone been able to acomplish this?
|||

No go, as far as I know.

:-(

|||

The only way to do this that I know of is to re-write the RDL dynamically at run time with the specifications that you need for this run. Does this help at all? There are probably only a couple of changes that you would need to make in your case.

>L<

|||Yeah that's what I have done. When the user selects the report from my web app, I load the rdl file, make the necessary changes to the xml, re-deploy the report and then generate it. A bit of a pain but unfortunately the only work around at the moment.
|||

Hi Mark,

One can imagine that something similar would be necessary if dynamic width were built into the product.

Unfortunately it would pretty much take the same work *and* -- this is the kicker that may have taken it off the Katmai table for all we know -- it might be very difficult to get it right for every type of scenario that people might want to use it in.

I think it would be a great idea for Katmai or some future version to provide a hook that allowed a "swap event" during the report rendering process (there's a reason I call it that, although I know it sounds odd <s>).

The basic idea here is that the kinds of work we need to do at this point in the process would still be up to us, the product wouldn't do the work of adjusting the RDL, but it would offer a safe and consistent point at which to do that work. It would maybe hand the RDL as a stream or a loaded DOM object, we could make whatever adjustments we wanted, and then it would continue on its way.

Would you agree that this would provide some benefit, or do you see it as not sufficiently "automagical"?

>L<

|||I think that any improvement in this area would be beneficial however I would prefer for the process to be a bit more "automagical" as you put it.