Currency format when exporting to excel

Hi,

I have a problem with the number format when i export my reports to excel with Reporting Services. I set numbers as currency with the command FormatCurrency() in visual studio, but when i export the report to excel, the numbers are considered as text.

Does anyone have a solution?
Thanks in advance.

Use the Format property on the cell/textbox, for currency the format string should be c<number decimal places>, i.e. c0 prints the currency figure with no decimal places. Once you have done this, remove the FormatCurrency() function from the expression as it overrides anything you have in the Format property. The reason the FormatCurrency() does not work when exporting to Excel is because its return value is a string, so Excel is confused - is it a currency or is it a string?

|||Thanks a lot, it works perfectly!!!! I'm so releaved

Currency Exporting to Excel

Hi,
In one of my reports I have some fields that are currency fields displayed
with the currency format string (C). However, when I export these to Excel
(2003) I get the little yellow warning that says Number stored as text. And
if I try to do a sum by dragging across the cells and clicking the sigma
button at the top, it causes it to put an odd formula in the top row.
Is there an easy fix so that #'s exported as currency remain tied to excel
as currency?
Thanks,
ChrisI tried this on a matrix in RS2005 and it worked OK.
The format was c0. I do remember it being an issue in 2000. I don't
think there was a way round it in the report definition.
The only thing you could try is, in Excel, highlight the column and
format the cell to currency. If this works you will be able to do a SUM.
Cheers
Chris
Chris Taylor wrote:
> Hi,
> In one of my reports I have some fields that are currency fields
> displayed with the currency format string (C). However, when I
> export these to Excel (2003) I get the little yellow warning that
> says Number stored as text. And if I try to do a sum by dragging
> across the cells and clicking the sigma button at the top, it causes
> it to put an odd formula in the top row.
> Is there an easy fix so that #'s exported as currency remain tied to
> excel as currency?
> Thanks,
> Chris|||Tried formatting C0, stlil getting the text formatted as #.
MS any insight on this?
"Chris" <mr.mcgoo@.gmail.com> wrote in message
news:uPH9wVvQGHA.2704@.TK2MSFTNGP15.phx.gbl...
>I tried this on a matrix in RS2005 and it worked OK.
> The format was c0. I do remember it being an issue in 2000. I don't
> think there was a way round it in the report definition.
> The only thing you could try is, in Excel, highlight the column and
> format the cell to currency. If this works you will be able to do a SUM.
> Cheers
> Chris
>
> Chris Taylor wrote:
>> Hi,
>> In one of my reports I have some fields that are currency fields
>> displayed with the currency format string (C). However, when I
>> export these to Excel (2003) I get the little yellow warning that
>> says Number stored as text. And if I try to do a sum by dragging
>> across the cells and clicking the sigma button at the top, it causes
>> it to put an odd formula in the top row.
>> Is there an easy fix so that #'s exported as currency remain tied to
>> excel as currency?
>> Thanks,
>> Chris
>
> --
>|||Hi Chris,
Please modify the column width in Excel. I have tested in my side on RS
2005, it works fine.
Wei Lu
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Nope. I just tried this; both FormatCurrency and Format c0 send a
number as text, causing Excel to just put a Smart Tag on it and ignore
it in functions. I know that converting numbers to text is the entire
purpose of those two functions, but making them the sole means of
formatting numbers makes the Excel export function about as useless as
nipples on the Batsuit.
Wei Lu: I think Chris Taylor means "text formatted as number" and not
"the column's too narrow, so Excel puts in pound signs to tell you to
resize the column."

CSV Render Engine

Hi

I have Reporting Services hosted on a server which has Workgroup edition of SQL Server which does not support csv export. I would like to write a csv Renderer.

I am not sure how complex this task is likely to be.
Are there any White Papers or samples that would assist ?
Any advice to point me in the right direction would be most appreciated.

Regards

JohnJames

Hi Chaps

I have just found an article on MSDN stating that
writing a Render is a very complex operation.
Will now seek another alternative.

Regards

JohnJames

csv export without headings

Hi,

is it possible to export a report to a csv file without the headings?

at best i have been able to hide the headings in the report, but when exported to csv file it includes a row at the top of commas, then the data follows. I need the file to be just the data.

thank.

Hi,

Most of the elements on a report contain some properties concerning the output format. You can disable/enable certain elements.

For example if you don't want to export the headers of a table, then you need to perform the following actions:

select a cell in the header of the table|||Hi,

thanks for replying, that kind of worked. I am still getting the first row to be a row of commas. do you know how i can get it to omit this first row of commas?

if not, we could have all the column headings, but because it's a matrix, it's not exporting my static column headings. any ideas on this?

Thanks.|||I'm still having trouble with this so if anyone has any ideas i'd love to hear them.

My report has a matrix no it, which has 6 static columns. Above the static columns i've placed a table object. In that table object i've remove the footer and details section and added 6 columns so that the 6 static column in my matric can have column headings.

When i export to CSV the static column headings do not get exported, instead it exports just the columns that seperate the fields. The column headings for the matrix appear after the 6 commas.

I either need to hide this whole first row in the CSV file, or have it populated properly with the static column names.|||

To eliminate column title row that you see before the data, use NoHeader option:

http://msdn2.microsoft.com/en-us/library/ms155365.aspx

You can use it with URL access (add &rc:NoHeader=true to report url), or, for RS 2005, you can configure your CSV rendering extension to always ommit the header row.

CSV renderer doesn't stack data from 2 different data regions, so your trick with table above matrix won't get you the result you are looking for.

|||thank you so much. that has worked!!!!!|||

Hi, Denis

I have been trying for two days to figure out how to export reports in csv without headers. You've explained it but I still can't figure out how to do it. Can you assist me?

1) I'd like to be able to have the user select the csv format and export (from Report Manager) to csv format w/o headers...and

2) in a subscription that will automatically export a report to users in a csv w/o headers format. Can you give me some examples?

thanks!!!

|||

Denis

Specifically, you indicated:

You can use it with URL access (add &rc:NoHeader=true to report url), or, for RS 2005, you can configure your CSV rendering extension to always ommit the header row....

how do I (in RS2005) configure my csv rendering extension to always omit the header row....

|||Hi Chaps

I have a Matrix Report with dynamic column headings
ie headings change subject to date
I cannot get the coulmn headings to export.

Is this possible with a Matrix report ?
any guidance most appreciated.

Regards

JohnJames

csv export without headings

Hi,

is it possible to export a report to a csv file without the headings?

at best i have been able to hide the headings in the report, but when exported to csv file it includes a row at the top of commas, then the data follows. I need the file to be just the data.

thank.

Hi,

Most of the elements on a report contain some properties concerning the output format. You can disable/enable certain elements.

For example if you don't want to export the headers of a table, then you need to perform the following actions:

select a cell in the header of the table|||Hi,

thanks for replying, that kind of worked. I am still getting the first row to be a row of commas. do you know how i can get it to omit this first row of commas?

if not, we could have all the column headings, but because it's a matrix, it's not exporting my static column headings. any ideas on this?

Thanks.
|||I'm still having trouble with this so if anyone has any ideas i'd love to hear them.

My report has a matrix no it, which has 6 static columns. Above the static columns i've placed a table object. In that table object i've remove the footer and details section and added 6 columns so that the 6 static column in my matric can have column headings.

When i export to CSV the static column headings do not get exported, instead it exports just the columns that seperate the fields. The column headings for the matrix appear after the 6 commas.

I either need to hide this whole first row in the CSV file, or have it populated properly with the static column names.
|||

To eliminate column title row that you see before the data, use NoHeader option:

http://msdn2.microsoft.com/en-us/library/ms155365.aspx

You can use it with URL access (add &rc:NoHeader=true to report url), or, for RS 2005, you can configure your CSV rendering extension to always ommit the header row.

CSV renderer doesn't stack data from 2 different data regions, so your trick with table above matrix won't get you the result you are looking for.

|||thank you so much. that has worked!!!!!
|||

Hi, Denis

I have been trying for two days to figure out how to export reports in csv without headers. You've explained it but I still can't figure out how to do it. Can you assist me?

1) I'd like to be able to have the user select the csv format and export (from Report Manager) to csv format w/o headers...and

2) in a subscription that will automatically export a report to users in a csv w/o headers format. Can you give me some examples?

thanks!!!

|||

Denis

Specifically, you indicated:

You can use it with URL access (add &rc:NoHeader=true to report url), or, for RS 2005, you can configure your CSV rendering extension to always ommit the header row....

how do I (in RS2005) configure my csv rendering extension to always omit the header row....

|||Hi Chaps

I have a Matrix Report with dynamic column headings
ie headings change subject to date
I cannot get the coulmn headings to export.

Is this possible with a Matrix report ?
any guidance most appreciated.

Regards

JohnJames

csv export without headings

Hi,

is it possible to export a report to a csv file without the headings?

at best i have been able to hide the headings in the report, but when exported to csv file it includes a row at the top of commas, then the data follows. I need the file to be just the data.

thank.

Hi,

Most of the elements on a report contain some properties concerning the output format. You can disable/enable certain elements.

For example if you don't want to export the headers of a table, then you need to perform the following actions:

select a cell in the header of the table|||Hi,

thanks for replying, that kind of worked. I am still getting the first row to be a row of commas. do you know how i can get it to omit this first row of commas?

if not, we could have all the column headings, but because it's a matrix, it's not exporting my static column headings. any ideas on this?

Thanks.
|||I'm still having trouble with this so if anyone has any ideas i'd love to hear them.

My report has a matrix no it, which has 6 static columns. Above the static columns i've placed a table object. In that table object i've remove the footer and details section and added 6 columns so that the 6 static column in my matric can have column headings.

When i export to CSV the static column headings do not get exported, instead it exports just the columns that seperate the fields. The column headings for the matrix appear after the 6 commas.

I either need to hide this whole first row in the CSV file, or have it populated properly with the static column names.
|||

To eliminate column title row that you see before the data, use NoHeader option:

http://msdn2.microsoft.com/en-us/library/ms155365.aspx

You can use it with URL access (add &rc:NoHeader=true to report url), or, for RS 2005, you can configure your CSV rendering extension to always ommit the header row.

CSV renderer doesn't stack data from 2 different data regions, so your trick with table above matrix won't get you the result you are looking for.

|||thank you so much. that has worked!!!!!
|||

Hi, Denis

I have been trying for two days to figure out how to export reports in csv without headers. You've explained it but I still can't figure out how to do it. Can you assist me?

1) I'd like to be able to have the user select the csv format and export (from Report Manager) to csv format w/o headers...and

2) in a subscription that will automatically export a report to users in a csv w/o headers format. Can you give me some examples?

thanks!!!

|||

Denis

Specifically, you indicated:

You can use it with URL access (add &rc:NoHeader=true to report url), or, for RS 2005, you can configure your CSV rendering extension to always ommit the header row....

how do I (in RS2005) configure my csv rendering extension to always omit the header row....

|||Hi Chaps

I have a Matrix Report with dynamic column headings
ie headings change subject to date
I cannot get the coulmn headings to export.

Is this possible with a Matrix report ?
any guidance most appreciated.

Regards

JohnJames

CSV export with single quotations for string fields

Hi

I need to export data to CSV file from Sql Reporting Services.

I am including single quotations in my view to display in SRS for string fields.

After export if we open in Notepad, for string field it is adding multiple quotations.

How to add single quotations for string fields - CSV files,

Please let me know if anybody knows.

Thx

Vijji

