Formula to view records

Hi,
I am having a report which takes a parameter to view records based on the parameter value passed to it.

I need to check the length of the parameter, if the length of the parameter value is "4", it should compare the parameter value with one field value, if the length is more than 4, then it should compare the value with another field and shoe me the records.

I have made the formula, but it doesn't show records, where as there are records in the table.

how could i do that ? Is anybody there, who could help me in that?

Thanks in advance.

Regards

DeepakIf len(parameter)=4 then
--do some work
else
--do some other work

Do you want to do this from Front end application?

Forms Security Extension Sample

Hi,

I have installed the SSRS 2005 Forms based login security extension as per the sample and instructions that come with the product install. I have double checked my work and debugged up to the point explained here.

My user is in the database and I can get to the login page. I have traced the code and can see the user being authenticated properly by server.LogonUser, the authentication cookie being created and placed in the response object, and then the redirect url being set to the reports/pages/folder.aspx. I have employed tcptrace and can see the sqlAuthCookie set in subsequent posts.

Unfortunately the redirect to folder.aspx never happens. I keep returning to UILogon.aspx. I think their is something either wrong with the auth cookie or the web.config in the ReportServer IIS virtual directory. The relevant xml from the web.config is attached below.

I would appreciate any thoughts. I am running on W2K3 SP1. Thanks.

Mitch

<identity impersonate="false" />

<!--<authentication mode="Windows" />-->

<authentication mode="Forms">

<forms loginUrl="logon.aspx" name="sqlAuthCookie" timeout="60" path="/"></forms>

</authentication>

<authorization>

<deny users="?" />

</authorization>

Mitch, are you initially navigating to SSRS by using http://localhost or http://someMachineName?

If you hit your site with http://localhost/reports, you'll see the behavior you're mentioning above: (It's basically a side-effect of the way the code inside the Forms Auth sample is written). Try http://someMachineName/reports instead and see if you have better luck.

|||Thanks, that was it. Now I can proceed with integrating SSRS with IBM Tivoli Access manager!

forms based queries

please help i am new to sql and my old access 2000 program used forms based queries.

the user simply input the patients last name and first name and the form would open up every record that had a matching combo to edit and if the combo didnt exist the form was ready for new input.

im under the understanding that sql doesnt support forms based queries and no i would like to know how to open my access form but first prompt users for what last name and first name they are looking for then fill the recordset with just those patients.

i have upsized my access 2000. mdb file to an access project now adp.
so im not using linked tables anymore or this would not be a problem.

this is very urgent for me to fix . i have already fixed all my vb code to make my chart number automatically. now im stuck on getting a prompt for a user to enter info to fill a form.Try using a separe form that is Modal = yes. This forces them to close the form before opening the next form. Then on event Form.Close check to make sure variables (names) are set properly (not empty).

Forms Based Authentication

Sorry to revive a previously discussed point, I've been trying to get my head around the http://msdn.microsoft.com/library/?url=/library/en-us/dnsql2k/html/ufairs.asp?frame=true#ufairs_topic3 article given in a previous post. I think this is the solution we require but it raises a few issues that I would like some help on. What we are trying to do, is when the user logs on to the .net application, he is authenicated on the report server at the same time. So the user only sees one authenication process and is assigned a role from the report server to limit his/her access to reports. The user credentials at the moment are kept separate to the reportserver, i.e a different datasource and this will be modified slightly to include the report server role mappings. Access to reports is done using a slightly customised ReportViewer control included with SRS.

1. In the development environment we obviously publish different reports for differing clients. These reports are driven from differing databases and so are the user credentials for the application. Is it possible to develop a solution to encapsulate this need? I was thinking of one security extension that accepts the name of the application as a parameter and changes behaviour based on that. I'll probably use the authority parameter?

If I have completely missed the point here, please let me know!!!

Thanks in advance,

Mike.You could store the credentials required for each report in the report server.
And you could give selective permissions to the various folder/reports in the server.
Would that satisfy the requirements?

Thanks
Tudorsql

Forms authentication security

