HI,
Does Reporting support the Oracle 11g, 10g or 9i databases. if yes, then kindly provide databinding etc samples for the same.
Regards,
Sohail Kazmi
Hello Sohail,
Our current version of NetAdvantage Reporting supports the creation of datasources connecting to an Oracle Database. You can find more information about how to configure it in section "How to > How to Work with Data Sources > How to Bind a Report to an Oracle Database" of the documentation. Here is a link.
Luis
Hi Luis,
I have have successfully accomplished binding report to Oracle, it is running, but in Report Data Explorer window there is no Data Source listed, infect all the options in the same are grayed. because of this i can't make parameters etc. Hope the attached pics can help in investigation. Kindly expedite the issue, and provide guidance for the same.
Sohail Kazmi.
We have checked this and it seems to be a problem in the way the Report Data Explorer is being used.
The idea of the Report Data Explorer is that it always displays the data sources and parameters that are associated to the current report in focus. In this case, the Report Data Explorer itself is acting as the document in focus, so it doesn't see any report to get the data sources and parameters from. That's why you don't see any data, and the buttons are disabled.
In order to fix this, just move the Report Data Explorer out of the documents area and dock it, for example, in the same area where the Server Explorer or the Toolbox are. You may need to reopen the report so that the Report Data Explorer contents are refreshed.
Please let us know if this solves your problem.
Hi Sohail,
I'm attaching to this post an example showing how to implement a variable for changing the printing style. It's a very simple report, using a background and a couple of controls with text, just to show you the idea.
In order to use it, just add it to your Visual Studio project, open it and go to the "Preview" tab. The report viewer will prompt the parameter window so you can specify the rendering mode. First type "PREVIEW" in the RenderMode textbox and then click "Submit". The rendered report will look like the following:
Next you can change the parameter value to "PRINT", and click "Submit" again. Then the rendered report will look like the following:
Once it's rendered using the printing colors, just click "Print" and it will be printed like that.
When you edit this report you will notice that it has a string parameter named "RenderMode". If you look at the properties for each section, you will see that the Background property is not a color, but a bound value, like this:
=If(Parameters.RenderMode = "PRINT", "White", "DarkBlue")
This binding could be interpreted as "use White color if we are in PRINT mode, else use DarkBlue color". On the other hand, if you look at the label properties in the report, you can see that the Foreground property has the following binding:
=If(Parameters.RenderMode = "PRINT", "Black", "White")
Which means "use Black color if we are in PRINT mode, else use White color".
I hope this helps you.
Thanks for suggestion, kindly provide some sample code for the same, so that it will be really helpful to me.
As of version 2011.2 of Reporting there's no way to tell, in render time, if the system is previewing a report or printing it. But it doesn't stop you from creating your own parameter in the report to indicate this. For example, you could create a string parameter named "RenderMode", and bind the background to a conditional format. Something like:
=If(Parameters.RenderMode = "PRINT", "White", "<my color for preview>")
The foreground property should be bound similarly to the parameter, but using black for printing mode.
If you take this approach, you will need to specify the parameter as "PREVIEW" when you want to preview the report. Later on you would set it to "PRINT" and render the report again when you want to print, so it gets drawn with the printing colors.
Thanks, at-least can i print the report in white background and black foreground despite of the same will be in color at preview.
1. In order to do this, you can set the "InsertPageBreakBefore" property of the Group Header section to true. Then it will start to render each group in a new page. Alternatively, you can set the Group Footer section property "InsertPageBreakAfter" (or in the Group Body if you don't use a footer), which would have the same effect.
2. Currently we don't have a way of defining different styles at runtime or printing time.