calendar picker?

  • Hi there

    I am trying to set up some sort of date picker for my reports in Reporting Services and found an article which basically uses an asp.net calendar control as a plug-in to the report (see link below).

    http://groups-beta.google.com/group/microsoft.public.sqlserver.reportingsvcs/browse_thread/thread/6e8cee511769b6c/1ddce2c2c6523fc0?q=&_done=/groups?enc_author=uFKGehIAAAAdZvNtw6tRAoeBJxgAOEvh8rhlH0Pnl47z4AZhN98BFg&&_doneTitle=Back%20to%20Search&d=&

    Unfortunately I am not very experienced in programming, so i don't fully understand how you would integrate the asp page with the report.

    My reports are based on an Analysis Services cube time dimension. i have an MDX statement in the Data query window in .NET which populates a Matrix table. The query looks like this:

    SELECT { Measures.members } on Columns ,

    NON EMPTY {{[Business].[User].[Business Entity Id].[891].Children}

     *  {[Time].[2004].[Quarter 1].[1].[January]:[Time].[2005].[Quarter 1].[1].[January]}} on Rows

    FROM UsageStats_Phase1

    I then deploy the report to the Reporting Server manually. How would I integrate an asp calendar control into this set up? Any help would be most appreciated!!!

    Thanks and regards

    Maria

  • Hmmm ... been ages since I worked with MDX, and I haven't used MDX in Reporting Services, but shouldn't you have something in the statement that acts as the parameter?

    For handling the parameters, with things like popup calendars, etc... the easiest way is to use the ReportViewer control that is included in the samples.

    Basically you have a web page that can have various controls for parameter entry along with the ReportViewer control.

    You then render the reports in the ReportViewer by setting appropriate properties when the user clicks the submit button.

     

    --------------------
    Colt 45 - the original point and click interface

  • We are trying to do the same thing.

    We tried the Hitchikers guide to Reporting services book example using a behaviour file - this works but it is a hack, isn't it?

    But we actually agree that the best approach is to create a standard ASP.Net page that has reference to the RS web service, use that page to collect user entered parameters, use the Report viewer control to render the report - it is in the samples directory of your reporting services installation. Use ASP.Net authentication too?

    There are plenty of Googleable code samples for connecting to the RS web service - including in BOL.

    I would recomend the Lavchev, Vaughn and Larson Reporting services books highly too - they are complimentery.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply