Showing posts with label designer. Show all posts
Showing posts with label designer. Show all posts

Monday, March 19, 2012

"Select All" option visible in Designer but gone on Report Manager

Hello,

I have several reports that use parameters that I have defined as multi-value. When I am designing the reports I see the "(Select All)" option listed first in each parm control that has the multi-value property set true. However, when the same reports are deployed to our server and viewed through Report Manager, the "(Select All)" option is missing. I need the "(Select All)" to be present.

I've seen some discussion of a service pack. Could this be the problem? What do we need to do to get our "(Select All)" back?

Thanks,

BCB

Hello BCB,

You'll need to apply SP2 to the server with Reporting Services on it. It seems that your local machine already has it applied.

Jarret

|||

Hello Jarret,

Thanks for your response. Can you tell me how to identify the service packs that have been applied to our SQL Server, if any? I checked the SQL Server properties and found a Version property that reads 9.00.2047.00. However, the number doesn't mean anything to me.

How can I tell if SP2 has been applied?

Thanks,

BCB

|||

BCB,

RTM - 2005.90.1399
SP1 - 2005.90.2047
SP2 - 2005.90.3042

This link will tell you which version number corresponds to which service pack:

http://support.microsoft.com/default.aspx/kb/321185

You can also go to the properties of the EXE file to get the version number. For example:

{Drive}:\Program Files\Microsoft SQL Server\MSSQL.{InstanceID_of_RS}\Reporting Services\ReportServer\bin\ReportingServicesService.exe

Jarret

|||

I have the same scenarios (but it's not a problem)

I applied SP2 (AND SP2a) on my local client, so my VS2005 has <Select All> in the Designer, and local Preview

however, our SSRS servers haven't been applied SP2 but only SP1, so no <Select All> there

My local .exe version is 3050 (ie. anything > 3042 is SP2) since SP2a is .3050 :)

|||Thanks to all for the very helpful responses...

Tuesday, March 6, 2012

"dangerous MSI" Microsoft SQL Server 2000 DTS Designer Components

Microsoft SQL Server 2000 DTS Designer Components has cause a total destruction of my Enterprise Manager.

In my workstation I've got Sql Server 2000 client and Sql Server 2005 client. Everything goes fine up to here.

But when I've installed that MSI I have not been able to open my Enterprise Manager.

From MMC appears: Error initializing component CLSID: {xxx.xxx}

My goal was be able to open 2000 stuff from Sql Management Studio. By the moment, I'm forget of that.

Does anyone have ever faced this issue?

QA is working.

Thanks in advance for any suggestion

is this an issue? I'm not worried about -I have multiple TS-. But I don't know if it's strongly related with my own workstation settings or is some more general.

My idea was to allow anyone use Sql Management Studio for Sql25k stuff and Sql2k stuff to the full (it included dts 2000) and so and cutting out time.

|||hey guys any ideas?|||

I know, such a pain, day in day out but I can't believe that anyone has ever experimented...

|||Install sp4 on the client. That fixed the problem for me.|||SP4 for Sql Server 2000, you mean?|||First, if you had 2000 client tools and 2005 client tools installed you did not need to install the "DTS designer tools". First thing to do is uninstall it. You only need to install that package if you DON'T have 2000 client tools.

Then, figure out why you are getting the error "You need DTS Designer Tools" when you try to open DTS in 2005.

I found I had SQL 7, 2000 and 2005 client tools installed. If I uninstalled the 7 client tools, the DTS started working.

Also, make sure you have SP4 of 2000 installed on your machine.

Saturday, February 11, 2012

#error on table in rpt designer

Hi, I'm probably missing something really simply here, but can't see it. I
have a table that I'm tring to compute the following expression in rpt
designer.
=IIf(Sum(Fields!cancels.Value) >=1,
Sum(Fields!enrollments.Value)/Sum(Fields!cancels.Value),0)
it works when (Fields!cancels.Value) is >=1 but
when (Fields!cancels.Value) is not >=1 then it gives me a blank instead of
the 0.
when it rolls up to the group it gives me the #error
Any suggestions. Thanks, LisaLisa,
The problem is that SRS evaluates the entire expression. Even though
your syntax is correct, SRS still does the calculation and returns a
divide by zero error.
To avoid this, I suggest creating a custom code function to use instead
of doing the calculation in the expression. What I use is this:
Public Function DivideBy(ByVal exp1, ByVal exp2)
If exp2 = 0 Then
DivideBy = 0
Else
DivideBy = exp1 / exp2
End If
End Function
Your expression would then be:
=code.DivideBy(Sum(Fields!enrollments.Value),Sum(Fields!cancels.Value))
toolman|||thanks, got it
"toolman" wrote:
> Lisa,
> The problem is that SRS evaluates the entire expression. Even though
> your syntax is correct, SRS still does the calculation and returns a
> divide by zero error.
> To avoid this, I suggest creating a custom code function to use instead
> of doing the calculation in the expression. What I use is this:
> Public Function DivideBy(ByVal exp1, ByVal exp2)
> If exp2 = 0 Then
> DivideBy = 0
> Else
> DivideBy = exp1 / exp2
> End If
> End Function
> Your expression would then be:
> =code.DivideBy(Sum(Fields!enrollments.Value),Sum(Fields!cancels.Value))
> toolman
>|||Glad I could help