"Paco" <Paco@discussions.microsoft.com> wrote in message
news:BBB0A48A-8A1B-47B6-B0DB-FA2410D3E8EB@microsoft.com...
> I made my Barchart and it is working OK. There is however a difference in

> If I use the values, the barcharts are connected to each other and

> I looked at the pointwidth, but the value is 0 and if I change it then it

>
>
>
> "Robert Bruckner [MSFT]" wrote:
>
> > If you use SP1, you have control over the datapoint colors.
> >
> > Assuming you have a category grouping like =Fields!WorkHour.Value and no
> > dynamic series grouping, you can write an expression for the datapoint
color
> > ()
> > =Choose(CInt(Fields!WorkHour.Value), "Green", "Blue", "Yellow", .......)
> >
> > MSDN docs for Choose:
> > http://msdn.microsoft.com/library/en-us/vblr7/html/vafctchoose.asp
> >
> > Alternatively, you can calculate some RGB values based on the WorkHour
> > value. Note: color expressions have to evaluate to strings, therefore
you
> > have to convert the RGB value into a string like this:
> > =String.Format("#{0:x6}", RGB(CInt(Fields!WorkHour.Value) * 5, 1, 96))
> >
> > MSDN docs for RGB:
> >
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vblr7/html/vafctrgb.asp
> >
> > Note: if you use a dynamic series grouping in the chart, you have to use
an
> > aggregate function using the name of the dynamic series grouping as
scope
> > when refering to WorkHour. Examples:
> > =Choose(CInt(First(Fields!WorkHour.Value, "SeriesGroupName")), "Green",
> > "Blue", "Yellow", .......)
> > =String.Format("#{0:x6}", RGB(CInt(First(Fields!WorkHour.Value,
> > "SeriesGroupName")) * 5, 1, 96))
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "Paco" <Paco@discussions.microsoft.com> wrote in message
> > news:2A34BE66-ECF2-48A8-802D-49AD08D70598@microsoft.com...
> > > I succeeded with the stored procedure. I also had to make a "user
definded
> > function" and it is all working fine now.
> > >
> > > There is one problem. Before I had the hour bars in two different
colors
> > (green, red), the first bar was green and the second red etc. In this
way
> > you can see them better.
> > > They way I made it now they can have only one color (also a gradient).
Is
> > it possible to give the bars different colors like e.g the first bar is
> > green and the second is red etc? The bars are then better to be
> > differentiated. Also if it is printed (black & white) you can see the
bars
> > better by having different colors (green, red = light, dark).
> > >
> > > I hope someone can help me with this one.
> > >
> > > "Robert Bruckner [MSFT]" wrote:
> > >
> > > > If you use "static categories", then as I mentioned in my first
posting,
> > you
> > > > can no longer modify the report in the report designer because it
does
> > _not_
> > > > support it - only the server supports it right now. If you load it
in
> > report
> > > > designer and modify any property it will destroy the original
changes.
> > Just
> > > > upload the modified RDL on the server and it will work.
> > > > Also, as indicated in the other post, you will need 24 static
categories
> > and
> > > > therefore have 24 datapoints (1 datapoint per static category). The
only
> > > > thing you gained by approach (1) is to have control over the X-axis.
> > > >
> > > > If you just want to have 1 datapoint expression, then you have to
use
> > > > approach (2). As described earlier, you will need to write a stored
> > > > procedure and change the structure of the dataset. Then you will
then
> > just
> > > > have 1 datapoint defined with =Count(Fields!EmployeeID.Value) and 1
> > dynamic
> > > > category grouping =Fields!WorkHour.Value, which will automatically
group
> > the
> > > > data per workhour.
> > > >
> > > > --
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > >
> > > >
> > > > "Paco" <Paco@discussions.microsoft.com> wrote in message
> > > > news:1B5E8C2D-FCFE-41F8-AC0E-EBEE4FE2DAB9@microsoft.com...
> > > > > I changed the code as you described and it is working fine.
However,
> > the
> > > > expression has to be in every dataopint in the RDL file. I tried to
> > change
> > > > and test what happens if I change the code going to "Chart
> > > > properties/data/values/".
> > > > > There is only the first expression and if I change it the whole
chart
> > does
> > > > not work anymore. It seems to me I can not do anything in that
section
> > > > because the chart will not work. If I could make some changes I
would
> > trie
> > > > to use a code with a loop to get the 24 "hour bars".
> > > > >
> > > > > How can I use the expression one time? Is it e.g. possible to make
a
> > > > function, in the code window or an assembly, with a loop so the code
is
> > > > written 24 times to the RDL file by calling that function in the RDL
> > file?
> > > > This way I only have to make changes in the function. Or is there an
> > other
> > > > possiblity?
> > > > >
> > > > > "Robert Bruckner [MSFT]" wrote:
> > > > >
> > > > > > The CategoryGroupings section of the RDL file seems correct.
> > > > > > However, you also need to change the structure of the ChartData
> > section.
> > > > > > Rather than 1 Datapoint per ChartSeries element and 24
ChartSeries
> > > > elements
> > > > > > in the entire file (i.e. 24 static series), you need to have

"Robert Bruckner [MSFT]" wrote:

