Exporting PDF - Adding empty page

Hi,

I created a report using dynamic display( I hide the column using the expression in Property->Visibility).By using expression the column which is having null is hided.When I try to export the report to PDF,the empty pages are displaying along with data.Ie.,The report contyains only 5 pages but in PDF it is displaying 10 pages(5pages data with 5 empty pages).

Any Suggestions appreciated!

Thanks

Please verify that the definition width of your table (regardless of any hidden columns) is less than the width of the body.

Also, be sure that:

Body.Width < Report.PageWidth - Report.LeftMargin - Report.RightMargin

-Chris

|||

Chris Baldwin - MSFT wrote:

Please verify that the definition width of your table (regardless of any hidden columns) is less than the width of the body.

Also, be sure that:

Body.Width < Report.PageWidth - Report.LeftMargin - Report.RightMargin

-Chris

I am trying to accomplish the same thing and my problem is the Body width as mentioned by Chris.. it is too wide since my available set of columns is fairly large. Are there any known tricks to work around this limitation, using matrices, or whatever technique?

- Ron

Exporting PDF - Adding empty page

Hi,

I created a report using dynamic display( I hide the column using the expression in Property->Visibility).By using expression the column which is having null is hided.When I try to export the report to PDF,the empty pages are displaying along with data.Ie.,The report contyains only 5 pages but in PDF it is displaying 10 pages(5pages data with 5 empty pages).

Any Suggestions appreciated!

Thanks

Please verify that the definition width of your table (regardless of any hidden columns) is less than the width of the body.

Also, be sure that:

Body.Width < Report.PageWidth - Report.LeftMargin - Report.RightMargin

-Chris

|||

Chris Baldwin - MSFT wrote:

Please verify that the definition width of your table (regardless of any hidden columns) is less than the width of the body.

Also, be sure that:

Body.Width < Report.PageWidth - Report.LeftMargin - Report.RightMargin

-Chris

I am trying to accomplish the same thing and my problem is the Body width as mentioned by Chris.. it is too wide since my available set of columns is fairly large. Are there any known tricks to work around this limitation, using matrices, or whatever technique?

- Ron

Exporting data with dynamic fields

Hi,

I have one Query Builder application where user creates queries and generates output with required fields.Then user can export the same to excel (Using farPointSpread properties)
But if no. of records goes beyond 10K it goes too slow or even user machine hangs up. I want to give proper export facility. Can it be given using DTS?

I tried DTS (.vbs) file. but for random field selection it did not work.DTS package asks for new Transactions to be built for every change in Source table structure. It first creates the table in the destination databse and then exports the data.
If I try modify the VB code generated by the package to match with new Source table it does'nt work.

Can anyone tell me what should I do for export the data dynamically i.e. export the tables with differrent structres?

Thanx in advance.|||You should do a helluvalotta programming. DTS sucks, and I don't believe most people on this forum use it for much more than directly transfering defined recordsets.

Export To Excel

Hi,

I'm trying to use the export to Excel (Excel Destination) however, I wish to supply a dynamic piece of SQL to generate the data.

When I set the properties I just get an option to enter "Table or View", "Table or View as Variable" or "SQL Command".

The issue is that the table does not exist until the SSIS job is run and the columns will not always be the same anyway.

How can I use a simple dynamic piece of SQL (or stored proc) to get a recordset that is simply dumped out to excel - rows... columns... nothing more ?.

Help very much appreciated - Paul.

I am afraid you cannot get a generic 'export to excel' utility using SSIS. The dataflow metadata can not be generated/changed dynamically at run time.

The closest thing you can get is to have a package per every source/destination; creating the excel sheet at run time is not a problem. The problem is creating the source destination mappings.

|||

Yeah... I was worried someone would say as much !

What on earth is wrong with sending a dataset of *unknown* columns in a tabular form to an Excel spreadsheet ?...

Why must everything be so complicated and convoluted ?... Its a SIMPLE export job....

Seriously - I give up...

Thanks for the reply