Report Definition Language

Using VS 2005, I have created a piece of software that creates an RDL file using XML. However, although my data (though a DataView control) is showing as it should, and I can update this to create new data, I cannot get the RDL to display a variable which I change and use as a 'header text' to the report. The variable is shown the first time I display the RDL through a ReportViewer Control but remains static thereafter. The interesting thing is that when I view the XML through a third-party viewer, it shows the correct value stored in the variable.

For information, I am using a child form in a MDI to create the data that is fed into another child form that contains the ReportViewer. The MDI has been programmed so that the child forms are not closed and disposed of, but are hidden from view.

Has anyone any initial ideas of what I could do to flush or clear the RDL or any other relevant object?

Are you viewing the RDL in the report designer when this happens? Report Designer has a functionality to cache the data in preview (http://msdn2.microsoft.com/en-us/library/ms157366.aspx). You should be able to click on the refresh button to get new data.

Report Definition in Crystal

Hi, everyone -
I just had a quick query that I was hoping one of the experts out there could help me with:

I remember, when we used WinQL as our previous report generator, the software provided a "report definition" print option. This would allow me to print off a page with the fields, formulas, groupings, etc. for reports so that I could recreate my report in what we now have -- Crystal 8.5.

Now that we are changing our housing program software from a DOS-based system to a Windows-based software, the vendor is telling me that I'll have to AGAIN :eek: recreate my Crystal reports because the fields will all be different.

I'm wondering whether Crystal provides the same sort of "report definition" print option so I can print off the reports I need to recreate without having to guess at the formulas..... I've looked around Crystal and wasn't able to locate anything like this.

Thanks for the help.I'm not sure about 8.5 but in developer 10 under exports there is an option to print the report definitions.

GJ|||Hi, GJ -

UUUGGG... :blush: :blush: :blush: I guess I didn't scroll down far enough under Export. I did find it though.

Thanks for the help!!!sql

Report Definition

Is it possible to control the number of table rows that can be displayed by modifying the report definition?Not sure if this is what you mean, but you can control the # of rows displayed by limiting the # of rows fetched from the data source. There's no way AFAIK to fetch N rows but only display N-M rows.|||

>> There's no way AFAIK to fetch N rows but only display N-M rows.

Yes, actually there is <s>.

You do need to give yourself appropriate information from the data source, but this doesn't necessarily mean limiting the rows! (because you might have another data region that shows a different count, in the same report, from the same data).

Here's a reporting query from my favorite ASP.NET add-on table (ELMAH error handler):

Code Snippet

SELECT ErrorId, Application, Host, Type, Source, Message,
[User], StatusCode, TimeUtc,

Sequence, AllXml

FROM ELMAH_Error ORDER BY ErrorId

... now suppose we add a column, as follows:

Code Snippet

SELECT ErrorId, Application, Host, Type, Source, Message,

[User], StatusCode, TimeUtc,

Sequence, AllXml, Row_Number() OVER (ORDER BY ErrorID) AS ItemID
FROM ELMAH_Error ORDER BY ErrorId

(you can add a counter like this different ways in other data sources)

... Now we can add the following filter to a table (or whatever):

Code Snippet

=Fields!ItemID.Value <= 8 ' or whatever maximum you have in mind,

' for example you can say:

=Fields!ItemID.Value <= =Parameters!MyMax.Value

... and readers please note, if you have trouble when you follow these instructions:

When I built this example I had to CInt() (cast) on both sides of the filter expression (including the literal 8!) to get it to work the first couple of times. It may be because I was building the query interactively for the dataset, and the designer doesn't support this clause so, while it processes the SQL, it is not sure about the data type of the result. IAC it does work.

>L<

|||Thanks for your help.