Showing posts with label cut. Show all posts
Showing posts with label cut. Show all posts

Wednesday, March 21, 2012

Exporting a RS 2005 report into a PDF file?

Hello!

I was able to export a report in RS 2005 into a .PDF file but since it is a wide report some of it got cut off in a PDF file. Is there a way to display the whole width of my report in PDF without cutting this off?

Thanks,

To be more specific, I would like to have my .pdf in landscape view after exporting to a .pdf file.

Thanks,

|||You can set the page size in Report->Properties->Layout. For landscape you would just swap the width and height of the papersize. For example, Letter is Width: 8.5in Height: 11in. To make this landscape, you would swap these values to be Width: 11in Height: 8.5in|||

That's exactly what I need to know.

Thanks a lot for your assistance.

Sunday, March 11, 2012

export to text file problem

Hi,
I recognise that long varchars are cut when exported to the text file.
This is the scenario:
Define varchar(6000) in the test table. Put in one line with , for example, 600 chars.
Run import data to the text file. The length of the string in the text file is only 232 chars.
Any idea?
Thanks,
Yana
Hi Yana,
I tried creating the testtable and exporting the data to the text file.
Surprisingly it worked correctly.
I would be glad if you can furnish some more information, so that I will be
able to work on it more appropriately.
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.

export to text file problem

Hi
I recognise that long varchars are cut when exported to the text file.
This is the scenario
Define varchar(6000) in the test table. Put in one line with , for example, 600 chars
Run import data to the text file. The length of the string in the text file is only 232 chars
Any idea
Thanks
YanaHi Yana,
I tried creating the testtable and exporting the data to the text file.
Surprisingly it worked correctly.
I would be glad if you can furnish some more information, so that I will be
able to work on it more appropriately.
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.

export to text file problem

Hi,
I recognise that long varchars are cut when exported to the text file.
This is the scenario:
Define varchar(6000) in the test table. Put in one line with , for example,
600 chars.
Run import data to the text file. The length of the string in the text file
is only 232 chars.
Any idea?
Thanks,
YanaHi Yana,
I tried creating the testtable and exporting the data to the text file.
Surprisingly it worked correctly.
I would be glad if you can furnish some more information, so that I will be
able to work on it more appropriately.
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.

Sunday, February 26, 2012

Export to Excel causes merged cells?

I have a report that is a table of data... the users export this report to
excel and then pivot the data in the table in order to cut and slice the data
to do analysis. When they go to insert a pivot table off of this report
Excel throws an error saying that the data source is not valid. What I've
noticed is that when reporting services exports the report to excel it
created one very narrow column and merges that column with the the next and
merges the cells in each of the rows below it' Also, even if I remove the
merged or hidden columns I still can't seem to pivot the data unless I do a
copy paste special values into a new workbook... it won't work if I just
paste into a new worksheet in the same workbook'
Any help you could provide would be greatly appreciated!On Mar 15, 12:54 pm, mr.letni <mrle...@.discussions.microsoft.com>
wrote:
> I have a report that is a table of data... the users export this report to
> excel and then pivot the data in the table in order to cut and slice the data
> to do analysis. When they go to insert a pivot table off of this report
> Excel throws an error saying that the data source is not valid. What I've
> noticed is that when reporting services exports the report to excel it
> created one very narrow column and merges that column with the the next and
> merges the cells in each of the rows below it' Also, even if I remove the
> merged or hidden columns I still can't seem to pivot the data unless I do a
> copy paste special values into a new workbook... it won't work if I just
> paste into a new worksheet in the same workbook'
> Any help you could provide would be greatly appreciated!
If you are using multiple tables (one-above-the-other) in a single
column report, I would suggest making sure that the column widths
match exactly between the multiple tables (that are one-above-the-
other). Also, make sure that your report title/independent textboxes
and table widths are the exact same width (i.e., don't have a report
title textbox smaller in width than the table(s) width). Other similar
kinds of nuances should apply as well. It depends on which axis you
see the merged cells on as far as which items need to be expanded to
match widths, etc. Also, make sure that there is no open space below
all items in the report to the bottom report border and no open space
to the right of the report items to the right border of the report.
I've had some very picky clients in regards to merged cell exports to
Excel and this was how I alleviated the merged cells for them. Hope
this helps.
Regards,
Enrique Martinez
Sr. SQL Server Developer|||The main issue I have seen is when I use a textbox at the top of my report
to put my title in. Instead, add additional header rows, then merge the
header row cells that you want to put your title in. When you use a text box
you end up with merged fields that then prevents sorting (or other
operations) on the data in Excel.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"mr.letni" <mrletni@.discussions.microsoft.com> wrote in message
news:4DD288E7-2C95-4A53-BB29-A86283B1C962@.microsoft.com...
>I have a report that is a table of data... the users export this report to
> excel and then pivot the data in the table in order to cut and slice the
> data
> to do analysis. When they go to insert a pivot table off of this report
> Excel throws an error saying that the data source is not valid. What I've
> noticed is that when reporting services exports the report to excel it
> created one very narrow column and merges that column with the the next
> and
> merges the cells in each of the rows below it' Also, even if I remove
> the
> merged or hidden columns I still can't seem to pivot the data unless I do
> a
> copy paste special values into a new workbook... it won't work if I just
> paste into a new worksheet in the same workbook'
> Any help you could provide would be greatly appreciated!

Friday, February 17, 2012

Export sql query to excel vba easier way

Hi,

I have a query ( Using sql) containing data that i need to export into excel.
I am currently exporting it by cut and paste the data, it is
not a very intuitive way of doing things, what i would prefer is if i
could have a button on a form which when it was clicked, it
automatically exported the query to a Excel file. Can anyone help me
with the VBA that would be neccessary, so i can connect excel and ms sql.Have you tried using MS query from Excel? Open a blank worksheet, click on "Data", "Import External Data", then "New Database Query". That will open up MS-Query with the query wizard. You can use the wizard to recreate your sql query from you db tables, or just stop the wizard, click on the SQL button in MS query and you can actually paste the sql code there. Will probably have some syntax issues, but those are pretty easy to solve. Once the query is created in MS-Query and you export the results to Excel, the query will be saved with the worksheet and you can use VB to simply refresh the query by the name you assign. Will need to set up an OBDC SQL driver to your db for this to work.

Note: If you can possibly create the query via the MSquery wizard, that is best, since you can then use fields from the Excel sheet to contain variable parameters to pass through to the query if you need to. If there are no variables to change on the sql query, it doesn't matter then.|||Another possibility is to use ODBC an call with an Access DB. Then use a form to export the data to excel.

We do that a lot with SQL and Oracle databases.|||You Can also use Ms SQL Server DTS.
Open the Export Wizard and set the source and destination. then enter your Query to run. at the Final Step Save the package as Vbscript.
now you can use this Code in your VB program and Run In your desired Time. you can also schedule it that SQL Server exports your data to Excel file in specified Times.
hope to be useful