Issue with Page break

Hi,

I have developed a simple report containing a table which has one group. The group has property 'Repeat Group Header '.

I can see the report when it returns data which spans more than one page. Other wise I see a blank page when seen from the web application. The report is seen properly in Designer.

I found out that if I had a 'Page Break at start' = True for the table, I can see the reports containing single page. But this page break is not acceptable.

Has anyone faced similar issue? Whats the solution to it?

Thanks,

Tanmaya

The issue was not with the report. I am using awreportviewer and it was placed in html table within <tr><td> tags.

I removed the viewer control from table & it started working fine.

IsSorted Property problem

Dear friends,

I have a ETL to import some data. When I try to open de merge join transformation, the BIDS give me an error. The error is the IsSorted must me set to true in both datasources, but I dont want to insert the sort transformation, because I know that both datasources are sorted... How can I update the IsSorted property for the both datasources? I didn't find the place to do it... it's not possible?

Thanks!

in the SOurce Components; you can right click, advanced properties; Input and output properties and set the IsSorted property of the 'OLE DB Source Output' equal to true. Additionally; you have to expand the 'output columns' node and set SortKeyPosition property for the proper columns. 0 means it is not sorted; 1 for the first column in the sort; 2 for the second one; 3 for the 3rd one....

Notice that by doing this you are just changing the metadata; the data will no be sorted. If data is not properly sorted; merge join will yield unexpected results. Also, make sure there are not tranformations in the dataflow, prior to the merge join; that alter the original sort of the data.

|||

Dear Rafael Salas

Thanks for your answer. I have some problem about "IsSorted Property". And I solve it by your guide. It is useful.

Again, Thanks for your support!

Tam Nguyen!

IsQueryStoredProcedure property won't stay set

I'm using an ExecuteSQL task to fire a stored procedure. There is a property in the editor called IsQueryStoredProcedure that is disabled. However, in the properties window there is a property call IsStoredProcedure that is enabled and can be set. Problem is that it doesn't stay set. Is this a bug?

From BOL

IsQueryStoredProcedure

Indicates whether the specified SQL statement to be run is a stored procedure. This property is read/write only if the task uses the ADO connection manager. Otherwise the property is read-only and its value is false.

|||I just went thru this...if you're using an OLE DB provider, don't worry about it. Just put the SP call as your sql statement and it will work. You don't need to set that property.