I have followed exactly what the MSDN white paper asked to implement the Form
based security. I have created the useraccount database,registered few new
users in there and then logged in the RS Report Manager and gave the browser
rights to the new users on a folder and reports which all works fine.But when
I log in with the new registered user I can log in the Report manager but the
page does not display any reports or folders!! what am I doing wrong please
help!!!Hi shabab where u got that information i.e formbased security.
can pls refer that link?
Thanks!
simmi
"shahab" wrote:
> I have followed exactly what the MSDN white paper asked to implement the Form
> based security. I have created the useraccount database,registered few new
> users in there and then logged in the RS Report Manager and gave the browser
> rights to the new users on a folder and reports which all works fine.But when
> I log in with the new registered user I can log in the Report manager but the
> page does not display any reports or folders!! what am I doing wrong please
> help!!!|||for example, Forms Authentication). Here's
a white paper that can get you started
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/ufairs.asp
also there is one very nice article extended on this white paper which is
published on devex. go to google and search for form based authentication in
MS RS...its by Harden ..let me know if you can find otherwise I will dig into
my favourites and let you know.
good luck
"simmi" wrote:
> Hi shabab where u got that information i.e formbased security.
> can pls refer that link?
> Thanks!
> simmi
> "shahab" wrote:
> > I have followed exactly what the MSDN white paper asked to implement the Form
> > based security. I have created the useraccount database,registered few new
> > users in there and then logged in the RS Report Manager and gave the browser
> > rights to the new users on a folder and reports which all works fine.But when
> > I log in with the new registered user I can log in the Report manager but the
> > page does not display any reports or folders!! what am I doing wrong please
> > help!!!

Forms authentication problems

