Showing posts with label developing. Show all posts
Showing posts with label developing. Show all posts

Wednesday, March 28, 2012

Report Parameter Display Problem

Hi,
I am developing several reports, I want to pass one parameter from
Report1 to Report2 and also make the same parameter selectable on
Report2. However I figured out that if I pass the parameter from
Report1 to Report2 and Report2 has the same report parameter, then the
parameter bar on the top of Report2 is not displayed. Moreover if I
click the Report2 on the report folder then the Report2 parameter bar
is displayed. How can I force Reporting Services to display the
parameter bar on the Report2?
Configuration:
Win2003 Standard Edition (Latest SP)
SQLServer 2000 (SP2)
SQLReporting Services (SP2)
Visual Studio 2003 (SP1) .Net 1.1
Alp Eren YILMAZAddition Information:
In visual studio Preview page, I can see the parameter on the parameter
bar while navigating from Report1 to Report2 but when I deploy the
reports, I could not see the parameter bar on the second report.
Alp Eren YILMAZ|||I believe there is a toggle on the right side of where the parameter
bar normally is that will display it after you jump to a report.
If you do a jump to url the parameter bar is always displayed.|||Hi Jon,
Yes actually I tried to jumping via URL and the parameters are
displayed but it's a bit hard to maintain the flow of reports because
you have to key the full URL everytime with the report names. Is there
any work around on that issue?
MS People, I found that the issue is resolved in RS2005, is there any
patch for RS2000 for that problem?
Thanks and Regards,
Jon Fife wrote:
> I believe there is a toggle on the right side of where the parameter
> bar normally is that will display it after you jump to a report.
> If you do a jump to url the parameter bar is always displayed.sql

Monday, March 12, 2012

Report Manager on 64 bit machine does not recognize 32 bit data sources

I'm a report developer who has created some reportsd against sybase data on another server. I am developing on a 64 bit Server 2003 box using SQL 2005 Reporting services. I hace created 32 bit ODBC data dsns using the supplied utitlity (odbcad32.exe). As I am creating the reports I can pull data using the data sources without a problem, however when I deploy my datasource and report to Report manager and run I get the following:

  • An error has occurred during report processing.
  • Cannot create a connection to data source 'Chicago_Reporting'.

  • ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

    This has been driving me crazy for 2 days now. Any help would be very much appreciated.

    Thanks

    Hi Rick!

    I use a 64-bit Windows Server 2003 Enterprise server also and connect to about seven different database types, although Sybase is not one of them. Have you installed SQL Server 2005 Service Pack 2?

    |||

    HI Chuck,

    Thanks for the response. I have limited experience with server admin stuff. I was brought for my reporting experience more then anything else. As far as I can tell our build number is 2005.090.3042.00 which equates to the original version of SP2 on the build list.

    Rick

  • Wednesday, March 7, 2012

    Report is using two different locales

    Can anyone help me with this?

    I am using IE ver. 6 with en-US locale, and da-DK as the locale on my developing computer.

    My problem is:

    I am translating a report parameter in one of the reports. What I would like to happen is that the parameter is translated using "en-US" like everything else in the report. But what happens is that the parameter is translated using "da-DK" and the rest of the report (when pressing view report) is translated in "en-US".

    Why are there two locales used at the same time?

    The order of the languages in the IE language settings is important. Is en-US the top-most language?`

    Also note that when using URL access to the report server, the culture for provided parameter values on the URL is determined by the rs:ParameterLanguage parameter (see also http://msdn2.microsoft.com/en-us/library/ms155064.aspx).

    For the report, you can set the Report.Language property to a specific constant culture value or based on the current user's settings: =User!Language (see also: http://msdn2.microsoft.com/en-us/library/ms156493.aspx)

    -- Robert

    Tuesday, February 21, 2012

    Report Formatting in Excel 2007

    I am currently developing a report for users who insist on exporting to Excel 2007. When I export to Excel on my PC, the report formatting is fine (I am using Excel 2003), however, font sizing as applied in the report is lost when exported to Excel 2007 (i.e. font size 9 in the report is actually 10 in excel 2007). In Excel 2007, the data which runs onto two lines does not show up correctly - the second line is squashed below the first.

    Any ideas on how I could resolve this?

    Strange, I tried on mine but did not experience this. I tried exporting to Excel 2003 and then opening it in Excel 2007 it worked perfectly fine.

    Then I also tried extracting the report from a PC which has Excel 2007 and then exporting the report in that PC, even this worked perfectly fine.