Yes. You can specify this value (it's called the "Qualifier") for the CSV renderer -- see http://msdn2.microsoft.com/en-us/library/ms155365.aspx

-- and I believe you can set the default for the value in the rsreportserver.config file as well -- see http://msdn2.microsoft.com/en-us/library/ms156281.aspx

>L<

|||

Hi Lisa Nicholls

Thank you so much for the response,

I changed in the config file as below

<Extension Name="CSV" Type="Microsoft.ReportingServices.Rendering.CsvRenderer.CsvReport,Microsoft.ReportingServices.CsvRendering">
<Configuration>
<DeviceInfo>
<Encoding>ASCII</Encoding>
<NoHeader>True</NoHeader>
<Qualifier>False</Qualifier>
</DeviceInfo>
</Configuration>
</Extension>

It is working fine.

I have another issue, any suggestions will be very helpful.

In my data string field having comma, while importing it is treating as seperate column.

How do we control with in the string comma values.

Thank you again

Vijji

|||

hi there,

This is on the same page of the docs I've already sent you to <s>. Use a different value for FieldDelimiter along with Qualifier, if your data contains a comma.

(Actually I think that they got the terms backwards -- it should be that the item for which the RS default is a comma is termed a "Field Separator" and the item for which the RS default is quotation mark is called the "Field Delimiter" -- but you get the idea <s>.)

HTH,

>L<

CSV Export problem

Hi
I wish to export a reportas CSV format, however when I open it in Excel it is assuming it is fixed width seperated, when it clearly is comma seperated! Is there any way I can get it to do it right?
I am using Excel 2000 to view the csv output, and it is being triggered via a URL on a ASP.NET application.
Thanks for any help.
Jan
*****************************************
* This message was posted via http://www.sqlmonster.com
*
* Report spam or abuse by clicking the following URL:
* http://www.sqlmonster.com/Uwe/Abuse.aspx?aid=0388cedae91e417186f2d4a5cdfc8406
*****************************************I have answered my own question, by applying the parameter
rc:Encoding=ASCII
to the URL!
*****************************************
* A copy of the whole thread can be found at:
* http://www.sqlmonster.com/Uwe/Forum.aspx/sql-server-reporting/5264
*
* Report spam or abuse by clicking the following URL:
* http://www.sqlmonster.com/Uwe/Abuse.aspx?aid=6357bd9e0da54182b1994c9908ce943b
*****************************************

CSV export missing row

Hello
Does any one have an explaination or work around for the missing first row
of data in csv export?
Please help!
Thanks
JessicaI am struggling with the same problem. Is there really no answer/help out
there?`
Thanks,
J. Schuetz.
"Jessica C" wrote:
> Hello
> Does any one have an explaination or work around for the missing first row
> of data in csv export?
> Please help!
> Thanks
> Jessica
>
>

CSV Export error

Hi,

After exporting a report to CSV format, when opening the file in Excel, all the data in a row comes into a single column, than spliting into different columns.

We can split into different columns using 'Text to columns' option from 'Data' Menu, but does not do defaultly as a CSV file is supposed to do.

Is this is bug with Reporting Service? Or am i missing something?

I am using release version of MS Reporting Service 2005.

Thanks,

Anobe

I experienced this problem too. The default setting is unicode, you have to specify ASCII for csv rendering. We were able to fix it by changing the config file.

File to change:

C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting Services\ReportServer\rsreportserver.config

Before:

<Extension Name="CSV" Type="Microsoft.ReportingServices.Rendering.CsvRenderer.CsvReport,Microsoft.ReportingServices.CsvRendering"/>

After:

<Extension Name="CSV" Type="Microsoft.ReportingServices.Rendering.CsvRenderer.CsvReport,Microsoft.ReportingServices.CsvRendering">

<Configuration>

<DeviceInfo>

<Encoding>ASCII</Encoding>

</DeviceInfo>

</Configuration>

</Extension>

|||

Thanks buddy,

this was very helpful. I didn't do the exact way, since i cannot change the config file. So, i handled the situation in the code using System.Text.UniEncoding.

|||

hi anobe....

i am facing the same situation like u...i cant change the config file. so i am wondering how did u handled the situation

using the system.text.uniencoding ? could you please elobrate further

thanks bro

CSV Export error

Hi,

After exporting a report to CSV format, when opening the file in Excel, all the data in a row comes into a single column, than spliting into different columns.

We can split into different columns using 'Text to columns' option from 'Data' Menu, but does not do defaultly as a CSV file is supposed to do.

Is this is bug with Reporting Service? Or am i missing something?

I am using release version of MS Reporting Service 2005.

Thanks,

Anobe

I experienced this problem too. The default setting is unicode, you have to specify ASCII for csv rendering. We were able to fix it by changing the config file.

File to change:

C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting Services\ReportServer\rsreportserver.config

Before:

<Extension Name="CSV" Type="Microsoft.ReportingServices.Rendering.CsvRenderer.CsvReport,Microsoft.ReportingServices.CsvRendering"/>

After:

<Extension Name="CSV" Type="Microsoft.ReportingServices.Rendering.CsvRenderer.CsvReport,Microsoft.ReportingServices.CsvRendering">

<Configuration>

<DeviceInfo>

<Encoding>ASCII</Encoding>

</DeviceInfo>

</Configuration>

</Extension>

|||

Thanks buddy,

this was very helpful. I didn't do the exact way, since i cannot change the config file. So, i handled the situation in the code using System.Text.UniEncoding.

|||

hi anobe....

i am facing the same situation like u...i cant change the config file. so i am wondering how did u handled the situation

using the system.text.uniencoding ? could you please elobrate further

thanks bro

|||In case you didn't get your problem solved (or for others out there with the same problem):

I was having this problem too and changing the encoding of the report to ASCII (default is UTF8 I think) fixed the problem.

I am calling my report through the url, you can pass the encoding as a url parameter, for example:
http://reportservername/ReportServer/report?rs:Command=Render&rs:Format=CSV&rc:Encoding=ASCII

CSV Export delimited not fixed

Since RS exports csv files using a comma delimiter, Excel doesn't by
default, open the file correctly. Is there a way to export to csv using a
format which excel will handle correctly using its default settings?
Currently the user must open the file from within Excel and specify
"Delimited" not "Fixed Width" and go through the Text Import Wizard.
Thanks in advance,
Ryan OpferIs there a problem with Excel format?
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
news:OkccOY3HFHA.1108@.TK2MSFTNGP10.phx.gbl...
> Since RS exports csv files using a comma delimiter, Excel doesn't by
> default, open the file correctly. Is there a way to export to csv using a
> format which excel will handle correctly using its default settings?
> Currently the user must open the file from within Excel and specify
> "Delimited" not "Fixed Width" and go through the Text Import Wizard.
> Thanks in advance,
> Ryan Opfer
>|||Thanks Bruce for the quick reply.
The Excel format is fine provided you go through the Text Import Wizard of
Excel and specify that the file is a comma delimited csv file not Fixed
Width. I would like to figure out how to Export from RS using a format in
which Excel will natively open the file as a comma delimited file and
thereby bypass having to have the user go through the Text Import Wizard.
There was a post back in November (Jan Bodey) that said she fixed this by
specifying rc:Encoding=ASCII, but I couldn't get this to work, and if I
could have, I wouldn't expect the user to put this in the link anyway.
Does that make more sense?
Thanks,
Ryan
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:e5%2331j3HFHA.1476@.TK2MSFTNGP09.phx.gbl...
> Is there a problem with Excel format?
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
> news:OkccOY3HFHA.1108@.TK2MSFTNGP10.phx.gbl...
>> Since RS exports csv files using a comma delimiter, Excel doesn't by
>> default, open the file correctly. Is there a way to export to csv using
>> a
>> format which excel will handle correctly using its default settings?
>> Currently the user must open the file from within Excel and specify
>> "Delimited" not "Fixed Width" and go through the Text Import Wizard.
>> Thanks in advance,
>> Ryan Opfer
>>
>|||I just noticed how I worded the subject title. By delimited not fixed, I
ment: default to "Delimited" not "Fixed Width".
Sorry for the confusion.
Ryan
"Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
news:OkccOY3HFHA.1108@.TK2MSFTNGP10.phx.gbl...
> Since RS exports csv files using a comma delimiter, Excel doesn't by
> default, open the file correctly. Is there a way to export to csv using a
> format which excel will handle correctly using its default settings?
> Currently the user must open the file from within Excel and specify
> "Delimited" not "Fixed Width" and go through the Text Import Wizard.
> Thanks in advance,
> Ryan Opfer
>|||You can render your report as an Excel file. No reason to use the CSV format
in the first place.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
news:uQS0Du3HFHA.3332@.TK2MSFTNGP15.phx.gbl...
> Thanks Bruce for the quick reply.
> The Excel format is fine provided you go through the Text Import Wizard of
> Excel and specify that the file is a comma delimited csv file not Fixed
> Width. I would like to figure out how to Export from RS using a format in
> which Excel will natively open the file as a comma delimited file and
> thereby bypass having to have the user go through the Text Import Wizard.
> There was a post back in November (Jan Bodey) that said she fixed this by
> specifying rc:Encoding=ASCII, but I couldn't get this to work, and if I
> could have, I wouldn't expect the user to put this in the link anyway.
> Does that make more sense?
> Thanks,
> Ryan
>
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:e5%2331j3HFHA.1476@.TK2MSFTNGP09.phx.gbl...
>> Is there a problem with Excel format?
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
>> news:OkccOY3HFHA.1108@.TK2MSFTNGP10.phx.gbl...
>> Since RS exports csv files using a comma delimiter, Excel doesn't by
>> default, open the file correctly. Is there a way to export to csv using
>> a
>> format which excel will handle correctly using its default settings?
>> Currently the user must open the file from within Excel and specify
>> "Delimited" not "Fixed Width" and go through the Text Import Wizard.
>> Thanks in advance,
>> Ryan Opfer
>>
>>
>|||An Excel format is what I tried first but I couldn't get around how Excel
sees the document (it's too smart). Excel sees the document map and puts it
on sheet 1 then on sheet 2 (which has the main table data) it shows drill
down. Ultimately this file will need to be imported into an MS SQL table so
it needs to be simple.
Excel would work fine if I can remove the document map (obviously I can do
this by just removing the document map from the report...and maybe that's
something the user will have to live with) and drill down capabilities (the
user can't live without this though), but by then I'd pretty much be looking
at a plain csv file anyway.
The key here is the user will be doing all this and just sending us back a
basic csv or Excel file for the sql import so thereby has to be a simple
process.
From your reply's, I take it that RS can't defign how it exports to csv or
for that matter Excel.
Thanks for the help,
Ryan
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:%23VOimb4HFHA.3076@.tk2msftngp13.phx.gbl...
> You can render your report as an Excel file. No reason to use the CSV
> format in the first place.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
> news:uQS0Du3HFHA.3332@.TK2MSFTNGP15.phx.gbl...
>> Thanks Bruce for the quick reply.
>> The Excel format is fine provided you go through the Text Import Wizard
>> of Excel and specify that the file is a comma delimited csv file not
>> Fixed Width. I would like to figure out how to Export from RS using a
>> format in which Excel will natively open the file as a comma delimited
>> file and thereby bypass having to have the user go through the Text
>> Import Wizard.
>> There was a post back in November (Jan Bodey) that said she fixed this by
>> specifying rc:Encoding=ASCII, but I couldn't get this to work, and if I
>> could have, I wouldn't expect the user to put this in the link anyway.
>> Does that make more sense?
>> Thanks,
>> Ryan
>>
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> news:e5%2331j3HFHA.1476@.TK2MSFTNGP09.phx.gbl...
>> Is there a problem with Excel format?
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
>> news:OkccOY3HFHA.1108@.TK2MSFTNGP10.phx.gbl...
>> Since RS exports csv files using a comma delimiter, Excel doesn't by
>> default, open the file correctly. Is there a way to export to csv
>> using a
>> format which excel will handle correctly using its default settings?
>> Currently the user must open the file from within Excel and specify
>> "Delimited" not "Fixed Width" and go through the Text Import Wizard.
>> Thanks in advance,
>> Ryan Opfer
>>
>>
>>
>|||Here is an idea for you. Have an additional report that is very plain and
exports to Excel well. Have it be the same as the other on as far as the
data is concerned and the report parameters. Then add a link that uses jump
to URL and have it render the second shadow report as Excel passing it the
parameters from the current report. I call it a shadow report because you
can set it to not be visible in list view so the user never sees it. The
only way it gets run is when they click on the link.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
news:%23V19fKAIFHA.2784@.TK2MSFTNGP09.phx.gbl...
> An Excel format is what I tried first but I couldn't get around how Excel
> sees the document (it's too smart). Excel sees the document map and puts
it
> on sheet 1 then on sheet 2 (which has the main table data) it shows drill
> down. Ultimately this file will need to be imported into an MS SQL table
so
> it needs to be simple.
> Excel would work fine if I can remove the document map (obviously I can do
> this by just removing the document map from the report...and maybe that's
> something the user will have to live with) and drill down capabilities
(the
> user can't live without this though), but by then I'd pretty much be
looking
> at a plain csv file anyway.
> The key here is the user will be doing all this and just sending us back a
> basic csv or Excel file for the sql import so thereby has to be a simple
> process.
> From your reply's, I take it that RS can't defign how it exports to csv or
> for that matter Excel.
> Thanks for the help,
> Ryan
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:%23VOimb4HFHA.3076@.tk2msftngp13.phx.gbl...
> > You can render your report as an Excel file. No reason to use the CSV
> > format in the first place.
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
> > news:uQS0Du3HFHA.3332@.TK2MSFTNGP15.phx.gbl...
> >> Thanks Bruce for the quick reply.
> >>
> >> The Excel format is fine provided you go through the Text Import Wizard
> >> of Excel and specify that the file is a comma delimited csv file not
> >> Fixed Width. I would like to figure out how to Export from RS using a
> >> format in which Excel will natively open the file as a comma delimited
> >> file and thereby bypass having to have the user go through the Text
> >> Import Wizard.
> >>
> >> There was a post back in November (Jan Bodey) that said she fixed this
by
> >> specifying rc:Encoding=ASCII, but I couldn't get this to work, and if I
> >> could have, I wouldn't expect the user to put this in the link anyway.
> >>
> >> Does that make more sense?
> >>
> >> Thanks,
> >>
> >> Ryan
> >>
> >>
> >> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> >> news:e5%2331j3HFHA.1476@.TK2MSFTNGP09.phx.gbl...
> >> Is there a problem with Excel format?
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
> >> news:OkccOY3HFHA.1108@.TK2MSFTNGP10.phx.gbl...
> >> Since RS exports csv files using a comma delimiter, Excel doesn't by
> >> default, open the file correctly. Is there a way to export to csv
> >> using a
> >> format which excel will handle correctly using its default settings?
> >> Currently the user must open the file from within Excel and specify
> >> "Delimited" not "Fixed Width" and go through the Text Import Wizard.
> >>
> >> Thanks in advance,
> >>
> >> Ryan Opfer
> >>
> >>
> >>
> >>
> >>
> >>
> >
> >
>|||Thanks Bruce for all the help, I do appreciate it. This sounds like an
adequate solution that I think will work.
It does seems strange though (although seemingly common for MS) to have RS
export to csv using a format that Excel doesn't natively understand by
default. I would have hoped that whatever MS decides to set as a default
format for csv would be the same between MS applications. I guess that's
just something we should all be use to by now anyway.
Ryan Opfer
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:u1VflVAIFHA.3536@.TK2MSFTNGP14.phx.gbl...
> Here is an idea for you. Have an additional report that is very plain and
> exports to Excel well. Have it be the same as the other on as far as the
> data is concerned and the report parameters. Then add a link that uses
> jump
> to URL and have it render the second shadow report as Excel passing it the
> parameters from the current report. I call it a shadow report because you
> can set it to not be visible in list view so the user never sees it. The
> only way it gets run is when they click on the link.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
> news:%23V19fKAIFHA.2784@.TK2MSFTNGP09.phx.gbl...
>> An Excel format is what I tried first but I couldn't get around how Excel
>> sees the document (it's too smart). Excel sees the document map and puts
> it
>> on sheet 1 then on sheet 2 (which has the main table data) it shows drill
>> down. Ultimately this file will need to be imported into an MS SQL table
> so
>> it needs to be simple.
>> Excel would work fine if I can remove the document map (obviously I can
>> do
>> this by just removing the document map from the report...and maybe that's
>> something the user will have to live with) and drill down capabilities
> (the
>> user can't live without this though), but by then I'd pretty much be
> looking
>> at a plain csv file anyway.
>> The key here is the user will be doing all this and just sending us back
>> a
>> basic csv or Excel file for the sql import so thereby has to be a simple
>> process.
>> From your reply's, I take it that RS can't defign how it exports to csv
>> or
>> for that matter Excel.
>> Thanks for the help,
>> Ryan
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> news:%23VOimb4HFHA.3076@.tk2msftngp13.phx.gbl...
>> > You can render your report as an Excel file. No reason to use the CSV
>> > format in the first place.
>> >
>> >
>> > --
>> > Bruce Loehle-Conger
>> > MVP SQL Server Reporting Services
>> >
>> > "Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
>> > news:uQS0Du3HFHA.3332@.TK2MSFTNGP15.phx.gbl...
>> >> Thanks Bruce for the quick reply.
>> >>
>> >> The Excel format is fine provided you go through the Text Import
>> >> Wizard
>> >> of Excel and specify that the file is a comma delimited csv file not
>> >> Fixed Width. I would like to figure out how to Export from RS using a
>> >> format in which Excel will natively open the file as a comma delimited
>> >> file and thereby bypass having to have the user go through the Text
>> >> Import Wizard.
>> >>
>> >> There was a post back in November (Jan Bodey) that said she fixed this
> by
>> >> specifying rc:Encoding=ASCII, but I couldn't get this to work, and if
>> >> I
>> >> could have, I wouldn't expect the user to put this in the link anyway.
>> >>
>> >> Does that make more sense?
>> >>
>> >> Thanks,
>> >>
>> >> Ryan
>> >>
>> >>
>> >> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> >> news:e5%2331j3HFHA.1476@.TK2MSFTNGP09.phx.gbl...
>> >> Is there a problem with Excel format?
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
>> >> news:OkccOY3HFHA.1108@.TK2MSFTNGP10.phx.gbl...
>> >> Since RS exports csv files using a comma delimiter, Excel doesn't by
>> >> default, open the file correctly. Is there a way to export to csv
>> >> using a
>> >> format which excel will handle correctly using its default settings?
>> >> Currently the user must open the file from within Excel and specify
>> >> "Delimited" not "Fixed Width" and go through the Text Import Wizard.
>> >>
>> >> Thanks in advance,
>> >>
>> >> Ryan Opfer
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >
>> >
>>
>|||For some reason, Excel doesn't understand Unicode CSV files by default. If
we did an ANSI CSV file (which you can specify in the DeviceInfo) then we
would lose data in certain scenarios. We could look at all of the characters
in the file and see whether we could use ANSI without data loss but this is
a lot of work.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
news:%23ETGwjAIFHA.1172@.TK2MSFTNGP12.phx.gbl...
> Thanks Bruce for all the help, I do appreciate it. This sounds like an
> adequate solution that I think will work.
>
> It does seems strange though (although seemingly common for MS) to have RS
> export to csv using a format that Excel doesn't natively understand by
> default. I would have hoped that whatever MS decides to set as a default
> format for csv would be the same between MS applications. I guess that's
> just something we should all be use to by now anyway.
>
> Ryan Opfer
>
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:u1VflVAIFHA.3536@.TK2MSFTNGP14.phx.gbl...
>> Here is an idea for you. Have an additional report that is very plain and
>> exports to Excel well. Have it be the same as the other on as far as the
>> data is concerned and the report parameters. Then add a link that uses
>> jump
>> to URL and have it render the second shadow report as Excel passing it
>> the
>> parameters from the current report. I call it a shadow report because you
>> can set it to not be visible in list view so the user never sees it. The
>> only way it gets run is when they click on the link.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
>> news:%23V19fKAIFHA.2784@.TK2MSFTNGP09.phx.gbl...
>> An Excel format is what I tried first but I couldn't get around how
>> Excel
>> sees the document (it's too smart). Excel sees the document map and puts
>> it
>> on sheet 1 then on sheet 2 (which has the main table data) it shows
>> drill
>> down. Ultimately this file will need to be imported into an MS SQL table
>> so
>> it needs to be simple.
>> Excel would work fine if I can remove the document map (obviously I can
>> do
>> this by just removing the document map from the report...and maybe
>> that's
>> something the user will have to live with) and drill down capabilities
>> (the
>> user can't live without this though), but by then I'd pretty much be
>> looking
>> at a plain csv file anyway.
>> The key here is the user will be doing all this and just sending us back
>> a
>> basic csv or Excel file for the sql import so thereby has to be a simple
>> process.
>> From your reply's, I take it that RS can't defign how it exports to csv
>> or
>> for that matter Excel.
>> Thanks for the help,
>> Ryan
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> news:%23VOimb4HFHA.3076@.tk2msftngp13.phx.gbl...
>> > You can render your report as an Excel file. No reason to use the CSV
>> > format in the first place.
>> >
>> >
>> > --
>> > Bruce Loehle-Conger
>> > MVP SQL Server Reporting Services
>> >
>> > "Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
>> > news:uQS0Du3HFHA.3332@.TK2MSFTNGP15.phx.gbl...
>> >> Thanks Bruce for the quick reply.
>> >>
>> >> The Excel format is fine provided you go through the Text Import
>> >> Wizard
>> >> of Excel and specify that the file is a comma delimited csv file not
>> >> Fixed Width. I would like to figure out how to Export from RS using
>> >> a
>> >> format in which Excel will natively open the file as a comma
>> >> delimited
>> >> file and thereby bypass having to have the user go through the Text
>> >> Import Wizard.
>> >>
>> >> There was a post back in November (Jan Bodey) that said she fixed
>> >> this
>> by
>> >> specifying rc:Encoding=ASCII, but I couldn't get this to work, and if
>> >> I
>> >> could have, I wouldn't expect the user to put this in the link
>> >> anyway.
>> >>
>> >> Does that make more sense?
>> >>
>> >> Thanks,
>> >>
>> >> Ryan
>> >>
>> >>
>> >> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> >> news:e5%2331j3HFHA.1476@.TK2MSFTNGP09.phx.gbl...
>> >> Is there a problem with Excel format?
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
>> >> news:OkccOY3HFHA.1108@.TK2MSFTNGP10.phx.gbl...
>> >> Since RS exports csv files using a comma delimiter, Excel doesn't
>> >> by
>> >> default, open the file correctly. Is there a way to export to csv
>> >> using a
>> >> format which excel will handle correctly using its default
>> >> settings?
>> >> Currently the user must open the file from within Excel and specify
>> >> "Delimited" not "Fixed Width" and go through the Text Import
>> >> Wizard.
>> >>
>> >> Thanks in advance,
>> >>
>> >> Ryan Opfer
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >
>> >
>>
>>
>

CSV export with characters "ÿþ"

CSV export with characters "ÿþ":
Using reporting services and URL encoding I'm exporting about 1000 records
to CSV format, after exporting i always these " ÿþ " special characters as
the beginning of the file.
these character can be seen clearly only if opened with office 97 or earlier
or with any HEX viewer.
It seems its a common problem with excel formatting.
http://groups.google.com.au/group/microsoft.public.excel.programming/browse_thread/thread/e540d95a1f3e83ae/4828dd254c80c8b9?q=%C3%BF%C3%BE+in+csv&rnum=2&hl=en
Does anyone has the same problem? I am not able to use this CSV for printing
with the printing softwares unless i manually remove these characters.
This problem disappeared if I select all data from CSV and paste it to a new
NOTEPAD and save as CSV. Is there any other way to avoid this extra work.
Cheers,
SRM.The CSV export from Report Manager uses the Unicode format for the CSV
created. You could try doing a jump to URL that specifies the ASCII format.
It is one of the options you can provide on the URL. Give that a try and see
if it solves the problem for you. It also solves the issue with Excel
opening it and putting everything in a single column. When exported as ASCII
CSV it opens up in Excel in all the correct columns.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"srm" <srm@.discussions.microsoft.com> wrote in message
news:2E59C2AE-833B-45B1-8FFE-84784B0AF82E@.microsoft.com...
> CSV export with characters "ÿþ":
> Using reporting services and URL encoding I'm exporting about 1000 records
> to CSV format, after exporting i always these " ÿþ " special characters as
> the beginning of the file.
> these character can be seen clearly only if opened with office 97 or
> earlier
> or with any HEX viewer.
> It seems its a common problem with excel formatting.
> http://groups.google.com.au/group/microsoft.public.excel.programming/browse_thread/thread/e540d95a1f3e83ae/4828dd254c80c8b9?q=%C3%BF%C3%BE+in+csv&rnum=2&hl=en
> Does anyone has the same problem? I am not able to use this CSV for
> printing
> with the printing softwares unless i manually remove these characters.
> This problem disappeared if I select all data from CSV and paste it to a
> new
> NOTEPAD and save as CSV. Is there any other way to avoid this extra work.
> Cheers,
> SRM.|||Tried with rs:Encoding=ASCII into the URL.
But did not remove those Characters. It's the same export format.
Given below is the part of the parameters within URL.
&rs:Command=Render&rs:Format=CSV&rc:Toolbar=false&rs:Encoding=ASCII&rc:Qualifier=*?&rc:NoHeader=true&rc:FieldDelimiter="|"&ProcessID=19653
Thank you.
Roy.
"Bruce L-C [MVP]" wrote:
> The CSV export from Report Manager uses the Unicode format for the CSV
> created. You could try doing a jump to URL that specifies the ASCII format.
> It is one of the options you can provide on the URL. Give that a try and see
> if it solves the problem for you. It also solves the issue with Excel
> opening it and putting everything in a single column. When exported as ASCII
> CSV it opens up in Excel in all the correct columns.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "srm" <srm@.discussions.microsoft.com> wrote in message
> news:2E59C2AE-833B-45B1-8FFE-84784B0AF82E@.microsoft.com...
> > CSV export with characters "ÿþ":
> >
> > Using reporting services and URL encoding I'm exporting about 1000 records
> > to CSV format, after exporting i always these " ÿþ " special characters as
> > the beginning of the file.
> >
> > these character can be seen clearly only if opened with office 97 or
> > earlier
> > or with any HEX viewer.
> >
> > It seems its a common problem with excel formatting.
> >
> > http://groups.google.com.au/group/microsoft.public.excel.programming/browse_thread/thread/e540d95a1f3e83ae/4828dd254c80c8b9?q=%C3%BF%C3%BE+in+csv&rnum=2&hl=en
> >
> > Does anyone has the same problem? I am not able to use this CSV for
> > printing
> > with the printing softwares unless i manually remove these characters.
> >
> > This problem disappeared if I select all data from CSV and paste it to a
> > new
> > NOTEPAD and save as CSV. Is there any other way to avoid this extra work.
> >
> > Cheers,
> > SRM.
>
>|||Oh well. It was worth a try. I don't have any other suggestions.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"srm" <srm@.discussions.microsoft.com> wrote in message
news:F88C961C-25A5-4DC7-9F75-22EB9D9AB99A@.microsoft.com...
> Tried with rs:Encoding=ASCII into the URL.
> But did not remove those Characters. It's the same export format.
> Given below is the part of the parameters within URL.
> &rs:Command=Render&rs:Format=CSV&rc:Toolbar=false&rs:Encoding=ASCII&rc:Qualifier=*?&rc:NoHeader=true&rc:FieldDelimiter="|"&ProcessID=19653
> Thank you.
> Roy.
>
> "Bruce L-C [MVP]" wrote:
>> The CSV export from Report Manager uses the Unicode format for the CSV
>> created. You could try doing a jump to URL that specifies the ASCII
>> format.
>> It is one of the options you can provide on the URL. Give that a try and
>> see
>> if it solves the problem for you. It also solves the issue with Excel
>> opening it and putting everything in a single column. When exported as
>> ASCII
>> CSV it opens up in Excel in all the correct columns.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "srm" <srm@.discussions.microsoft.com> wrote in message
>> news:2E59C2AE-833B-45B1-8FFE-84784B0AF82E@.microsoft.com...
>> > CSV export with characters "ÿþ":
>> >
>> > Using reporting services and URL encoding I'm exporting about 1000
>> > records
>> > to CSV format, after exporting i always these " ÿþ " special characters
>> > as
>> > the beginning of the file.
>> >
>> > these character can be seen clearly only if opened with office 97 or
>> > earlier
>> > or with any HEX viewer.
>> >
>> > It seems its a common problem with excel formatting.
>> >
>> > http://groups.google.com.au/group/microsoft.public.excel.programming/browse_thread/thread/e540d95a1f3e83ae/4828dd254c80c8b9?q=%C3%BF%C3%BE+in+csv&rnum=2&hl=en
>> >
>> > Does anyone has the same problem? I am not able to use this CSV for
>> > printing
>> > with the printing softwares unless i manually remove these characters.
>> >
>> > This problem disappeared if I select all data from CSV and paste it to
>> > a
>> > new
>> > NOTEPAD and save as CSV. Is there any other way to avoid this extra
>> > work.
>> >
>> > Cheers,
>> > SRM.
>>|||Instead of &rs:Encoding try &rc:Encoding
HTH
"srm" wrote:
> Tried with rs:Encoding=ASCII into the URL.
> But did not remove those Characters. It's the same export format.
> Given below is the part of the parameters within URL.
> &rs:Command=Render&rs:Format=CSV&rc:Toolbar=false&rs:Encoding=ASCII&rc:Qualifier=*?&rc:NoHeader=true&rc:FieldDelimiter="|"&ProcessID=19653
> Thank you.
> Roy.
>
> "Bruce L-C [MVP]" wrote:
> > The CSV export from Report Manager uses the Unicode format for the CSV
> > created. You could try doing a jump to URL that specifies the ASCII format.
> > It is one of the options you can provide on the URL. Give that a try and see
> > if it solves the problem for you. It also solves the issue with Excel
> > opening it and putting everything in a single column. When exported as ASCII
> > CSV it opens up in Excel in all the correct columns.
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "srm" <srm@.discussions.microsoft.com> wrote in message
> > news:2E59C2AE-833B-45B1-8FFE-84784B0AF82E@.microsoft.com...
> > > CSV export with characters "ÿþ":
> > >
> > > Using reporting services and URL encoding I'm exporting about 1000 records
> > > to CSV format, after exporting i always these " ÿþ " special characters as
> > > the beginning of the file.
> > >
> > > these character can be seen clearly only if opened with office 97 or
> > > earlier
> > > or with any HEX viewer.
> > >
> > > It seems its a common problem with excel formatting.
> > >
> > > http://groups.google.com.au/group/microsoft.public.excel.programming/browse_thread/thread/e540d95a1f3e83ae/4828dd254c80c8b9?q=%C3%BF%C3%BE+in+csv&rnum=2&hl=en
> > >
> > > Does anyone has the same problem? I am not able to use this CSV for
> > > printing
> > > with the printing softwares unless i manually remove these characters.
> > >
> > > This problem disappeared if I select all data from CSV and paste it to a
> > > new
> > > NOTEPAD and save as CSV. Is there any other way to avoid this extra work.
> > >
> > > Cheers,
> > > SRM.
> >
> >
> >

CSV export via BCP, spaces in database name >:(

Hello, I'm having trouble with an SQL database that has a space in it's name. What I want to do is extract the table "fileinfo" from the database "Vigilant Server" to a CSV file "FileInfo.CSV". Also, know that I am neither a programmer nor a DB admin, merely a general technician and a writer of DOS BAT files.

First I tried using OSQL:
OSQL -U xxx -P xxx -d "Vigilant Server" -Q "SELECT * FROM fileinfo" -o FileInfo.CSV
It works but is incredibly slow.

Then I heard about BCP, and tried this:
BCP "Vigilant Server..fileinfo" out FileInfo.CSV -U xxx -P xxx -c -t ,
No matter where I put the quotation marks, I can't get BCP to recognize Vigilant Server as the database name.

I am not doing something right? Is there another way to do this that's better suited to what I'm trying to do? Any help would be appreciated.Check out the books online (bol) for the bcp command:

To specify a database name that contains a space or quotation mark, you must use the q option.|||That worked just great, thank you for your help.|||You are welcome. The bol tool will be an invaluable resource for you.

CSV Export delimited not fixed

Since RS exports csv files using a comma delimiter, Excel doesn't by
default, open the file correctly. Is there a way to export to csv using a
format which excel will handle correctly using its default settings?
Currently the user must open the file from within Excel and specify
"Delimited" not "Fixed Width" and go through the Text Import Wizard.
Thanks in advance,
Ryan OpferIs there a problem with Excel format?
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
news:OkccOY3HFHA.1108@.TK2MSFTNGP10.phx.gbl...
> Since RS exports csv files using a comma delimiter, Excel doesn't by
> default, open the file correctly. Is there a way to export to csv using a
> format which excel will handle correctly using its default settings?
> Currently the user must open the file from within Excel and specify
> "Delimited" not "Fixed Width" and go through the Text Import Wizard.
> Thanks in advance,
> Ryan Opfer
>|||Thanks Bruce for the quick reply.
The Excel format is fine provided you go through the Text Import Wizard of
Excel and specify that the file is a comma delimited csv file not Fixed
Width. I would like to figure out how to Export from RS using a format in
which Excel will natively open the file as a comma delimited file and
thereby bypass having to have the user go through the Text Import Wizard.
There was a post back in November (Jan Bodey) that said she fixed this by
specifying rc:Encoding=ASCII, but I couldn't get this to work, and if I
could have, I wouldn't expect the user to put this in the link anyway.
Does that make more sense?
Thanks,
Ryan
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:e5%2331j3HFHA.1476@.TK2MSFTNGP09.phx.gbl...
> Is there a problem with Excel format?
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
> news:OkccOY3HFHA.1108@.TK2MSFTNGP10.phx.gbl...
>> Since RS exports csv files using a comma delimiter, Excel doesn't by
>> default, open the file correctly. Is there a way to export to csv using
>> a
>> format which excel will handle correctly using its default settings?
>> Currently the user must open the file from within Excel and specify
>> "Delimited" not "Fixed Width" and go through the Text Import Wizard.
>> Thanks in advance,
>> Ryan Opfer
>>
>|||I just noticed how I worded the subject title. By delimited not fixed, I
ment: default to "Delimited" not "Fixed Width".
Sorry for the confusion.
Ryan
"Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
news:OkccOY3HFHA.1108@.TK2MSFTNGP10.phx.gbl...
> Since RS exports csv files using a comma delimiter, Excel doesn't by
> default, open the file correctly. Is there a way to export to csv using a
> format which excel will handle correctly using its default settings?
> Currently the user must open the file from within Excel and specify
> "Delimited" not "Fixed Width" and go through the Text Import Wizard.
> Thanks in advance,
> Ryan Opfer
>|||You can render your report as an Excel file. No reason to use the CSV format
in the first place.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
news:uQS0Du3HFHA.3332@.TK2MSFTNGP15.phx.gbl...
> Thanks Bruce for the quick reply.
> The Excel format is fine provided you go through the Text Import Wizard of
> Excel and specify that the file is a comma delimited csv file not Fixed
> Width. I would like to figure out how to Export from RS using a format in
> which Excel will natively open the file as a comma delimited file and
> thereby bypass having to have the user go through the Text Import Wizard.
> There was a post back in November (Jan Bodey) that said she fixed this by
> specifying rc:Encoding=ASCII, but I couldn't get this to work, and if I
> could have, I wouldn't expect the user to put this in the link anyway.
> Does that make more sense?
> Thanks,
> Ryan
>
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:e5%2331j3HFHA.1476@.TK2MSFTNGP09.phx.gbl...
>> Is there a problem with Excel format?
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
>> news:OkccOY3HFHA.1108@.TK2MSFTNGP10.phx.gbl...
>> Since RS exports csv files using a comma delimiter, Excel doesn't by
>> default, open the file correctly. Is there a way to export to csv using
>> a
>> format which excel will handle correctly using its default settings?
>> Currently the user must open the file from within Excel and specify
>> "Delimited" not "Fixed Width" and go through the Text Import Wizard.
>> Thanks in advance,
>> Ryan Opfer
>>
>>
>|||An Excel format is what I tried first but I couldn't get around how Excel
sees the document (it's too smart). Excel sees the document map and puts it
on sheet 1 then on sheet 2 (which has the main table data) it shows drill
down. Ultimately this file will need to be imported into an MS SQL table so
it needs to be simple.
Excel would work fine if I can remove the document map (obviously I can do
this by just removing the document map from the report...and maybe that's
something the user will have to live with) and drill down capabilities (the
user can't live without this though), but by then I'd pretty much be looking
at a plain csv file anyway.
The key here is the user will be doing all this and just sending us back a
basic csv or Excel file for the sql import so thereby has to be a simple
process.
From your reply's, I take it that RS can't defign how it exports to csv or
for that matter Excel.
Thanks for the help,
Ryan
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:%23VOimb4HFHA.3076@.tk2msftngp13.phx.gbl...
> You can render your report as an Excel file. No reason to use the CSV
> format in the first place.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
> news:uQS0Du3HFHA.3332@.TK2MSFTNGP15.phx.gbl...
>> Thanks Bruce for the quick reply.
>> The Excel format is fine provided you go through the Text Import Wizard
>> of Excel and specify that the file is a comma delimited csv file not
>> Fixed Width. I would like to figure out how to Export from RS using a
>> format in which Excel will natively open the file as a comma delimited
>> file and thereby bypass having to have the user go through the Text
>> Import Wizard.
>> There was a post back in November (Jan Bodey) that said she fixed this by
>> specifying rc:Encoding=ASCII, but I couldn't get this to work, and if I
>> could have, I wouldn't expect the user to put this in the link anyway.
>> Does that make more sense?
>> Thanks,
>> Ryan
>>
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> news:e5%2331j3HFHA.1476@.TK2MSFTNGP09.phx.gbl...
>> Is there a problem with Excel format?
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
>> news:OkccOY3HFHA.1108@.TK2MSFTNGP10.phx.gbl...
>> Since RS exports csv files using a comma delimiter, Excel doesn't by
>> default, open the file correctly. Is there a way to export to csv
>> using a
>> format which excel will handle correctly using its default settings?
>> Currently the user must open the file from within Excel and specify
>> "Delimited" not "Fixed Width" and go through the Text Import Wizard.
>> Thanks in advance,
>> Ryan Opfer
>>
>>
>>
>|||Here is an idea for you. Have an additional report that is very plain and
exports to Excel well. Have it be the same as the other on as far as the
data is concerned and the report parameters. Then add a link that uses jump
to URL and have it render the second shadow report as Excel passing it the
parameters from the current report. I call it a shadow report because you
can set it to not be visible in list view so the user never sees it. The
only way it gets run is when they click on the link.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
news:%23V19fKAIFHA.2784@.TK2MSFTNGP09.phx.gbl...
> An Excel format is what I tried first but I couldn't get around how Excel
> sees the document (it's too smart). Excel sees the document map and puts
it
> on sheet 1 then on sheet 2 (which has the main table data) it shows drill
> down. Ultimately this file will need to be imported into an MS SQL table
so
> it needs to be simple.
> Excel would work fine if I can remove the document map (obviously I can do
> this by just removing the document map from the report...and maybe that's
> something the user will have to live with) and drill down capabilities
(the
> user can't live without this though), but by then I'd pretty much be
looking
> at a plain csv file anyway.
> The key here is the user will be doing all this and just sending us back a
> basic csv or Excel file for the sql import so thereby has to be a simple
> process.
> From your reply's, I take it that RS can't defign how it exports to csv or
> for that matter Excel.
> Thanks for the help,
> Ryan
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:%23VOimb4HFHA.3076@.tk2msftngp13.phx.gbl...
> > You can render your report as an Excel file. No reason to use the CSV
> > format in the first place.
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
> > news:uQS0Du3HFHA.3332@.TK2MSFTNGP15.phx.gbl...
> >> Thanks Bruce for the quick reply.
> >>
> >> The Excel format is fine provided you go through the Text Import Wizard
> >> of Excel and specify that the file is a comma delimited csv file not
> >> Fixed Width. I would like to figure out how to Export from RS using a
> >> format in which Excel will natively open the file as a comma delimited
> >> file and thereby bypass having to have the user go through the Text
> >> Import Wizard.
> >>
> >> There was a post back in November (Jan Bodey) that said she fixed this
by
> >> specifying rc:Encoding=ASCII, but I couldn't get this to work, and if I
> >> could have, I wouldn't expect the user to put this in the link anyway.
> >>
> >> Does that make more sense?
> >>
> >> Thanks,
> >>
> >> Ryan
> >>
> >>
> >> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> >> news:e5%2331j3HFHA.1476@.TK2MSFTNGP09.phx.gbl...
> >> Is there a problem with Excel format?
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
> >> news:OkccOY3HFHA.1108@.TK2MSFTNGP10.phx.gbl...
> >> Since RS exports csv files using a comma delimiter, Excel doesn't by
> >> default, open the file correctly. Is there a way to export to csv
> >> using a
> >> format which excel will handle correctly using its default settings?
> >> Currently the user must open the file from within Excel and specify
> >> "Delimited" not "Fixed Width" and go through the Text Import Wizard.
> >>
> >> Thanks in advance,
> >>
> >> Ryan Opfer
> >>
> >>
> >>
> >>
> >>
> >>
> >
> >
>|||Thanks Bruce for all the help, I do appreciate it. This sounds like an
adequate solution that I think will work.
It does seems strange though (although seemingly common for MS) to have RS
export to csv using a format that Excel doesn't natively understand by
default. I would have hoped that whatever MS decides to set as a default
format for csv would be the same between MS applications. I guess that's
just something we should all be use to by now anyway.
Ryan Opfer
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:u1VflVAIFHA.3536@.TK2MSFTNGP14.phx.gbl...
> Here is an idea for you. Have an additional report that is very plain and
> exports to Excel well. Have it be the same as the other on as far as the
> data is concerned and the report parameters. Then add a link that uses
> jump
> to URL and have it render the second shadow report as Excel passing it the
> parameters from the current report. I call it a shadow report because you
> can set it to not be visible in list view so the user never sees it. The
> only way it gets run is when they click on the link.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
> news:%23V19fKAIFHA.2784@.TK2MSFTNGP09.phx.gbl...
>> An Excel format is what I tried first but I couldn't get around how Excel
>> sees the document (it's too smart). Excel sees the document map and puts
> it
>> on sheet 1 then on sheet 2 (which has the main table data) it shows drill
>> down. Ultimately this file will need to be imported into an MS SQL table
> so
>> it needs to be simple.
>> Excel would work fine if I can remove the document map (obviously I can
>> do
>> this by just removing the document map from the report...and maybe that's
>> something the user will have to live with) and drill down capabilities
> (the
>> user can't live without this though), but by then I'd pretty much be
> looking
>> at a plain csv file anyway.
>> The key here is the user will be doing all this and just sending us back
>> a
>> basic csv or Excel file for the sql import so thereby has to be a simple
>> process.
>> From your reply's, I take it that RS can't defign how it exports to csv
>> or
>> for that matter Excel.
>> Thanks for the help,
>> Ryan
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> news:%23VOimb4HFHA.3076@.tk2msftngp13.phx.gbl...
>> > You can render your report as an Excel file. No reason to use the CSV
>> > format in the first place.
>> >
>> >
>> > --
>> > Bruce Loehle-Conger
>> > MVP SQL Server Reporting Services
>> >
>> > "Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
>> > news:uQS0Du3HFHA.3332@.TK2MSFTNGP15.phx.gbl...
>> >> Thanks Bruce for the quick reply.
>> >>
>> >> The Excel format is fine provided you go through the Text Import
>> >> Wizard
>> >> of Excel and specify that the file is a comma delimited csv file not
>> >> Fixed Width. I would like to figure out how to Export from RS using a
>> >> format in which Excel will natively open the file as a comma delimited
>> >> file and thereby bypass having to have the user go through the Text
>> >> Import Wizard.
>> >>
>> >> There was a post back in November (Jan Bodey) that said she fixed this
> by
>> >> specifying rc:Encoding=ASCII, but I couldn't get this to work, and if
>> >> I
>> >> could have, I wouldn't expect the user to put this in the link anyway.
>> >>
>> >> Does that make more sense?
>> >>
>> >> Thanks,
>> >>
>> >> Ryan
>> >>
>> >>
>> >> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> >> news:e5%2331j3HFHA.1476@.TK2MSFTNGP09.phx.gbl...
>> >> Is there a problem with Excel format?
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
>> >> news:OkccOY3HFHA.1108@.TK2MSFTNGP10.phx.gbl...
>> >> Since RS exports csv files using a comma delimiter, Excel doesn't by
>> >> default, open the file correctly. Is there a way to export to csv
>> >> using a
>> >> format which excel will handle correctly using its default settings?
>> >> Currently the user must open the file from within Excel and specify
>> >> "Delimited" not "Fixed Width" and go through the Text Import Wizard.
>> >>
>> >> Thanks in advance,
>> >>
>> >> Ryan Opfer
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >
>> >
>>
>|||For some reason, Excel doesn't understand Unicode CSV files by default. If
we did an ANSI CSV file (which you can specify in the DeviceInfo) then we
would lose data in certain scenarios. We could look at all of the characters
in the file and see whether we could use ANSI without data loss but this is
a lot of work.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
news:%23ETGwjAIFHA.1172@.TK2MSFTNGP12.phx.gbl...
> Thanks Bruce for all the help, I do appreciate it. This sounds like an
> adequate solution that I think will work.
>
> It does seems strange though (although seemingly common for MS) to have RS
> export to csv using a format that Excel doesn't natively understand by
> default. I would have hoped that whatever MS decides to set as a default
> format for csv would be the same between MS applications. I guess that's
> just something we should all be use to by now anyway.
>
> Ryan Opfer
>
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:u1VflVAIFHA.3536@.TK2MSFTNGP14.phx.gbl...
>> Here is an idea for you. Have an additional report that is very plain and
>> exports to Excel well. Have it be the same as the other on as far as the
>> data is concerned and the report parameters. Then add a link that uses
>> jump
>> to URL and have it render the second shadow report as Excel passing it
>> the
>> parameters from the current report. I call it a shadow report because you
>> can set it to not be visible in list view so the user never sees it. The
>> only way it gets run is when they click on the link.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
>> news:%23V19fKAIFHA.2784@.TK2MSFTNGP09.phx.gbl...
>> An Excel format is what I tried first but I couldn't get around how
>> Excel
>> sees the document (it's too smart). Excel sees the document map and puts
>> it
>> on sheet 1 then on sheet 2 (which has the main table data) it shows
>> drill
>> down. Ultimately this file will need to be imported into an MS SQL table
>> so
>> it needs to be simple.
>> Excel would work fine if I can remove the document map (obviously I can
>> do
>> this by just removing the document map from the report...and maybe
>> that's
>> something the user will have to live with) and drill down capabilities
>> (the
>> user can't live without this though), but by then I'd pretty much be
>> looking
>> at a plain csv file anyway.
>> The key here is the user will be doing all this and just sending us back
>> a
>> basic csv or Excel file for the sql import so thereby has to be a simple
>> process.
>> From your reply's, I take it that RS can't defign how it exports to csv
>> or
>> for that matter Excel.
>> Thanks for the help,
>> Ryan
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> news:%23VOimb4HFHA.3076@.tk2msftngp13.phx.gbl...
>> > You can render your report as an Excel file. No reason to use the CSV
>> > format in the first place.
>> >
>> >
>> > --
>> > Bruce Loehle-Conger
>> > MVP SQL Server Reporting Services
>> >
>> > "Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
>> > news:uQS0Du3HFHA.3332@.TK2MSFTNGP15.phx.gbl...
>> >> Thanks Bruce for the quick reply.
>> >>
>> >> The Excel format is fine provided you go through the Text Import
>> >> Wizard
>> >> of Excel and specify that the file is a comma delimited csv file not
>> >> Fixed Width. I would like to figure out how to Export from RS using
>> >> a
>> >> format in which Excel will natively open the file as a comma
>> >> delimited
>> >> file and thereby bypass having to have the user go through the Text
>> >> Import Wizard.
>> >>
>> >> There was a post back in November (Jan Bodey) that said she fixed
>> >> this
>> by
>> >> specifying rc:Encoding=ASCII, but I couldn't get this to work, and if
>> >> I
>> >> could have, I wouldn't expect the user to put this in the link
>> >> anyway.
>> >>
>> >> Does that make more sense?
>> >>
>> >> Thanks,
>> >>
>> >> Ryan
>> >>
>> >>
>> >> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> >> news:e5%2331j3HFHA.1476@.TK2MSFTNGP09.phx.gbl...
>> >> Is there a problem with Excel format?
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "Ryan Opfer" <ropfer@.usa.ibs.org> wrote in message
>> >> news:OkccOY3HFHA.1108@.TK2MSFTNGP10.phx.gbl...
>> >> Since RS exports csv files using a comma delimiter, Excel doesn't
>> >> by
>> >> default, open the file correctly. Is there a way to export to csv
>> >> using a
>> >> format which excel will handle correctly using its default
>> >> settings?
>> >> Currently the user must open the file from within Excel and specify
>> >> "Delimited" not "Fixed Width" and go through the Text Import
>> >> Wizard.
>> >>
>> >> Thanks in advance,
>> >>
>> >> Ryan Opfer
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >
>> >
>>
>>
>

CSV Export Bug

Hello,
I have a report that displays data from SQL Server, and it also has a
subscription that exports the report as a CSV file to a network share on
specified schedule. There is another external app that picks up the CSV file
and imports it into a proprietary database.
The report uses a stored procedure on the SQL Server to query data that is
displays on the report. When the query returns data, everything works well.
However, there are times when there is no data returned from the query (an
empty result set). If that happens, the report itself looks fine, but the
exported CSV is messed up. When I open up the exported CSV into a text
editor, all it shows is "table1". I am not sure where its getting "table1"
from, but logically, if there is no data to be reported, I would expect the
CSV to contain the headers (field names) and no data. Obviously, the
external app that imports this CSV is not smart enough to recognize that
"table1" means no data and the entire import process crashes.
If there are any workarounds or hot fixes for this bug, I would like to find
out about them ASAP since this is a production system.
Thank you,
MHAROONNo replies, so do I assume that no one else has run into this issue? This is
a pretty serious issue for us, so I would appreciate any help.
"mharoon" wrote:
> Hello,
> I have a report that displays data from SQL Server, and it also has a
> subscription that exports the report as a CSV file to a network share on
> specified schedule. There is another external app that picks up the CSV file
> and imports it into a proprietary database.
> The report uses a stored procedure on the SQL Server to query data that is
> displays on the report. When the query returns data, everything works well.
> However, there are times when there is no data returned from the query (an
> empty result set). If that happens, the report itself looks fine, but the
> exported CSV is messed up. When I open up the exported CSV into a text
> editor, all it shows is "table1". I am not sure where its getting "table1"
> from, but logically, if there is no data to be reported, I would expect the
> CSV to contain the headers (field names) and no data. Obviously, the
> external app that imports this CSV is not smart enough to recognize that
> "table1" means no data and the entire import process crashes.
> If there are any workarounds or hot fixes for this bug, I would like to find
> out about them ASAP since this is a production system.
> Thank you,
> MHAROON

CSV Export

I'm using a webclient to pull back the different rendering format's
available from SQL Reports. I guess MS added CSV files and I would like to
bring that down - but I'm having a little trouble passing the paramater that
will bring it back. Following is my current list. Does anyone know what it
should by for csv? (I've tried CSV and it doesn't work.)
case _rsTypePDF:
fext = "pdf";
ReportFormat = "PDF";
break;
case _rsTypeIMAGE:
fext = "tif";
ReportFormat = "IMAGE";
break;
case _rsTypeMHTML:
fext = "htm";
ReportFormat = "MHTML";
break;
case _rsTypeEXCEL:
fext = "xls";
ReportFormat = "EXCEL";
break;
Thanks,
DavidGot it to work - but realize it's not what I need.
Is there a way to render just the straight ascii in a report retaining some
of the formatting such as tabs - carriage returns - etc ?
<drchips@.nospam.nospam> wrote in message
news:ugbpufmNGHA.740@.TK2MSFTNGP12.phx.gbl...
> I'm using a webclient to pull back the different rendering format's
> available from SQL Reports. I guess MS added CSV files and I would like
> to bring that down - but I'm having a little trouble passing the paramater
> that will bring it back. Following is my current list. Does anyone know
> what it should by for csv? (I've tried CSV and it doesn't work.)
> case _rsTypePDF:
> fext = "pdf";
> ReportFormat = "PDF";
> break;
> case _rsTypeIMAGE:
> fext = "tif";
> ReportFormat = "IMAGE";
> break;
> case _rsTypeMHTML:
> fext = "htm";
> ReportFormat = "MHTML";
> break;
> case _rsTypeEXCEL:
> fext = "xls";
> ReportFormat = "EXCEL";
> break;
>
> Thanks,
>
> David
>|||Hi David,
Welcome to use MSDN Managed Newsgroup Support.
From your description, my understanding of this issue is: You want to
export the report to CSV with tab delimited. If I misunderstood your
concern, please feel free to point it out.
Reporting Services can not do it directly. Reporting Services only could
export the CSV with comma delimited. I think the best way is to do it in
Excel. You can create a new worksheet in Excel
1. Import the data from the CSV file and select the Delimited option
at the first step and select Comma as the Delimiter.
2. After import from the CSV file, you can save it as the Text(Tab
Delimited) type.
Hope this will be helpful.
Sincerely yours,
Wei Lu
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||I need a straight ASCII dump of a report with some of the formatting - such
as returns, etc. Is there a way to get that?
"Wei Lu" <t-weilu@.online.microsoft.com> wrote in message
news:r6JxVfsNGHA.2336@.TK2MSFTNGXA01.phx.gbl...
> Hi David,
> Welcome to use MSDN Managed Newsgroup Support.
> From your description, my understanding of this issue is: You want to
> export the report to CSV with tab delimited. If I misunderstood your
> concern, please feel free to point it out.
> Reporting Services can not do it directly. Reporting Services only could
> export the CSV with comma delimited. I think the best way is to do it in
> Excel. You can create a new worksheet in Excel
> 1. Import the data from the CSV file and select the Delimited option
> at the first step and select Comma as the Delimiter.
> 2. After import from the CSV file, you can save it as the Text(Tab
> Delimited) type.
>
> Hope this will be helpful.
> Sincerely yours,
> Wei Lu
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> =====================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||The other issue might be that he is getting the CSV in Unicode instead of
ASCII.
Here is an example of a Jump to URL link I use. This causes Excel to come up
with the data in a separate window:
="javascript:void(window.open('" & Globals!ReportServerUrl &
"?/SomeFolder/SomeReport&ParamName=" & Parameters!ParamName.Value &
"&rs:Format=CSV&rc:Encoding=ASCII','_blank'))"
If you don't want to have it appear in a new window then do this in jump to
URL:
=Globals!ReportServerUrl & "?/SomeFolder/SomeReport&ParamName=" &
Parameters!ParamName.Value & "&rs:Format=CSV&rc:Encoding=ASCII"
Note the rc:Encoding that is what causes the CSV to come up in ASCII. Excel
does not know how to handle unicode and puts all the data in a single
column. With ASCII, Excel will automatically split the data out into
multiple columns.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Wei Lu" <t-weilu@.online.microsoft.com> wrote in message
news:r6JxVfsNGHA.2336@.TK2MSFTNGXA01.phx.gbl...
> Hi David,
> Welcome to use MSDN Managed Newsgroup Support.
> From your description, my understanding of this issue is: You want to
> export the report to CSV with tab delimited. If I misunderstood your
> concern, please feel free to point it out.
> Reporting Services can not do it directly. Reporting Services only could
> export the CSV with comma delimited. I think the best way is to do it in
> Excel. You can create a new worksheet in Excel
> 1. Import the data from the CSV file and select the Delimited option
> at the first step and select Comma as the Delimiter.
> 2. After import from the CSV file, you can save it as the Text(Tab
> Delimited) type.
>
> Hope this will be helpful.
> Sincerely yours,
> Wei Lu
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> =====================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi David,
Thanks for the update. And also thanks Bruce's great suggestion.
I test the solution Bruce used and it works fine on my side.
I use the following statement in a Jump to URL property of a textbox.
=Globals!ReportServerUrl & "?/SomeFolder/SomeReport&ParamName=" &
Parameters!ParamName.Value & "&rs:Format=CSV&rc:Encoding=ASCII"
I think it meet your requirement.
Hope this will be helpful.
Wei Lu
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||I'm doing this in C#.
I wasn't sure what parameter you set to "_blank" so I set the mimetype to
it. Here's my code snippet:
case _rsTypeCSV:
fext = "csv";
ReportFormat = "CSV";
encoding = "ASCII";
mimeType = "_blank";
break;
}
results = rs.Render(ReportName, ReportFormat, historyID, deviceInfo,
parameters, credentials, showHide, out encoding, out mimeType, out
reportHistoryParameters, out warnings, out streamIDs);
I'm still getting back:
textbox1,textbox47,textbox30,textbox11,textbox72,textbox65,textbox27,textbox21,textbox57,textbox9,textbox4,textbox16,textbox78,textbox80,textbox12,textbox25,textbox36,RBP,Pulse,LBP,Icd9CodesTxt,textbox61,textbox41,textbox6,ExerciseProtocol,ExerciseStage,Time,ExerciseMets,RatePressure,HeartRate1Min,textbox170,textbox166,textbox162,TermMeds,textbox158,textbox154,textbox146,textbox142,textbox138,textbox114,textbox115,textbox110,textbox111,textbox106,textbox107,textbox102,textbox103,NlLowEf,textbox65,textbox61,textbox57,textbox93,textbox89,textbox85,textbox81,textbox77,textbox73,textbox69,AerobicCapacity,textbox49,textbox45,IschemicResponse,textbox41,textbox37,textbox33,textbox21,textbox18,textbox15,textbox12,textbox4,textbox3,textbox9,DateTxt
Nuclear Stress Imaging Report,"Palms Office
The whole report is a medical record which I can't show you - however - it
has still lost all of it's formatting. I'm not sure what I'm doing wrong
here.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:%23$jdHVvNGHA.1716@.TK2MSFTNGP10.phx.gbl...
> The other issue might be that he is getting the CSV in Unicode instead of
> ASCII.
> Here is an example of a Jump to URL link I use. This causes Excel to come
> up with the data in a separate window:
> ="javascript:void(window.open('" & Globals!ReportServerUrl &
> "?/SomeFolder/SomeReport&ParamName=" & Parameters!ParamName.Value &
> "&rs:Format=CSV&rc:Encoding=ASCII','_blank'))"
> If you don't want to have it appear in a new window then do this in jump
> to URL:
> =Globals!ReportServerUrl & "?/SomeFolder/SomeReport&ParamName=" &
> Parameters!ParamName.Value & "&rs:Format=CSV&rc:Encoding=ASCII"
> Note the rc:Encoding that is what causes the CSV to come up in ASCII.
> Excel does not know how to handle unicode and puts all the data in a
> single column. With ASCII, Excel will automatically split the data out
> into multiple columns.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Wei Lu" <t-weilu@.online.microsoft.com> wrote in message
> news:r6JxVfsNGHA.2336@.TK2MSFTNGXA01.phx.gbl...
>> Hi David,
>> Welcome to use MSDN Managed Newsgroup Support.
>> From your description, my understanding of this issue is: You want to
>> export the report to CSV with tab delimited. If I misunderstood your
>> concern, please feel free to point it out.
>> Reporting Services can not do it directly. Reporting Services only could
>> export the CSV with comma delimited. I think the best way is to do it in
>> Excel. You can create a new worksheet in Excel
>> 1. Import the data from the CSV file and select the Delimited option
>> at the first step and select Comma as the Delimiter.
>> 2. After import from the CSV file, you can save it as the Text(Tab
>> Delimited) type.
>>
>> Hope this will be helpful.
>> Sincerely yours,
>> Wei Lu
>> Microsoft Online Partner Support
>> Get Secure! - www.microsoft.com/security
>> =====================================================>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>> =====================================================>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>|||_blank is definitely not mime type. That had to do with the frame to show in
the browser.
What you will get back is comma separated variable. Looking at what you
posted it looks like that is what you go back. If you do not want comma
separated variables then don't use CSV export.
Also, the reason you are getting back all the textbox information is because
your report has multiple textboxes above the table. What I do is add
additional table header rows, merge the cells and put my titles etc there.
While working it out I suggest using a very clean report (nothing but your
table on it).
What formatting are you expecting? CSV puts all the fields for a row on one
line separated by commas. The CSV is great for getting data into Excel.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<drchips@.nospam.nospam> wrote in message
news:OoJ5nc9NGHA.3576@.TK2MSFTNGP15.phx.gbl...
> I'm doing this in C#.
> I wasn't sure what parameter you set to "_blank" so I set the mimetype to
> it. Here's my code snippet:
> case _rsTypeCSV:
> fext = "csv";
> ReportFormat = "CSV";
> encoding = "ASCII";
> mimeType = "_blank";
> break;
> }
> results = rs.Render(ReportName, ReportFormat, historyID, deviceInfo,
> parameters, credentials, showHide, out encoding, out mimeType, out
> reportHistoryParameters, out warnings, out streamIDs);
>
> I'm still getting back:
> textbox1,textbox47,textbox30,textbox11,textbox72,textbox65,textbox27,textbox21,textbox57,textbox9,textbox4,textbox16,textbox78,textbox80,textbox12,textbox25,textbox36,RBP,Pulse,LBP,Icd9CodesTxt,textbox61,textbox41,textbox6,ExerciseProtocol,ExerciseStage,Time,ExerciseMets,RatePressure,HeartRate1Min,textbox170,textbox166,textbox162,TermMeds,textbox158,textbox154,textbox146,textbox142,textbox138,textbox114,textbox115,textbox110,textbox111,textbox106,textbox107,textbox102,textbox103,NlLowEf,textbox65,textbox61,textbox57,textbox93,textbox89,textbox85,textbox81,textbox77,textbox73,textbox69,AerobicCapacity,textbox49,textbox45,IschemicResponse,textbox41,textbox37,textbox33,textbox21,textbox18,textbox15,textbox12,textbox4,textbox3,textbox9,DateTxt
> Nuclear Stress Imaging Report,"Palms Office
> The whole report is a medical record which I can't show you - however - it
> has still lost all of it's formatting. I'm not sure what I'm doing wrong
> here.
>
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:%23$jdHVvNGHA.1716@.TK2MSFTNGP10.phx.gbl...
>> The other issue might be that he is getting the CSV in Unicode instead of
>> ASCII.
>> Here is an example of a Jump to URL link I use. This causes Excel to come
>> up with the data in a separate window:
>> ="javascript:void(window.open('" & Globals!ReportServerUrl &
>> "?/SomeFolder/SomeReport&ParamName=" & Parameters!ParamName.Value &
>> "&rs:Format=CSV&rc:Encoding=ASCII','_blank'))"
>> If you don't want to have it appear in a new window then do this in jump
>> to URL:
>> =Globals!ReportServerUrl & "?/SomeFolder/SomeReport&ParamName=" &
>> Parameters!ParamName.Value & "&rs:Format=CSV&rc:Encoding=ASCII"
>> Note the rc:Encoding that is what causes the CSV to come up in ASCII.
>> Excel does not know how to handle unicode and puts all the data in a
>> single column. With ASCII, Excel will automatically split the data out
>> into multiple columns.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Wei Lu" <t-weilu@.online.microsoft.com> wrote in message
>> news:r6JxVfsNGHA.2336@.TK2MSFTNGXA01.phx.gbl...
>> Hi David,
>> Welcome to use MSDN Managed Newsgroup Support.
>> From your description, my understanding of this issue is: You want to
>> export the report to CSV with tab delimited. If I misunderstood your
>> concern, please feel free to point it out.
>> Reporting Services can not do it directly. Reporting Services only could
>> export the CSV with comma delimited. I think the best way is to do it in
>> Excel. You can create a new worksheet in Excel
>> 1. Import the data from the CSV file and select the Delimited
>> option
>> at the first step and select Comma as the Delimiter.
>> 2. After import from the CSV file, you can save it as the Text(Tab
>> Delimited) type.
>>
>> Hope this will be helpful.
>> Sincerely yours,
>> Wei Lu
>> Microsoft Online Partner Support
>> Get Secure! - www.microsoft.com/security
>> =====================================================>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>> =====================================================>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>|||It a medical diagnosis report. I need a straight ascii dump that retains
it's formatting as much as possible (Carriage returns - hopefully some
positioning by using spaces etc. )
Is there another format besides csv that can give me this? This information
needs to be posted to a central EMR repository for patient data and no meta
info for formatting is accepted by the system.
The way I'm sort of handling it now is to create an mshtml file - write a
bat file to launch it from my app. At that point - a transcriptionist has
to stick her cursor in the browser - hit Cntrl-A - Cntrl C - close the
browser - switch to her EMR interface - hit Cntrl V and save it. This
method doesn't bring any of the html tags over and retains some formatting.
I need to be able to eliminate the transcriptionists intervention in this so
she can focus on all the other work she has to do. Any suggestions? (I can
automate the interface between the systems with no problem - I just need the
ASCII dump)
Thanks for all your input so far.
David
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:ec90zo9NGHA.3936@.TK2MSFTNGP12.phx.gbl...
> _blank is definitely not mime type. That had to do with the frame to show
> in the browser.
> What you will get back is comma separated variable. Looking at what you
> posted it looks like that is what you go back. If you do not want comma
> separated variables then don't use CSV export.
> Also, the reason you are getting back all the textbox information is
> because your report has multiple textboxes above the table. What I do is
> add additional table header rows, merge the cells and put my titles etc
> there.
> While working it out I suggest using a very clean report (nothing but your
> table on it).
> What formatting are you expecting? CSV puts all the fields for a row on
> one line separated by commas. The CSV is great for getting data into
> Excel.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> <drchips@.nospam.nospam> wrote in message
> news:OoJ5nc9NGHA.3576@.TK2MSFTNGP15.phx.gbl...
>> I'm doing this in C#.
>> I wasn't sure what parameter you set to "_blank" so I set the mimetype to
>> it. Here's my code snippet:
>> case _rsTypeCSV:
>> fext = "csv";
>> ReportFormat = "CSV";
>> encoding = "ASCII";
>> mimeType = "_blank";
>> break;
>> }
>> results = rs.Render(ReportName, ReportFormat, historyID, deviceInfo,
>> parameters, credentials, showHide, out encoding, out mimeType, out
>> reportHistoryParameters, out warnings, out streamIDs);
>>
>> I'm still getting back:
>> textbox1,textbox47,textbox30,textbox11,textbox72,textbox65,textbox27,textbox21,textbox57,textbox9,textbox4,textbox16,textbox78,textbox80,textbox12,textbox25,textbox36,RBP,Pulse,LBP,Icd9CodesTxt,textbox61,textbox41,textbox6,ExerciseProtocol,ExerciseStage,Time,ExerciseMets,RatePressure,HeartRate1Min,textbox170,textbox166,textbox162,TermMeds,textbox158,textbox154,textbox146,textbox142,textbox138,textbox114,textbox115,textbox110,textbox111,textbox106,textbox107,textbox102,textbox103,NlLowEf,textbox65,textbox61,textbox57,textbox93,textbox89,textbox85,textbox81,textbox77,textbox73,textbox69,AerobicCapacity,textbox49,textbox45,IschemicResponse,textbox41,textbox37,textbox33,textbox21,textbox18,textbox15,textbox12,textbox4,textbox3,textbox9,DateTxt
>> Nuclear Stress Imaging Report,"Palms Office
>> The whole report is a medical record which I can't show you - however -
>> it has still lost all of it's formatting. I'm not sure what I'm doing
>> wrong here.
>>
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> news:%23$jdHVvNGHA.1716@.TK2MSFTNGP10.phx.gbl...
>> The other issue might be that he is getting the CSV in Unicode instead
>> of ASCII.
>> Here is an example of a Jump to URL link I use. This causes Excel to
>> come up with the data in a separate window:
>> ="javascript:void(window.open('" & Globals!ReportServerUrl &
>> "?/SomeFolder/SomeReport&ParamName=" & Parameters!ParamName.Value &
>> "&rs:Format=CSV&rc:Encoding=ASCII','_blank'))"
>> If you don't want to have it appear in a new window then do this in jump
>> to URL:
>> =Globals!ReportServerUrl & "?/SomeFolder/SomeReport&ParamName=" &
>> Parameters!ParamName.Value & "&rs:Format=CSV&rc:Encoding=ASCII"
>> Note the rc:Encoding that is what causes the CSV to come up in ASCII.
>> Excel does not know how to handle unicode and puts all the data in a
>> single column. With ASCII, Excel will automatically split the data out
>> into multiple columns.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Wei Lu" <t-weilu@.online.microsoft.com> wrote in message
>> news:r6JxVfsNGHA.2336@.TK2MSFTNGXA01.phx.gbl...
>> Hi David,
>> Welcome to use MSDN Managed Newsgroup Support.
>> From your description, my understanding of this issue is: You want to
>> export the report to CSV with tab delimited. If I misunderstood your
>> concern, please feel free to point it out.
>> Reporting Services can not do it directly. Reporting Services only
>> could
>> export the CSV with comma delimited. I think the best way is to do it
>> in
>> Excel. You can create a new worksheet in Excel
>> 1. Import the data from the CSV file and select the Delimited
>> option
>> at the first step and select Comma as the Delimiter.
>> 2. After import from the CSV file, you can save it as the Text(Tab
>> Delimited) type.
>>
>> Hope this will be helpful.
>> Sincerely yours,
>> Wei Lu
>> Microsoft Online Partner Support
>> Get Secure! - www.microsoft.com/security
>> =====================================================>> When responding to posts, please "Reply to Group" via your newsreader
>> so
>> that others may learn and benefit from your issue.
>> =====================================================>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>|||CSV does not do what you want. I am not aware of a straight ASCII output.
You could do html if this is from your own app and then strip the html tags
out (the .net framework has a library that would allow that).
Bruce Loehle-Conger
<drchips@.nospam.nospam> wrote in message
news:etrP63IOGHA.2916@.tk2msftngp13.phx.gbl...
> It a medical diagnosis report. I need a straight ascii dump that retains
> it's formatting as much as possible (Carriage returns - hopefully some
> positioning by using spaces etc. )
> Is there another format besides csv that can give me this? This
> information needs to be posted to a central EMR repository for patient
> data and no meta info for formatting is accepted by the system.
> The way I'm sort of handling it now is to create an mshtml file - write a
> bat file to launch it from my app. At that point - a transcriptionist has
> to stick her cursor in the browser - hit Cntrl-A - Cntrl C - close the
> browser - switch to her EMR interface - hit Cntrl V and save it. This
> method doesn't bring any of the html tags over and retains some
> formatting.
> I need to be able to eliminate the transcriptionists intervention in this
> so she can focus on all the other work she has to do. Any suggestions? (I
> can automate the interface between the systems with no problem - I just
> need the ASCII dump)
> Thanks for all your input so far.
> David
>
>
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:ec90zo9NGHA.3936@.TK2MSFTNGP12.phx.gbl...
>> _blank is definitely not mime type. That had to do with the frame to show
>> in the browser.
>> What you will get back is comma separated variable. Looking at what you
>> posted it looks like that is what you go back. If you do not want comma
>> separated variables then don't use CSV export.
>> Also, the reason you are getting back all the textbox information is
>> because your report has multiple textboxes above the table. What I do is
>> add additional table header rows, merge the cells and put my titles etc
>> there.
>> While working it out I suggest using a very clean report (nothing but
>> your table on it).
>> What formatting are you expecting? CSV puts all the fields for a row on
>> one line separated by commas. The CSV is great for getting data into
>> Excel.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> <drchips@.nospam.nospam> wrote in message
>> news:OoJ5nc9NGHA.3576@.TK2MSFTNGP15.phx.gbl...
>> I'm doing this in C#.
>> I wasn't sure what parameter you set to "_blank" so I set the mimetype
>> to it. Here's my code snippet:
>> case _rsTypeCSV:
>> fext = "csv";
>> ReportFormat = "CSV";
>> encoding = "ASCII";
>> mimeType = "_blank";
>> break;
>> }
>> results = rs.Render(ReportName, ReportFormat, historyID, deviceInfo,
>> parameters, credentials, showHide, out encoding, out mimeType, out
>> reportHistoryParameters, out warnings, out streamIDs);
>>
>> I'm still getting back:
>> textbox1,textbox47,textbox30,textbox11,textbox72,textbox65,textbox27,textbox21,textbox57,textbox9,textbox4,textbox16,textbox78,textbox80,textbox12,textbox25,textbox36,RBP,Pulse,LBP,Icd9CodesTxt,textbox61,textbox41,textbox6,ExerciseProtocol,ExerciseStage,Time,ExerciseMets,RatePressure,HeartRate1Min,textbox170,textbox166,textbox162,TermMeds,textbox158,textbox154,textbox146,textbox142,textbox138,textbox114,textbox115,textbox110,textbox111,textbox106,textbox107,textbox102,textbox103,NlLowEf,textbox65,textbox61,textbox57,textbox93,textbox89,textbox85,textbox81,textbox77,textbox73,textbox69,AerobicCapacity,textbox49,textbox45,IschemicResponse,textbox41,textbox37,textbox33,textbox21,textbox18,textbox15,textbox12,textbox4,textbox3,textbox9,DateTxt
>> Nuclear Stress Imaging Report,"Palms Office
>> The whole report is a medical record which I can't show you - however -
>> it has still lost all of it's formatting. I'm not sure what I'm doing
>> wrong here.
>>
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> news:%23$jdHVvNGHA.1716@.TK2MSFTNGP10.phx.gbl...
>> The other issue might be that he is getting the CSV in Unicode instead
>> of ASCII.
>> Here is an example of a Jump to URL link I use. This causes Excel to
>> come up with the data in a separate window:
>> ="javascript:void(window.open('" & Globals!ReportServerUrl &
>> "?/SomeFolder/SomeReport&ParamName=" & Parameters!ParamName.Value &
>> "&rs:Format=CSV&rc:Encoding=ASCII','_blank'))"
>> If you don't want to have it appear in a new window then do this in
>> jump to URL:
>> =Globals!ReportServerUrl & "?/SomeFolder/SomeReport&ParamName=" &
>> Parameters!ParamName.Value & "&rs:Format=CSV&rc:Encoding=ASCII"
>> Note the rc:Encoding that is what causes the CSV to come up in ASCII.
>> Excel does not know how to handle unicode and puts all the data in a
>> single column. With ASCII, Excel will automatically split the data out
>> into multiple columns.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Wei Lu" <t-weilu@.online.microsoft.com> wrote in message
>> news:r6JxVfsNGHA.2336@.TK2MSFTNGXA01.phx.gbl...
>> Hi David,
>> Welcome to use MSDN Managed Newsgroup Support.
>> From your description, my understanding of this issue is: You want to
>> export the report to CSV with tab delimited. If I misunderstood your
>> concern, please feel free to point it out.
>> Reporting Services can not do it directly. Reporting Services only
>> could
>> export the CSV with comma delimited. I think the best way is to do it
>> in
>> Excel. You can create a new worksheet in Excel
>> 1. Import the data from the CSV file and select the Delimited
>> option
>> at the first step and select Comma as the Delimiter.
>> 2. After import from the CSV file, you can save it as the
>> Text(Tab
>> Delimited) type.
>>
>> Hope this will be helpful.
>> Sincerely yours,
>> Wei Lu
>> Microsoft Online Partner Support
>> Get Secure! - www.microsoft.com/security
>> =====================================================>> When responding to posts, please "Reply to Group" via your newsreader
>> so
>> that others may learn and benefit from your issue.
>> =====================================================>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>>
>|||One thing that might work for you but I haven't done is to use XML output
and then provide your own xslt to get a straight ascii representation of
your report.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<drchips@.nospam.nospam> wrote in message
news:etrP63IOGHA.2916@.tk2msftngp13.phx.gbl...
> It a medical diagnosis report. I need a straight ascii dump that retains
> it's formatting as much as possible (Carriage returns - hopefully some
> positioning by using spaces etc. )
> Is there another format besides csv that can give me this? This
> information needs to be posted to a central EMR repository for patient
> data and no meta info for formatting is accepted by the system.
> The way I'm sort of handling it now is to create an mshtml file - write a
> bat file to launch it from my app. At that point - a transcriptionist has
> to stick her cursor in the browser - hit Cntrl-A - Cntrl C - close the
> browser - switch to her EMR interface - hit Cntrl V and save it. This
> method doesn't bring any of the html tags over and retains some
> formatting.
> I need to be able to eliminate the transcriptionists intervention in this
> so she can focus on all the other work she has to do. Any suggestions? (I
> can automate the interface between the systems with no problem - I just
> need the ASCII dump)
> Thanks for all your input so far.
> David
>
>
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:ec90zo9NGHA.3936@.TK2MSFTNGP12.phx.gbl...
>> _blank is definitely not mime type. That had to do with the frame to show
>> in the browser.
>> What you will get back is comma separated variable. Looking at what you
>> posted it looks like that is what you go back. If you do not want comma
>> separated variables then don't use CSV export.
>> Also, the reason you are getting back all the textbox information is
>> because your report has multiple textboxes above the table. What I do is
>> add additional table header rows, merge the cells and put my titles etc
>> there.
>> While working it out I suggest using a very clean report (nothing but
>> your table on it).
>> What formatting are you expecting? CSV puts all the fields for a row on
>> one line separated by commas. The CSV is great for getting data into
>> Excel.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> <drchips@.nospam.nospam> wrote in message
>> news:OoJ5nc9NGHA.3576@.TK2MSFTNGP15.phx.gbl...
>> I'm doing this in C#.
>> I wasn't sure what parameter you set to "_blank" so I set the mimetype
>> to it. Here's my code snippet:
>> case _rsTypeCSV:
>> fext = "csv";
>> ReportFormat = "CSV";
>> encoding = "ASCII";
>> mimeType = "_blank";
>> break;
>> }
>> results = rs.Render(ReportName, ReportFormat, historyID, deviceInfo,
>> parameters, credentials, showHide, out encoding, out mimeType, out
>> reportHistoryParameters, out warnings, out streamIDs);
>>
>> I'm still getting back:
>> textbox1,textbox47,textbox30,textbox11,textbox72,textbox65,textbox27,textbox21,textbox57,textbox9,textbox4,textbox16,textbox78,textbox80,textbox12,textbox25,textbox36,RBP,Pulse,LBP,Icd9CodesTxt,textbox61,textbox41,textbox6,ExerciseProtocol,ExerciseStage,Time,ExerciseMets,RatePressure,HeartRate1Min,textbox170,textbox166,textbox162,TermMeds,textbox158,textbox154,textbox146,textbox142,textbox138,textbox114,textbox115,textbox110,textbox111,textbox106,textbox107,textbox102,textbox103,NlLowEf,textbox65,textbox61,textbox57,textbox93,textbox89,textbox85,textbox81,textbox77,textbox73,textbox69,AerobicCapacity,textbox49,textbox45,IschemicResponse,textbox41,textbox37,textbox33,textbox21,textbox18,textbox15,textbox12,textbox4,textbox3,textbox9,DateTxt
>> Nuclear Stress Imaging Report,"Palms Office
>> The whole report is a medical record which I can't show you - however -
>> it has still lost all of it's formatting. I'm not sure what I'm doing
>> wrong here.
>>
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> news:%23$jdHVvNGHA.1716@.TK2MSFTNGP10.phx.gbl...
>> The other issue might be that he is getting the CSV in Unicode instead
>> of ASCII.
>> Here is an example of a Jump to URL link I use. This causes Excel to
>> come up with the data in a separate window:
>> ="javascript:void(window.open('" & Globals!ReportServerUrl &
>> "?/SomeFolder/SomeReport&ParamName=" & Parameters!ParamName.Value &
>> "&rs:Format=CSV&rc:Encoding=ASCII','_blank'))"
>> If you don't want to have it appear in a new window then do this in
>> jump to URL:
>> =Globals!ReportServerUrl & "?/SomeFolder/SomeReport&ParamName=" &
>> Parameters!ParamName.Value & "&rs:Format=CSV&rc:Encoding=ASCII"
>> Note the rc:Encoding that is what causes the CSV to come up in ASCII.
>> Excel does not know how to handle unicode and puts all the data in a
>> single column. With ASCII, Excel will automatically split the data out
>> into multiple columns.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Wei Lu" <t-weilu@.online.microsoft.com> wrote in message
>> news:r6JxVfsNGHA.2336@.TK2MSFTNGXA01.phx.gbl...
>> Hi David,
>> Welcome to use MSDN Managed Newsgroup Support.
>> From your description, my understanding of this issue is: You want to
>> export the report to CSV with tab delimited. If I misunderstood your
>> concern, please feel free to point it out.
>> Reporting Services can not do it directly. Reporting Services only
>> could
>> export the CSV with comma delimited. I think the best way is to do it
>> in
>> Excel. You can create a new worksheet in Excel
>> 1. Import the data from the CSV file and select the Delimited
>> option
>> at the first step and select Comma as the Delimiter.
>> 2. After import from the CSV file, you can save it as the
>> Text(Tab
>> Delimited) type.
>>
>> Hope this will be helpful.
>> Sincerely yours,
>> Wei Lu
>> Microsoft Online Partner Support
>> Get Secure! - www.microsoft.com/security
>> =====================================================>> When responding to posts, please "Reply to Group" via your newsreader
>> so
>> that others may learn and benefit from your issue.
>> =====================================================>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>>
>|||That would be great.
What is the name of that library?
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:e0wOQnKOGHA.2624@.TK2MSFTNGP12.phx.gbl...
> CSV does not do what you want. I am not aware of a straight ASCII output.
> You could do html if this is from your own app and then strip the html
> tags out (the .net framework has a library that would allow that).
> Bruce Loehle-Conger
>
> <drchips@.nospam.nospam> wrote in message
> news:etrP63IOGHA.2916@.tk2msftngp13.phx.gbl...
>> It a medical diagnosis report. I need a straight ascii dump that retains
>> it's formatting as much as possible (Carriage returns - hopefully some
>> positioning by using spaces etc. )
>> Is there another format besides csv that can give me this? This
>> information needs to be posted to a central EMR repository for patient
>> data and no meta info for formatting is accepted by the system.
>> The way I'm sort of handling it now is to create an mshtml file - write a
>> bat file to launch it from my app. At that point - a transcriptionist
>> has to stick her cursor in the browser - hit Cntrl-A - Cntrl C - close
>> the browser - switch to her EMR interface - hit Cntrl V and save it.
>> This method doesn't bring any of the html tags over and retains some
>> formatting.
>> I need to be able to eliminate the transcriptionists intervention in this
>> so she can focus on all the other work she has to do. Any suggestions?
>> (I can automate the interface between the systems with no problem - I
>> just need the ASCII dump)
>> Thanks for all your input so far.
>> David
>>
>>
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> news:ec90zo9NGHA.3936@.TK2MSFTNGP12.phx.gbl...
>> _blank is definitely not mime type. That had to do with the frame to
>> show in the browser.
>> What you will get back is comma separated variable. Looking at what you
>> posted it looks like that is what you go back. If you do not want comma
>> separated variables then don't use CSV export.
>> Also, the reason you are getting back all the textbox information is
>> because your report has multiple textboxes above the table. What I do is
>> add additional table header rows, merge the cells and put my titles etc
>> there.
>> While working it out I suggest using a very clean report (nothing but
>> your table on it).
>> What formatting are you expecting? CSV puts all the fields for a row on
>> one line separated by commas. The CSV is great for getting data into
>> Excel.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> <drchips@.nospam.nospam> wrote in message
>> news:OoJ5nc9NGHA.3576@.TK2MSFTNGP15.phx.gbl...
>> I'm doing this in C#.
>> I wasn't sure what parameter you set to "_blank" so I set the mimetype
>> to it. Here's my code snippet:
>> case _rsTypeCSV:
>> fext = "csv";
>> ReportFormat = "CSV";
>> encoding = "ASCII";
>> mimeType = "_blank";
>> break;
>> }
>> results = rs.Render(ReportName, ReportFormat, historyID, deviceInfo,
>> parameters, credentials, showHide, out encoding, out mimeType, out
>> reportHistoryParameters, out warnings, out streamIDs);
>>
>> I'm still getting back:
>> textbox1,textbox47,textbox30,textbox11,textbox72,textbox65,textbox27,textbox21,textbox57,textbox9,textbox4,textbox16,textbox78,textbox80,textbox12,textbox25,textbox36,RBP,Pulse,LBP,Icd9CodesTxt,textbox61,textbox41,textbox6,ExerciseProtocol,ExerciseStage,Time,ExerciseMets,RatePressure,HeartRate1Min,textbox170,textbox166,textbox162,TermMeds,textbox158,textbox154,textbox146,textbox142,textbox138,textbox114,textbox115,textbox110,textbox111,textbox106,textbox107,textbox102,textbox103,NlLowEf,textbox65,textbox61,textbox57,textbox93,textbox89,textbox85,textbox81,textbox77,textbox73,textbox69,AerobicCapacity,textbox49,textbox45,IschemicResponse,textbox41,textbox37,textbox33,textbox21,textbox18,textbox15,textbox12,textbox4,textbox3,textbox9,DateTxt
>> Nuclear Stress Imaging Report,"Palms Office
>> The whole report is a medical record which I can't show you - however -
>> it has still lost all of it's formatting. I'm not sure what I'm doing
>> wrong here.
>>
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> news:%23$jdHVvNGHA.1716@.TK2MSFTNGP10.phx.gbl...
>> The other issue might be that he is getting the CSV in Unicode instead
>> of ASCII.
>> Here is an example of a Jump to URL link I use. This causes Excel to
>> come up with the data in a separate window:
>> ="javascript:void(window.open('" & Globals!ReportServerUrl &
>> "?/SomeFolder/SomeReport&ParamName=" & Parameters!ParamName.Value &
>> "&rs:Format=CSV&rc:Encoding=ASCII','_blank'))"
>> If you don't want to have it appear in a new window then do this in
>> jump to URL:
>> =Globals!ReportServerUrl & "?/SomeFolder/SomeReport&ParamName=" &
>> Parameters!ParamName.Value & "&rs:Format=CSV&rc:Encoding=ASCII"
>> Note the rc:Encoding that is what causes the CSV to come up in ASCII.
>> Excel does not know how to handle unicode and puts all the data in a
>> single column. With ASCII, Excel will automatically split the data out
>> into multiple columns.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Wei Lu" <t-weilu@.online.microsoft.com> wrote in message
>> news:r6JxVfsNGHA.2336@.TK2MSFTNGXA01.phx.gbl...
>> Hi David,
>> Welcome to use MSDN Managed Newsgroup Support.
>> From your description, my understanding of this issue is: You want to
>> export the report to CSV with tab delimited. If I misunderstood your
>> concern, please feel free to point it out.
>> Reporting Services can not do it directly. Reporting Services only
>> could
>> export the CSV with comma delimited. I think the best way is to do it
>> in
>> Excel. You can create a new worksheet in Excel
>> 1. Import the data from the CSV file and select the Delimited
>> option
>> at the first step and select Comma as the Delimiter.
>> 2. After import from the CSV file, you can save it as the
>> Text(Tab
>> Delimited) type.
>>
>> Hope this will be helpful.
>> Sincerely yours,
>> Wei Lu
>> Microsoft Online Partner Support
>> Get Secure! - www.microsoft.com/security
>> =====================================================>> When responding to posts, please "Reply to Group" via your newsreader
>> so
>> that others may learn and benefit from your issue.
>> =====================================================>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>>
>>
>|||Here are several ideas for you:
http://weblogs.asp.net/rosherove/archive/2003/05/13/6963.aspx
http://www.freevbcode.com/ShowCode.asp?ID=110
This article gives some ideas plus how it can't do everything:
http://groups.google.com/group/microsoft.public.dotnet.languages.vb/browse_thread/thread/27332781e3126287/ceebf4e075a5a8ed%23ceebf4e075a5a8ed?sa=X&oi=groupsr&start=0&num=2
from the article:
>>>>>>>
How To Strip HTML Tags :
Well, the short answer is Regular Expressions, for example:
'(assuming that you have imported System.Text.RegularExpressions)
Dim oRegEx as Regex = RegEx("<[^>]*>")
Dim myNewString as string = oRegEx.Replace(myOldString, "")
However, that won't get you anywhere close to all the way. Even after you
entirely strip out all the <htmltags> you may be left with HTML-encoded
strings such as which you will also want to parse. These are easily
handled with
System.Web.HTTPUtility.HTMLDecode()
>>>>>>
You might be better off with XML and XSLT as I mentioned in another post.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<drchips@.nospam.nospam> wrote in message
news:O1NTj6WOGHA.2128@.TK2MSFTNGP10.phx.gbl...
> That would be great.
> What is the name of that library?
>
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:e0wOQnKOGHA.2624@.TK2MSFTNGP12.phx.gbl...
>> CSV does not do what you want. I am not aware of a straight ASCII output.
>> You could do html if this is from your own app and then strip the html
>> tags out (the .net framework has a library that would allow that).
>> Bruce Loehle-Conger
>>
>> <drchips@.nospam.nospam> wrote in message
>> news:etrP63IOGHA.2916@.tk2msftngp13.phx.gbl...
>> It a medical diagnosis report. I need a straight ascii dump that
>> retains it's formatting as much as possible (Carriage returns -
>> hopefully some positioning by using spaces etc. )
>> Is there another format besides csv that can give me this? This
>> information needs to be posted to a central EMR repository for patient
>> data and no meta info for formatting is accepted by the system.
>> The way I'm sort of handling it now is to create an mshtml file - write
>> a bat file to launch it from my app. At that point - a transcriptionist
>> has to stick her cursor in the browser - hit Cntrl-A - Cntrl C - close
>> the browser - switch to her EMR interface - hit Cntrl V and save it.
>> This method doesn't bring any of the html tags over and retains some
>> formatting.
>> I need to be able to eliminate the transcriptionists intervention in
>> this so she can focus on all the other work she has to do. Any
>> suggestions? (I can automate the interface between the systems with no
>> problem - I just need the ASCII dump)
>> Thanks for all your input so far.
>> David
>>
>>
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> news:ec90zo9NGHA.3936@.TK2MSFTNGP12.phx.gbl...
>> _blank is definitely not mime type. That had to do with the frame to
>> show in the browser.
>> What you will get back is comma separated variable. Looking at what you
>> posted it looks like that is what you go back. If you do not want comma
>> separated variables then don't use CSV export.
>> Also, the reason you are getting back all the textbox information is
>> because your report has multiple textboxes above the table. What I do
>> is add additional table header rows, merge the cells and put my titles
>> etc there.
>> While working it out I suggest using a very clean report (nothing but
>> your table on it).
>> What formatting are you expecting? CSV puts all the fields for a row on
>> one line separated by commas. The CSV is great for getting data into
>> Excel.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> <drchips@.nospam.nospam> wrote in message
>> news:OoJ5nc9NGHA.3576@.TK2MSFTNGP15.phx.gbl...
>> I'm doing this in C#.
>> I wasn't sure what parameter you set to "_blank" so I set the mimetype
>> to it. Here's my code snippet:
>> case _rsTypeCSV:
>> fext = "csv";
>> ReportFormat = "CSV";
>> encoding = "ASCII";
>> mimeType = "_blank";
>> break;
>> }
>> results = rs.Render(ReportName, ReportFormat, historyID, deviceInfo,
>> parameters, credentials, showHide, out encoding, out mimeType, out
>> reportHistoryParameters, out warnings, out streamIDs);
>>
>> I'm still getting back:
>> textbox1,textbox47,textbox30,textbox11,textbox72,textbox65,textbox27,textbox21,textbox57,textbox9,textbox4,textbox16,textbox78,textbox80,textbox12,textbox25,textbox36,RBP,Pulse,LBP,Icd9CodesTxt,textbox61,textbox41,textbox6,ExerciseProtocol,ExerciseStage,Time,ExerciseMets,RatePressure,HeartRate1Min,textbox170,textbox166,textbox162,TermMeds,textbox158,textbox154,textbox146,textbox142,textbox138,textbox114,textbox115,textbox110,textbox111,textbox106,textbox107,textbox102,textbox103,NlLowEf,textbox65,textbox61,textbox57,textbox93,textbox89,textbox85,textbox81,textbox77,textbox73,textbox69,AerobicCapacity,textbox49,textbox45,IschemicResponse,textbox41,textbox37,textbox33,textbox21,textbox18,textbox15,textbox12,textbox4,textbox3,textbox9,DateTxt
>> Nuclear Stress Imaging Report,"Palms Office
>> The whole report is a medical record which I can't show you -
>> however - it has still lost all of it's formatting. I'm not sure what
>> I'm doing wrong here.
>>
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> news:%23$jdHVvNGHA.1716@.TK2MSFTNGP10.phx.gbl...
>> The other issue might be that he is getting the CSV in Unicode
>> instead of ASCII.
>> Here is an example of a Jump to URL link I use. This causes Excel to
>> come up with the data in a separate window:
>> ="javascript:void(window.open('" & Globals!ReportServerUrl &
>> "?/SomeFolder/SomeReport&ParamName=" & Parameters!ParamName.Value &
>> "&rs:Format=CSV&rc:Encoding=ASCII','_blank'))"
>> If you don't want to have it appear in a new window then do this in
>> jump to URL:
>> =Globals!ReportServerUrl & "?/SomeFolder/SomeReport&ParamName=" &
>> Parameters!ParamName.Value & "&rs:Format=CSV&rc:Encoding=ASCII"
>> Note the rc:Encoding that is what causes the CSV to come up in
>> ASCII. Excel does not know how to handle unicode and puts all the
>> data in a single column. With ASCII, Excel will automatically split
>> the data out into multiple columns.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Wei Lu" <t-weilu@.online.microsoft.com> wrote in message
>> news:r6JxVfsNGHA.2336@.TK2MSFTNGXA01.phx.gbl...
>>> Hi David,
>>>
>>> Welcome to use MSDN Managed Newsgroup Support.
>>>
>>> From your description, my understanding of this issue is: You want
>>> to
>>> export the report to CSV with tab delimited. If I misunderstood your
>>> concern, please feel free to point it out.
>>>
>>> Reporting Services can not do it directly. Reporting Services only
>>> could
>>> export the CSV with comma delimited. I think the best way is to do
>>> it in
>>> Excel. You can create a new worksheet in Excel
>>>
>>> 1. Import the data from the CSV file and select the Delimited
>>> option
>>> at the first step and select Comma as the Delimiter.
>>>
>>> 2. After import from the CSV file, you can save it as the
>>> Text(Tab
>>> Delimited) type.
>>>
>>>
>>> Hope this will be helpful.
>>>
>>> Sincerely yours,
>>>
>>> Wei Lu
>>> Microsoft Online Partner Support
>>>
>>> Get Secure! - www.microsoft.com/security
>>> =====================================================>>> When responding to posts, please "Reply to Group" via your
>>> newsreader so
>>> that others may learn and benefit from your issue.
>>> =====================================================>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>>
>>
>>
>>
>>
>>
>