Hi,
I'm implementing a custom security extension for Reporting Services,
based on the forms authentication sample, and am having a couple of
problems with authentication.
Here's some background on my set-up.
- We intend to expose reports to our customers over the internet.
Since we already have a main web application with a logon form and
authentication framework, we are sharing the authentication cookies
with that application (which lives on a different server), according
to the MSDN article 'Forms Authentication Across Applications'.
- I have implemented an authentication extension which uses this
framework to authenticate users, and it works. (I can call LogonUser
and get a cookie back if my credentials are valid, among other things.)
- Rather than having a separate logon form for Reporting Services, we
want to redirect users to/from our main logon form on the other server.
First problem: Report Manager isn't redirecting to the logon page that I
specified in the RSWebApplication.config file. Instead it is trying to
call the web service when not authenticated, and failing. (It gets
redirected to the logon page, and doesn't know what to do with it.)
The UFAIRS article doesn't say how RM works out whether the user has
an authentication cookie for the web service which needs forwarding.
Presumably it looks for one in the request, and redirects to the logon
page if the cookie isn't there. But how does it know what the cookie's
called? How does it even know that the web service is using forms
authentication (without first trying it)?
I don't know how what I'm doing is any different to the sample, which
does work. The only thing I've changed (in the Report Manager
configuration) is the loginUrl element within CustomAuthenticationUI,
but RM isn't even trying to redirect the client.
I'm also getting what I think is the same problem using Report Designer
in Visual Studio. When the sample was installed, Report Designer would
pop up a box asking for username and password whenever it tried to use
the web service, but now it just gives me an error message stating "a
connection could not be made to the report server". Again, I'm not sure
how it's trying to determine what it has to do to authenticate itself.
Second problem: redirection from the web service works, but it isn't
respecting the useFullyQualifiedRedirectUrl setting in web.config
(attribute of the httpRuntime element), which I've set to 'true'. The
URL it generates and puts in the query string is relative to the local
server root. Since my logon page is on a different server, I need it to
include the full URL.
Sorry for the long post, and thanks for reading if you got this far.
Please let me know any ideas you might have. I can post details from my
configuration files on request, and please ask if there's something I
haven't made clear. Thanks.
StephenThe name of the authentication cookie is configured in web.config under the
<forms> tag.
Perhaps you can make a call SOAP to LogonUser from your application before
the user gets to report manager. Then send the cookie to the client. Further
access to report server should be authenticated. For report manager to work
in this configuration you need to set the AllowPassthroughCookies - see the
SP1 readme for the exact name.
--
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Stephen Kell" <skell@.opaltelecom.co.uk> wrote in message
news:pan.2004.08.04.15.24.00.797000@.opaltelecom.co.uk...
> Hi,
> I'm implementing a custom security extension for Reporting Services,
> based on the forms authentication sample, and am having a couple of
> problems with authentication.
> Here's some background on my set-up.
> - We intend to expose reports to our customers over the internet.
> Since we already have a main web application with a logon form and
> authentication framework, we are sharing the authentication cookies
> with that application (which lives on a different server), according
> to the MSDN article 'Forms Authentication Across Applications'.
> - I have implemented an authentication extension which uses this
> framework to authenticate users, and it works. (I can call LogonUser
> and get a cookie back if my credentials are valid, among other things.)
> - Rather than having a separate logon form for Reporting Services, we
> want to redirect users to/from our main logon form on the other server.
> First problem: Report Manager isn't redirecting to the logon page that I
> specified in the RSWebApplication.config file. Instead it is trying to
> call the web service when not authenticated, and failing. (It gets
> redirected to the logon page, and doesn't know what to do with it.)
> The UFAIRS article doesn't say how RM works out whether the user has
> an authentication cookie for the web service which needs forwarding.
> Presumably it looks for one in the request, and redirects to the logon
> page if the cookie isn't there. But how does it know what the cookie's
> called? How does it even know that the web service is using forms
> authentication (without first trying it)?
> I don't know how what I'm doing is any different to the sample, which
> does work. The only thing I've changed (in the Report Manager
> configuration) is the loginUrl element within CustomAuthenticationUI,
> but RM isn't even trying to redirect the client.
> I'm also getting what I think is the same problem using Report Designer
> in Visual Studio. When the sample was installed, Report Designer would
> pop up a box asking for username and password whenever it tried to use
> the web service, but now it just gives me an error message stating "a
> connection could not be made to the report server". Again, I'm not sure
> how it's trying to determine what it has to do to authenticate itself.
> Second problem: redirection from the web service works, but it isn't
> respecting the useFullyQualifiedRedirectUrl setting in web.config
> (attribute of the httpRuntime element), which I've set to 'true'. The
> URL it generates and puts in the query string is relative to the local
> server root. Since my logon page is on a different server, I need it to
> include the full URL.
> Sorry for the long post, and thanks for reading if you got this far.
> Please let me know any ideas you might have. I can post details from my
> configuration files on request, and please ask if there's something I
> haven't made clear. Thanks.
> Stephen
>|||Firstly, thanks for the reply.
> The name of the authentication cookie is configured in web.config under the
> <forms> tag.
Maybe I misunderstood, but I thought that this was only for the web
service (i.e. in ReportServer/web.config). Report Manager is using Windows
authentication itself, and doesn't have a <forms> element in its
web.config. Let me know if this is not correct.
> Perhaps you can make a call SOAP to LogonUser from your application before
> the user gets to report manager. Then send the cookie to the client. Further
> access to report server should be authenticated. For report manager to work
> in this configuration you need to set the AllowPassthroughCookies - see the
> SP1 readme for the exact name.
Thanks -- I set the PassThroughCookies configuration as required and now I
can access Report Manager. It's still not redirecting in the case of an
unauthenticated request, which would be nice to have working, but not
essential as I can log on using our form first, which generates a valid
cookie. Unfortunately though, I still get the error I described with
Report Designer, and don't have any possibility of working around that
similarly. Please let me know if you have any ideas.
Stephen|||Report manager reads the name of the authentication cookie which is sent by
the report server as an HTTP header.
Unfortunately I don't know of any solution that would allow report designer
to work in this case. As a workaround you could write your own application
that would publish reports using SOAP calls. In the SOAP client, you can
manage your custom cookies as you wish.
--
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Stephen Kell" <skell@.opaltelecom.co.uk> wrote in message
news:pan.2004.08.05.14.48.01.766000@.opaltelecom.co.uk...
> Firstly, thanks for the reply.
> > The name of the authentication cookie is configured in web.config under
the
> > <forms> tag.
> Maybe I misunderstood, but I thought that this was only for the web
> service (i.e. in ReportServer/web.config). Report Manager is using Windows
> authentication itself, and doesn't have a <forms> element in its
> web.config. Let me know if this is not correct.
> > Perhaps you can make a call SOAP to LogonUser from your application
before
> > the user gets to report manager. Then send the cookie to the client.
Further
> > access to report server should be authenticated. For report manager to
work
> > in this configuration you need to set the AllowPassthroughCookies - see
the
> > SP1 readme for the exact name.
> Thanks -- I set the PassThroughCookies configuration as required and now I
> can access Report Manager. It's still not redirecting in the case of an
> unauthenticated request, which would be nice to have working, but not
> essential as I can log on using our form first, which generates a valid
> cookie. Unfortunately though, I still get the error I described with
> Report Designer, and don't have any possibility of working around that
> similarly. Please let me know if you have any ideas.
> Stephen
>|||Thanks. I will look into implementing a separate application to deploy
reports.
I am still a bit puzzled about how what I'm doing is substantially
different to the sample -- there's nothing special about my cookies, and
valid cookies can be generated by the RS web service as well as by our own
login page (or at least that's the idea). I'll try to investigate whether
the HTTP requests issued by RM/RD (or the responses they get) are any
different when using the sample, compared to my current installation. (Not
managed to do so yet as I don't currently have a machine with the sample
installed.)
Going back to another issue I mentioned in my first post, I don't suppose
there's any clues about why the web service doesn't generate
fully-qualified redirect URLs? I thought this was all handled by ASP.NET's
underlying FormsAuthentication implementation, but it seems like RS has
altered the normal behaviour, unless I've misunderstood something. Any
suggestions appreciated.
Stephen|||Yes, the redirect in Report manager is done only into the report manager
directory.
--
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Stephen Kell" <skell@.opaltelecom.co.uk> wrote in message
news:pan.2004.08.06.15.52.29.703000@.opaltelecom.co.uk...
> Thanks. I will look into implementing a separate application to deploy
> reports.
> I am still a bit puzzled about how what I'm doing is substantially
> different to the sample -- there's nothing special about my cookies, and
> valid cookies can be generated by the RS web service as well as by our own
> login page (or at least that's the idea). I'll try to investigate whether
> the HTTP requests issued by RM/RD (or the responses they get) are any
> different when using the sample, compared to my current installation. (Not
> managed to do so yet as I don't currently have a machine with the sample
> installed.)
> Going back to another issue I mentioned in my first post, I don't suppose
> there's any clues about why the web service doesn't generate
> fully-qualified redirect URLs? I thought this was all handled by ASP.NET's
> underlying FormsAuthentication implementation, but it seems like RS has
> altered the normal behaviour, unless I've misunderstood something. Any
> suggestions appreciated.
> Stephen
>|||(I don't know if anyone's still reading this thread, but if so, I finally
worked out the solution and thought I'd share it.)
Thanks -- it did turn out to be something to do with the redirect
destination being outside of the application's virtual directory, but not
quite what you said. (I won't claim that my explanation matches the
intended logic behind the Reporting Services code, only that it allowed me
to understand and solve the problem I was having.)
In fact, both the RS web service and Report Manager are quite happy to
redirect outside of their virtual directory. The problem is in how their
clients interpret this.
Both Report Manager and Report Designer need some way of determining
whether to call LogonUser. If the web service redirects them to a location
inside its virtual directory, they assume this is a logon page, and do
their ask-for-credentials thing. (For Report Manager it's redirecting to
the page specified in the CustomAuthenticationUI configuration element,
while for Report Designer it's popping up that dialog asking for
credentials.) Once they have the credentials, they call LogonUser to get
their cookie.
If the web service redirects them elsewhere, they don't do any of this,
and instead fall over, in the end generating generic error messages
claiming that the report server isn't working.
I got around this by configuring the web service to redirect to a simple
aspx page (called Logon.aspx, though the name doesn't matter) in its own
virtual directory. In the Page_Load event I test whether a the User-Agent
header was received. This is a bit of magic intended to determine whether
the client is interactive (i.e. a web browser) and therefore capable of
logging in using a form, or not (e.g. a web service client like Report
Designer or Report Manager).
In the case of an interactive client, the page redirects to the (external)
login page. (The URL of the login page is read from a label in the aspx
page, so you don't need to recompile in order to change it.) You must make
sure that you also include the ReturnUrl query string parameter in your
redirect destination URL, *and* that you translate it to a fully-qualified
URL (since RS doesn't seem to do this).
For non-interactive clients, it just serves a blank page (or actually,
since I was feeling helpful, a short message about why the client wasn't
redirected, followed by the aforementioned label showing the login page
URL).
Report Manager and Report Designer now work fine. You can specify the
external login page for RM just like any other.
Sorry for the long-winded explanation -- I hope it proves useful for
someone.
Stephen

Forms authentication and URL access

Ive written a security extension based on microsoft samples, i can call the
SOAP API and get authenticated but i dont know what to do so i can use this
authentication method using URL access, i need that since i want to be able
to keep the toolbar.Rodrigo,
The typical integration scenario for Forms Autnentication and web-based URL
reporting is:
1. You have a web app which authenticates the user on the server side.
2. The web app calls LogonUser SOAP API.
3. The web app utilizes the Report Viewer or another approach (static
hyperlinks, client-side javascript, etc) to submit URL-based report
requests.
So, once the user is authenticated the we app just needs to submit report
requests on the client side of the application. As long as the
authentication ticket (cookie) is passed successfully, the reports should
render fine subject to aurhorization restrictions.
Hope this helps.
----
Teo Lachev, MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
----
"Rodrigo Sánchez" <rodrigoss@.netshoreprogramming.com> wrote in message
news:%23p%23QEV5jEHA.704@.TK2MSFTNGP09.phx.gbl...
> Ive written a security extension based on microsoft samples, i can call
the
> SOAP API and get authenticated but i dont know what to do so i can use
this
> authentication method using URL access, i need that since i want to be
able
> to keep the toolbar.
>|||thanks, ill review my implementation and get back to you with more detail if
needed
"Teo Lachev" <teo.lachev@.nospam.prologika.com> escribió en el mensaje
news:%23rrIi15jEHA.592@.TK2MSFTNGP11.phx.gbl...
> Rodrigo,
> The typical integration scenario for Forms Autnentication and web-based
URL
> reporting is:
> 1. You have a web app which authenticates the user on the server side.
> 2. The web app calls LogonUser SOAP API.
> 3. The web app utilizes the Report Viewer or another approach (static
> hyperlinks, client-side javascript, etc) to submit URL-based report
> requests.
> So, once the user is authenticated the we app just needs to submit report
> requests on the client side of the application. As long as the
> authentication ticket (cookie) is passed successfully, the reports should
> render fine subject to aurhorization restrictions.
>
> --
> Hope this helps.
> ----
> Teo Lachev, MCSD, MCT
> Author: "Microsoft Reporting Services in Action"
> Publisher website: http://www.manning.com/lachev
> Buy it from Amazon.com: http://shrinkster.com/eq
> Home page and blog: http://www.prologika.com/
> ----
> "Rodrigo Sánchez" <rodrigoss@.netshoreprogramming.com> wrote in message
> news:%23p%23QEV5jEHA.704@.TK2MSFTNGP09.phx.gbl...
> > Ive written a security extension based on microsoft samples, i can call
> the
> > SOAP API and get authenticated but i dont know what to do so i can use
> this
> > authentication method using URL access, i need that since i want to be
> able
> > to keep the toolbar.
> >
> >
>|||Teo - Is it a requirement of Forms Authentication that the users who are
authenticated to the ASP.NET web app have credentials defined in reporting
services? If not, how can you manage that user's rights?
thanks
"Teo Lachev" wrote:
> Rodrigo,
> The typical integration scenario for Forms Autnentication and web-based URL
> reporting is:
> 1. You have a web app which authenticates the user on the server side.
> 2. The web app calls LogonUser SOAP API.
> 3. The web app utilizes the Report Viewer or another approach (static
> hyperlinks, client-side javascript, etc) to submit URL-based report
> requests.
> So, once the user is authenticated the we app just needs to submit report
> requests on the client side of the application. As long as the
> authentication ticket (cookie) is passed successfully, the reports should
> render fine subject to aurhorization restrictions.
>
> --
> Hope this helps.
> ----
> Teo Lachev, MCSD, MCT
> Author: "Microsoft Reporting Services in Action"
> Publisher website: http://www.manning.com/lachev
> Buy it from Amazon.com: http://shrinkster.com/eq
> Home page and blog: http://www.prologika.com/
> ----
> "Rodrigo Sánchez" <rodrigoss@.netshoreprogramming.com> wrote in message
> news:%23p%23QEV5jEHA.704@.TK2MSFTNGP09.phx.gbl...
> > Ive written a security extension based on microsoft samples, i can call
> the
> > SOAP API and get authenticated but i dont know what to do so i can use
> this
> > authentication method using URL access, i need that since i want to be
> able
> > to keep the toolbar.
> >
> >
>
>|||No credentials, just security policies in the report catalog. You would
typically use the Report Manager to set up your user security policy just
like you would normally do with Windows authentication.
Please note though that you don't have to register invividual users.
Instead, if it makes sense, you can group users into application-defined
roles outside of the Report Server. Then, in the Report Manager you will set
up security policies based the roles not users for easier maintainance.
Finally, in your CheckAccess overloads you need to take extra steps to find
out which role the user belongs to and authorize the user based on the user
role membership
Does this confuse even more :-)
---
Teo Lachev, MVP [SQL Server], MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
---
"ISGADMIN" <isgadmin@.newsgroup.nospam> wrote in message
news:9ABD45EE-390D-4272-A0AC-119114A0638E@.microsoft.com...
> Teo - Is it a requirement of Forms Authentication that the users who are
> authenticated to the ASP.NET web app have credentials defined in reporting
> services? If not, how can you manage that user's rights?
> thanks
> "Teo Lachev" wrote:
> > Rodrigo,
> >
> > The typical integration scenario for Forms Autnentication and web-based
URL
> > reporting is:
> > 1. You have a web app which authenticates the user on the server side.
> > 2. The web app calls LogonUser SOAP API.
> > 3. The web app utilizes the Report Viewer or another approach (static
> > hyperlinks, client-side javascript, etc) to submit URL-based report
> > requests.
> >
> > So, once the user is authenticated the we app just needs to submit
report
> > requests on the client side of the application. As long as the
> > authentication ticket (cookie) is passed successfully, the reports
should
> > render fine subject to aurhorization restrictions.
> >
> >
> >
> > --
> > Hope this helps.
> >
> > ----
> > Teo Lachev, MCSD, MCT
> > Author: "Microsoft Reporting Services in Action"
> > Publisher website: http://www.manning.com/lachev
> > Buy it from Amazon.com: http://shrinkster.com/eq
> > Home page and blog: http://www.prologika.com/
> > ----
> >
> > "Rodrigo Sánchez" <rodrigoss@.netshoreprogramming.com> wrote in message
> > news:%23p%23QEV5jEHA.704@.TK2MSFTNGP09.phx.gbl...
> > > Ive written a security extension based on microsoft samples, i can
call
> > the
> > > SOAP API and get authenticated but i dont know what to do so i can use
> > this
> > > authentication method using URL access, i need that since i want to be
> > able
> > > to keep the toolbar.
> > >
> > >
> >
> >
> >

Formatting subtotals in Matrix reports

I am trying to alter the color of a cell of a subtotal based on the value of the subtotal.
Example: =IIF(Subtotal.Value < 20 ,"Brown","Blue")
This doesn't work. How do I refer to the value of a subtotal inside an expression' I think it has something to do with InScope(). I have definitely clicked the little green tab and am getting the correct properties window.Please see this posting:
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=c9b1dcda-cd35-4669-bb9b-4076ad21ed43
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Getting started and liking it" <Getting started and liking
it@.discussions.microsoft.com> wrote in message
news:5BC824BC-61A2-44A8-BA0B-FD0163954F8E@.microsoft.com...
> I am trying to alter the color of a cell of a subtotal based on the value
of the subtotal.
> Example: =IIF(Subtotal.Value < 20 ,"Brown","Blue")
> This doesn't work. How do I refer to the value of a subtotal inside an
expression' I think it has something to do with InScope(). I have
definitely clicked the little green tab and am getting the correct
properties window.

Formating Date Display

How to I set the =User!Language on a Reporting Services report to display
based on the locale of the user. I'd like to make sure date fields are
displayed using the correct format.On Nov 19, 1:48 am, Greg Larsen <gregalar...@.removeit.msn.com> wrote:
> How to I set the =User!Language on a Reporting Services report to display
> based on the locale of the user. I'd like to make sure date fields are
> displayed using the correct format.
I found an example online that shows it should be something like:
lblTime.Text = String.Format("{0:T}", rightNow);
lblDate.Text = String.Format("{0:d}", rightNow);
-- Scott