Page break and subreport

Hello,
Using SSRS 2005, SP1.
I've got a report which contains a subreport.
This subreport is based on a list and can display one or more records.
When i put the subreport in its parent report, i give it an height
which is equal to the height necessary for displaying one record.
When i run my report, if the subreport display one record, there's no
problem.
But if my subreport display more than one record, and then needs to
extend its height, the report works properly but i've got a blank page
after.
As i can't know how much records my subreport has to display, i don't
see how to resolve this problem of blank page.
Is there anyone who've got idea?
Thanks in advance.
Jerome
I hope my english is enough efficient to explain my problem!Jerome,
You're not alone! I am also having this problem, but I'm getting 2
blank pages after my subreport. I ran the subreport by itself and get
no blank pages. I also ran the parent report by itself and get no
blank pages. I only get the blank pages after the subreport when I put
the subreport inside the parent report.
I hope you get feedback because I need it too!!
jennifer
Jerome FAURE wrote:
> Hello,
> Using SSRS 2005, SP1.
> I've got a report which contains a subreport.
> This subreport is based on a list and can display one or more records.
> When i put the subreport in its parent report, i give it an height
> which is equal to the height necessary for displaying one record.
> When i run my report, if the subreport display one record, there's no
> problem.
> But if my subreport display more than one record, and then needs to
> extend its height, the report works properly but i've got a blank page
> after.
> As i can't know how much records my subreport has to display, i don't
> see how to resolve this problem of blank page.
> Is there anyone who've got idea?
> Thanks in advance.
> Jerome
> I hope my english is enough efficient to explain my problem!

Package hanging on OLE DB Command with large result sets

I have an SSIS package (SQL 2005 SP2 and Visual Studio SP1) that does the following:

OLE DB Source --> Conditional Split --> OLE DB Command #1 --> OLE DB Command #2

The source reads from database A. Each row is variable-width and up to several KB wide, including two ntext columns.

Command #1 executes a stored proc in db A, using a bunch of inputs and two output parameters.

Cmd #2 executes an update in db B, using the two output params from cmd #1 as inputs.

When the rowset size is small, around 500, everything works fine.

However, when the rowset size is larger, around 5000, SSIS hangs when trying to execute cmd #2. The profiler shows that none of the cmd #2 updates are ever executed. No error messages are produced, and the connection never times out -- it just hangs forever.

If I replace the cmd #2 updates with a simple select, everything works fine. If I replace it with a stored proc that does an update, it hangs.

The work-around I came up with was to create a new table in db B, and do inserts into the table, but unless I'm missing something, this still seems like a bug...

Do you have the RetainSameConnection property set to true on the OLE DB connection manager you are using? Try that if not.