Viewing 15 posts - 691 through 705 (of 2,278 total)
Could the scale of your graph be responsible for flattening the spikes?
February 9, 2012 at 7:12 am
Your report parameter needs to have a data type of Date/Time
February 9, 2012 at 7:11 am
Revenant (2/8/2012)
eccentricDBA (2/8/2012)
Objectivism... Shrugged
Atlas
February 9, 2012 at 7:09 am
Interesting question, and an interesting bit of reading. However
That quote comes from a section in whch the topic is encryption and encrypted data; SQL Server encryption always uses a...
February 9, 2012 at 7:08 am
Revenant (2/7/2012)
JAZZ Master (2/7/2012)
Angry BirdsHit!
Smash
February 8, 2012 at 7:13 am
I had to do a little research. I definitely learned something useful. Thanks
February 8, 2012 at 7:02 am
Cadavre (2/7/2012)
Ray K (2/7/2012)
ShippingLate
Never
February 7, 2012 at 7:24 am
If I am not mistaken RS looks at the fields in the select query to determine what fields to display. First, from your example, I don't see a dataset...
February 3, 2012 at 7:27 am
I would probably do it in the SP, yes.
February 2, 2012 at 11:30 am
If you want it to throw the error when they enter the value, then no. You could build the report dataset to do parameter validation and feedback an error...
February 2, 2012 at 7:44 am
A couple of ideas.
First you might want to try a horizontal bar chart and just let all items display. This might make your paging easier.
Another option is to add...
February 2, 2012 at 7:40 am
I am guessing but you may be running up against the character limit for your data type.
February 2, 2012 at 7:30 am
Are you using a JOIN of the original parameter data to feed your second dataset?
JOIN(Parameter.Value,", ")
Is your second dataset being fed by an inline query of stored procedure. If...
February 2, 2012 at 7:04 am
Viewing 15 posts - 691 through 705 (of 2,278 total)