> "Values" represent static chart series. Every chart series is independent
> (and has its own legend entry, its own default color etc.).
> A (dynamic) category group will group the datapoints within one series.
> Therefore, category groups share the same default color and many other
> settings within the same chart series.
>
> The Dundas chart control will automatically leave space between different
> category groups - especially when you have category groups and multiple
> chart series.
> I'm not sure why the PointWidth property did not give the expected results.
> Which values did you try? By default the internal PointWidth setting is 55,
> unless explicitly set in the RDL file. You might want to try values close to
> 100. Note: the effect of the PointWidth setting is unfortunately not visible
> in the chart layout mode, only in preview and server.
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "Paco" <Paco@discussions.microsoft.com> wrote in message
> news:BBB0A48A-8A1B-47B6-B0DB-FA2410D3E8EB@microsoft.com...
> > I made my Barchart and it is working OK. There is however a difference in
> display when having different values that makes up the barchart and a
> barchart that is made up by a Category Group.
> > If I use the values, the barcharts are connected to each other and
> therefore they are thicker and better displayed compared to a barchart made
> up by a Category group. The bars made up by a Category group have a space
> between each other of appr. 30% of the bar width.
> > I looked at the pointwidth, but the value is 0 and if I change it then it
> gets only worse. I am using a barchart that displays 24 hours and every hour
> has 4 bars. The bars are already very small so I like to get rid of the
> spaces in between and make the bars wider. Are there possiblities to do
> this?
> >
> >
> >
> > "Robert Bruckner [MSFT]" wrote:
> >
> > > If you use SP1, you have control over the datapoint colors.
> > >
> > > Assuming you have a category grouping like =Fields!WorkHour.Value and no
> > > dynamic series grouping, you can write an expression for the datapoint
> color
> > > ()
> > > =Choose(CInt(Fields!WorkHour.Value), "Green", "Blue", "Yellow", .......)
> > >
> > > MSDN docs for Choose:
> > > http://msdn.microsoft.com/library/en-us/vblr7/html/vafctchoose.asp
> > >
> > > Alternatively, you can calculate some RGB values based on the WorkHour
> > > value. Note: color expressions have to evaluate to strings, therefore
> you
> > > have to convert the RGB value into a string like this:
> > > =String.Format("#{0:x6}", RGB(CInt(Fields!WorkHour.Value) * 5, 1, 96))
> > >
> > > MSDN docs for RGB:
> > >
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vblr7/html/vafctrgb.asp
> > >
> > > Note: if you use a dynamic series grouping in the chart, you have to use
> an
> > > aggregate function using the name of the dynamic series grouping as
> scope
> > > when refering to WorkHour. Examples:
> > > =Choose(CInt(First(Fields!WorkHour.Value, "SeriesGroupName")), "Green",
> > > "Blue", "Yellow", .......)
> > > =String.Format("#{0:x6}", RGB(CInt(First(Fields!WorkHour.Value,
> > > "SeriesGroupName")) * 5, 1, 96))
> > >
> > > --
> > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > >
> > >
> > > "Paco" <Paco@discussions.microsoft.com> wrote in message
> > > news:2A34BE66-ECF2-48A8-802D-49AD08D70598@microsoft.com...
> > > > I succeeded with the stored procedure. I also had to make a "user
> definded
> > > function" and it is all working fine now.
> > > >
> > > > There is one problem. Before I had the hour bars in two different
> colors
> > > (green, red), the first bar was green and the second red etc. In this
> way
> > > you can see them better.
> > > > They way I made it now they can have only one color (also a gradient).
> Is
> > > it possible to give the bars different colors like e.g the first bar is
> > > green and the second is red etc? The bars are then better to be
> > > differentiated. Also if it is printed (black & white) you can see the
> bars
> > > better by having different colors (green, red = light, dark).
> > > >
> > > > I hope someone can help me with this one.
> > > >
> > > > "Robert Bruckner [MSFT]" wrote:
> > > >
> > > > > If you use "static categories", then as I mentioned in my first
> posting,
> > > you
> > > > > can no longer modify the report in the report designer because it
> does
> > > _not_
> > > > > support it - only the server supports it right now. If you load it
> in
> > > report
> > > > > designer and modify any property it will destroy the original
> changes.
> > > Just
> > > > > upload the modified RDL on the server and it will work.
> > > > > Also, as indicated in the other post, you will need 24 static
> categories
> > > and
> > > > > therefore have 24 datapoints (1 datapoint per static category). The
> only
> > > > > thing you gained by approach (1) is to have control over the X-axis.
> > > > >
> > > > > If you just want to have 1 datapoint expression, then you have to
> use
> > > > > approach (2). As described earlier, you will need to write a stored
> > > > > procedure and change the structure of the dataset. Then you will
> then
> > > just
> > > > > have 1 datapoint defined with =Count(Fields!EmployeeID.Value) and 1
> > > dynamic
> > > > > category grouping =Fields!WorkHour.Value, which will automatically
> group
> > > the
> > > > > data per workhour.
> > > > >
> > > > > --
> > > > > This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > > > >
> > > > >
> > > > > "Paco" <Paco@discussions.microsoft.com> wrote in message
> > > > > news:1B5E8C2D-FCFE-41F8-AC0E-EBEE4FE2DAB9@microsoft.com...
> > > > > > I changed the code as you described and it is working fine.
> However,
> > > the
> > > > > expression has to be in every dataopint in the RDL file. I tried to
> > > change
> > > > > and test what happens if I change the code going to "Chart
> > > > > properties/data/values/".
> > > > > > There is only the first expression and if I change it the whole
> chart
> > > does
> > > > > not work anymore. It seems to me I can not do anything in that
> section
> > > > > because the chart will not work. If I could make some changes I
> would
> > > trie
> > > > > to use a code with a loop to get the 24 "hour bars".
> > > > > >
> > > > > > How can I use the expression one time? Is it e.g. possible to make
> a
> > > > > function, in the code window or an assembly, with a loop so the code
> is
> > > > > written 24 times to the RDL file by calling that function in the RDL
> > > file?