Showing posts with label excel. Show all posts
Showing posts with label excel. Show all posts

Friday, March 30, 2012

I found a bug in MSSQL DTS import wizard

We have a textfile that we import in Excel(provided by our mainframe folks).
It's fixed width with 142 columns. When I import it in excel or ms access,
it gives me about ~34000 rows. But when I import using DTS package that is
exported to Access mdb, rows becomes ~17000 rows
And another hurdle that I'm faced is that there are rows that contains
combined data such as street, city and state all together without spaces.
Unfortunately, we can't modify the source text file. However, I do have a
fieldmarker(save a .txt file) which I always use in Excel so that when I
import it, I can select the area to create a vertical line just right that
marker.
Here is a sample of my fieldmarker.
12345p1234567p12pp123456p
Everytime i see a p, I click it with a mouse to create a vertical line in
fixed width importing. In that case, there are 5 columns. These are all
similar to ms access or excel.
The bug.
Please see this link below about the bug I found in MSSQL DTS Import wizard.
It doesn't happen in Excel or MS Access. Excel and MS Access can handle it
properly.
http://restricted.dyndns.org/dtsimportissue.html
Please help. Solution needed very badly!
Thanks,
Neil
"Neil" <neil-on-ht@.restricted.dyndns.org> wrote in message
news:Oj$m4gz5EHA.1292@.TK2MSFTNGP10.phx.gbl...
> We have a textfile that we import in Excel(provided by our mainframe
> folks). It's fixed width with 142 columns. When I import it in excel or ms
> access, it gives me about ~34000 rows. But when I import using DTS package
> that is exported to Access mdb, rows becomes ~17000 rows
> And another hurdle that I'm faced is that there are rows that contains
> combined data such as street, city and state all together without spaces.
> Unfortunately, we can't modify the source text file. However, I do have a
> fieldmarker(save a .txt file) which I always use in Excel so that when I
> import it, I can select the area to create a vertical line just right that
> marker.
> Here is a sample of my fieldmarker.
> 12345p1234567p12pp123456p
> Everytime i see a p, I click it with a mouse to create a vertical line in
> fixed width importing. In that case, there are 5 columns. These are all
> similar to ms access or excel.
> The bug.
> Please see this link below about the bug I found in MSSQL DTS Import
> wizard. It doesn't happen in Excel or MS Access. Excel and MS Access can
> handle it properly.
> http://restricted.dyndns.org/dtsimportissue.html
> Please help. Solution needed very badly!
It looks as though DTS is using the CRLF in the first line to define the
line lengths, and concatenating data in the rows because they are too short
and therefore incomplete records. What happens if you trim the first line
back to the same length as the other lines? Or how about padding the lines
out so they are all the same length?
According to http://support.microsoft.com/default...b;en-us;271247
if any rows are longer than expected then additional characters appear
wrapped in the DTS wizard, but are actually discarded.
However, in article
http://support.microsoft.com/default...b;en-us;247360 it mentions
that DTS expects a fixed length file to have lines of fixed length, and
having shorter lines will cause additional characters to be read from the
next line.
So the answer appears to be that in a fixed length import, make sure every
line is the same length to avoid this problem.
Dan
|||"Daniel Crichton" <msnews@.worldofspack.co.uk> wrote in message
news:uZDTPI05EHA.3076@.TK2MSFTNGP15.phx.gbl...
> It looks as though DTS is using the CRLF in the first line to define the
> line lengths, and concatenating data in the rows because they are too
> short and therefore incomplete records. What happens if you trim the first
> line back to the same length as the other lines? Or how about padding the
> lines out so they are all the same length?
> According to
> http://support.microsoft.com/default...b;en-us;271247 if any rows
> are longer than expected then additional characters appear wrapped in the
> DTS wizard, but are actually discarded.
> However, in article
> http://support.microsoft.com/default...b;en-us;247360 it
> mentions that DTS expects a fixed length file to have lines of fixed
> length, and having shorter lines will cause additional characters to be
> read from the next line.
> So the answer appears to be that in a fixed length import, make sure every
> line is the same length to avoid this problem.
>
Ok. Then we're out of luck then. I will contact the vendor if there will be
data for those columns in the future. If not, I can just delete it for now
to avoid the problem. It's just that MS Excel and Access support it. I don't
know why they didn't do that for DTS
Thanks.
Neil
|||Neil,
I don't quite understand your explanation or the online example. You
say this is a fixed-width file, but the example you give online shows a
first line that is much longer than the second line. Fixed-width means
every line of the text file has the same length. Your file has lines of
different lengths, but it also doesn't have a separator character
between each column, so the wizard won't help you, and you'll need to do
something else, I guess.
Maybe one of these will work:
Import using BULK INSERT with a format file.
Preprocess the file with Unix-like utilities to add delimiters, then
import as delimited
Import the file into a staging table with one long column, then split
it up with
insert into FinalDestinationTable
select substring(s,1,4), substring(s,5,7), ...
Steve Kass
Drew University
Neil wrote:

>We have a textfile that we import in Excel(provided by our mainframe folks).
>It's fixed width with 142 columns. When I import it in excel or ms access,
>it gives me about ~34000 rows. But when I import using DTS package that is
>exported to Access mdb, rows becomes ~17000 rows
>And another hurdle that I'm faced is that there are rows that contains
>combined data such as street, city and state all together without spaces.
>Unfortunately, we can't modify the source text file. However, I do have a
>fieldmarker(save a .txt file) which I always use in Excel so that when I
>import it, I can select the area to create a vertical line just right that
>marker.
>Here is a sample of my fieldmarker.
>12345p1234567p12pp123456p
>Everytime i see a p, I click it with a mouse to create a vertical line in
>fixed width importing. In that case, there are 5 columns. These are all
>similar to ms access or excel.
>The bug.
>Please see this link below about the bug I found in MSSQL DTS Import wizard.
>It doesn't happen in Excel or MS Access. Excel and MS Access can handle it
>properly.
>http://restricted.dyndns.org/dtsimportissue.html
>Please help. Solution needed very badly!
>Thanks,
>Neil
>
>
|||Sorry if my example is to confusing. The first row is actually coming
from a different text file. I call it field separator. I just wrote that
website for reference. My real field separator is about 2,050 characters
long. the data really starts at row 2 and they are all in fixed length.
Going back to the field separators, I use it only so that when I import
it using Fixed width, I will be able to tell where I need to click the
mouse.
Let say the mainframe file specs goes like this:
loanno text(10)
datewritten text(8)
code text(2)
state text(2)
zipcode text(5)
firstname text(5)
lastname text(5)
If the data was like this, it would have been ok
1234567890 12/21/04 DD IL 60061 frank burns
1234567891 12/21/04 DD IL 60061 ana saige
1234567892 12/21/04 DD IL 60061 polly yuigo
1234567893 12/21/04 DD IL 60061 jake snake
But our mainframe data is like this,
123456789012/21/04DDIL60061frankburns
123456789112/21/04DDIL60061ana saige
123456789212/21/04DDIL60061pollyyuigo
123456789312/21/04DDIL60061jake snake
For that example, I could have come up with a field marker like this
123456789p1234567p1p1p1234p1234p1234p. It works great in Excel and
Access. The p marker is just for me. It can be any. Unfortunately, the
target table for the DTS have more columns. I tried modify the data
above but still, DTS is importing it improperly. It's not intelligent
enough to pad it with blank spaces. I can pad using a different tool but
that's not a good solution. That's another point of failure.
I tried this data,
123456789012/21/04DDIL60061frankburns
123456789112/21/04DDIL60061ana saige
123456789212/21/04DDIL60061pollyyuigo
123456789312/21/04DDIL60061jake snakeBBBCCCCCDDDD
the data was still concatenated with the previous lines. So looks like,
DTS import is not honoring the {CR}{LF} but I'm 100% very sure that
there is an {CR}{LF}
Like what I said, it works perfect in Excel and Access. So I guess, this
is still considered a bug.
Thanks.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||I found a better solution in MS Access. I found it inside the Advanced
button when we do the import table wizard.
It's the table specification. It's awesome. Is this possible in DTS?
Thanks.
"Neil Camara" <neil-on-ht@.restricted.dyndns.org> wrote in message
news:ea%23nwe75EHA.2568@.TK2MSFTNGP10.phx.gbl...
> Sorry if my example is to confusing. The first row is actually coming
> from a different text file. I call it field separator. I just wrote that
> website for reference. My real field separator is about 2,050 characters
> long. the data really starts at row 2 and they are all in fixed length.
> Going back to the field separators, I use it only so that when I import
> it using Fixed width, I will be able to tell where I need to click the
> mouse.
> Let say the mainframe file specs goes like this:
> loanno text(10)
> datewritten text(8)
> code text(2)
> state text(2)
> zipcode text(5)
> firstname text(5)
> lastname text(5)
> If the data was like this, it would have been ok
> 1234567890 12/21/04 DD IL 60061 frank burns
> 1234567891 12/21/04 DD IL 60061 ana saige
> 1234567892 12/21/04 DD IL 60061 polly yuigo
> 1234567893 12/21/04 DD IL 60061 jake snake
> But our mainframe data is like this,
>
> 123456789012/21/04DDIL60061frankburns
> 123456789112/21/04DDIL60061ana saige
> 123456789212/21/04DDIL60061pollyyuigo
> 123456789312/21/04DDIL60061jake snake
> For that example, I could have come up with a field marker like this
> 123456789p1234567p1p1p1234p1234p1234p. It works great in Excel and
> Access. The p marker is just for me. It can be any. Unfortunately, the
> target table for the DTS have more columns. I tried modify the data
> above but still, DTS is importing it improperly. It's not intelligent
> enough to pad it with blank spaces. I can pad using a different tool but
> that's not a good solution. That's another point of failure.
> I tried this data,
> 123456789012/21/04DDIL60061frankburns
> 123456789112/21/04DDIL60061ana saige
> 123456789212/21/04DDIL60061pollyyuigo
> 123456789312/21/04DDIL60061jake snakeBBBCCCCCDDDD
> the data was still concatenated with the previous lines. So looks like,
> DTS import is not honoring the {CR}{LF} but I'm 100% very sure that
> there is an {CR}{LF}
> Like what I said, it works perfect in Excel and Access. So I guess, this
> is still considered a bug.
> Thanks.
>
>
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||Sorry, Neil, but I still don't understand. You have a text file with
equal length lines, and with <CRLF> ending each line, and dts doesn't
respect the end-of-line markers? You say you are 100% very sure that
there is an {CR}{LF}. Have you used a hex editor to be certain?
My earlier suggest to use BULK INSERT may work for you if indeed this is
a bug. You can specify a format file and bulk insert into a table that
has already been created.
SK
Neil Camara wrote:

>Sorry if my example is to confusing. The first row is actually coming
>from a different text file. I call it field separator. I just wrote that
>website for reference. My real field separator is about 2,050 characters
>long. the data really starts at row 2 and they are all in fixed length.
>Going back to the field separators, I use it only so that when I import
>it using Fixed width, I will be able to tell where I need to click the
>mouse.
>Let say the mainframe file specs goes like this:
>loanno text(10)
>datewritten text(8)
>code text(2)
>state text(2)
>zipcode text(5)
>firstname text(5)
>lastname text(5)
>If the data was like this, it would have been ok
>1234567890 12/21/04 DD IL 60061 frank burns
>1234567891 12/21/04 DD IL 60061 ana saige
>1234567892 12/21/04 DD IL 60061 polly yuigo
>1234567893 12/21/04 DD IL 60061 jake snake
>But our mainframe data is like this,
>
>123456789012/21/04DDIL60061frankburns
>123456789112/21/04DDIL60061ana saige
>123456789212/21/04DDIL60061pollyyuigo
>123456789312/21/04DDIL60061jake snake
>For that example, I could have come up with a field marker like this
>123456789p1234567p1p1p1234p1234p1234p. It works great in Excel and
>Access. The p marker is just for me. It can be any. Unfortunately, the
>target table for the DTS have more columns. I tried modify the data
>above but still, DTS is importing it improperly. It's not intelligent
>enough to pad it with blank spaces. I can pad using a different tool but
>that's not a good solution. That's another point of failure.
>I tried this data,
>123456789012/21/04DDIL60061frankburns
>123456789112/21/04DDIL60061ana saige
>123456789212/21/04DDIL60061pollyyuigo
>123456789312/21/04DDIL60061jake snakeBBBCCCCCDDDD
>the data was still concatenated with the previous lines. So looks like,
>DTS import is not honoring the {CR}{LF} but I'm 100% very sure that
>there is an {CR}{LF}
>Like what I said, it works perfect in Excel and Access. So I guess, this
>is still considered a bug.
>Thanks.
>
>
>
>*** Sent via Developersdex http://www.codecomments.com ***
>Don't just participate in USENET...get rewarded for it!
>
|||"Steve Kass" <skass@.drew.edu> wrote in message
news:OKuZfY%235EHA.2876@.TK2MSFTNGP12.phx.gbl...
> Sorry, Neil, but I still don't understand. You have a text file with
> equal length lines, and with <CRLF> ending each line, and dts doesn't
> respect the end-of-line markers? You say you are 100% very sure that
> there is an {CR}{LF}. Have you used a hex editor to be certain?
See my earlier reply with articles from the MS KB that mention that the
fixed width import requires all lines to be the same length, otherwise it
concatenates the data from successive lines to pad shorter lines out. Looks
like the CRLF is only used for the first line to determine the fixed row
length, all other lines are then dealt with using that length - extra
characters on lines are discarded, lines that are too short are treated as
continuing onto the next line.
Dan
|||Ok then. I'd have to accept that that is the way DTS works. I have to
fix my source by padding spaces. I can only say that Access or Excel
pads everything automatically for us. At least, that article explains
what I have found out.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
sql

I found a bug in MSSQL DTS import wizard

We have a textfile that we import in Excel(provided by our mainframe folks).
It's fixed width with 142 columns. When I import it in excel or ms access,
it gives me about ~34000 rows. But when I import using DTS package that is
exported to Access mdb, rows becomes ~17000 rows :(
And another hurdle that I'm faced is that there are rows that contains
combined data such as street, city and state all together without spaces.
Unfortunately, we can't modify the source text file. However, I do have a
fieldmarker(save a .txt file) which I always use in Excel so that when I
import it, I can select the area to create a vertical line just right that
marker.
Here is a sample of my fieldmarker.
12345p1234567p12pp123456p
Everytime i see a p, I click it with a mouse to create a vertical line in
fixed width importing. In that case, there are 5 columns. These are all
similar to ms access or excel.
The bug.
Please see this link below about the bug I found in MSSQL DTS Import wizard.
It doesn't happen in Excel or MS Access. Excel and MS Access can handle it
properly.
http://restricted.dyndns.org/dtsimportissue.html
Please help. Solution needed very badly!
Thanks,
Neil"Neil" <neil-on-ht@.restricted.dyndns.org> wrote in message
news:Oj$m4gz5EHA.1292@.TK2MSFTNGP10.phx.gbl...
> We have a textfile that we import in Excel(provided by our mainframe
> folks). It's fixed width with 142 columns. When I import it in excel or ms
> access, it gives me about ~34000 rows. But when I import using DTS package
> that is exported to Access mdb, rows becomes ~17000 rows :(
> And another hurdle that I'm faced is that there are rows that contains
> combined data such as street, city and state all together without spaces.
> Unfortunately, we can't modify the source text file. However, I do have a
> fieldmarker(save a .txt file) which I always use in Excel so that when I
> import it, I can select the area to create a vertical line just right that
> marker.
> Here is a sample of my fieldmarker.
> 12345p1234567p12pp123456p
> Everytime i see a p, I click it with a mouse to create a vertical line in
> fixed width importing. In that case, there are 5 columns. These are all
> similar to ms access or excel.
> The bug.
> Please see this link below about the bug I found in MSSQL DTS Import
> wizard. It doesn't happen in Excel or MS Access. Excel and MS Access can
> handle it properly.
> http://restricted.dyndns.org/dtsimportissue.html
> Please help. Solution needed very badly!
It looks as though DTS is using the CRLF in the first line to define the
line lengths, and concatenating data in the rows because they are too short
and therefore incomplete records. What happens if you trim the first line
back to the same length as the other lines? Or how about padding the lines
out so they are all the same length?
According to http://support.microsoft.com/default.aspx?scid=kb;en-us;271247
if any rows are longer than expected then additional characters appear
wrapped in the DTS wizard, but are actually discarded.
However, in article
http://support.microsoft.com/default.aspx?scid=kb;en-us;247360 it mentions
that DTS expects a fixed length file to have lines of fixed length, and
having shorter lines will cause additional characters to be read from the
next line.
So the answer appears to be that in a fixed length import, make sure every
line is the same length to avoid this problem.
Dan|||"Daniel Crichton" <msnews@.worldofspack.co.uk> wrote in message
news:uZDTPI05EHA.3076@.TK2MSFTNGP15.phx.gbl...
> It looks as though DTS is using the CRLF in the first line to define the
> line lengths, and concatenating data in the rows because they are too
> short and therefore incomplete records. What happens if you trim the first
> line back to the same length as the other lines? Or how about padding the
> lines out so they are all the same length?
> According to
> http://support.microsoft.com/default.aspx?scid=kb;en-us;271247 if any rows
> are longer than expected then additional characters appear wrapped in the
> DTS wizard, but are actually discarded.
> However, in article
> http://support.microsoft.com/default.aspx?scid=kb;en-us;247360 it
> mentions that DTS expects a fixed length file to have lines of fixed
> length, and having shorter lines will cause additional characters to be
> read from the next line.
> So the answer appears to be that in a fixed length import, make sure every
> line is the same length to avoid this problem.
>
Ok. Then we're out of luck then. I will contact the vendor if there will be
data for those columns in the future. If not, I can just delete it for now
to avoid the problem. It's just that MS Excel and Access support it. I don't
know why they didn't do that for DTS :(
Thanks.
Neil|||Neil,
I don't quite understand your explanation or the online example. You
say this is a fixed-width file, but the example you give online shows a
first line that is much longer than the second line. Fixed-width means
every line of the text file has the same length. Your file has lines of
different lengths, but it also doesn't have a separator character
between each column, so the wizard won't help you, and you'll need to do
something else, I guess.
Maybe one of these will work:
Import using BULK INSERT with a format file.
Preprocess the file with Unix-like utilities to add delimiters, then
import as delimited
Import the file into a staging table with one long column, then split
it up with
insert into FinalDestinationTable
select substring(s,1,4), substring(s,5,7), ...
Steve Kass
Drew University
Neil wrote:
>We have a textfile that we import in Excel(provided by our mainframe folks).
>It's fixed width with 142 columns. When I import it in excel or ms access,
>it gives me about ~34000 rows. But when I import using DTS package that is
>exported to Access mdb, rows becomes ~17000 rows :(
>And another hurdle that I'm faced is that there are rows that contains
>combined data such as street, city and state all together without spaces.
>Unfortunately, we can't modify the source text file. However, I do have a
>fieldmarker(save a .txt file) which I always use in Excel so that when I
>import it, I can select the area to create a vertical line just right that
>marker.
>Here is a sample of my fieldmarker.
>12345p1234567p12pp123456p
>Everytime i see a p, I click it with a mouse to create a vertical line in
>fixed width importing. In that case, there are 5 columns. These are all
>similar to ms access or excel.
>The bug.
>Please see this link below about the bug I found in MSSQL DTS Import wizard.
>It doesn't happen in Excel or MS Access. Excel and MS Access can handle it
>properly.
>http://restricted.dyndns.org/dtsimportissue.html
>Please help. Solution needed very badly!
>Thanks,
>Neil
>
>

Wednesday, March 28, 2012

I don't suppose BULK UPDATE exists?... like BULK INSERT?

I have to update a field within a table of 60 records or so. Each record has a different field value. it's type varchar. i was given an excel file with the field values and was thinking of a bulk update like bulk insert, but i don't recall that it's possible that way.

Is the only way to create a table, bulk insert, then merge the two tables together with UPDATE?

Just wanted to see if there was an easier way to do it, otherwise i'll take the latter route. Thanks!

You'll need to bulk insert into a work table, then do the update.

Unfortunately (or maybe, fortunately ) there's not Bulk Update.

Or, you could do the processing with SSIS....

I do want Collapsed Columns (+/-) to export in excel.

Hi,
I have a simple requirement, I do want to show columns in collapsed
mode(with +/-) when it is exported to excel.
i.e I have some groups in report and by default they are in collapsed mode,
so when we click on export to excel, data in excel also shows with +/- which
I don't want.
Any idea how this expected behaviour can be changed for export funtionality ?
--
SanjayIn a tricky way, you can create a copy of the same report with expanded items.
In your main report create an "Action" and put this report. name the box as
"Save as Excel" ofcourse you need to give in URL access.
Otherwise what you see is what you export.
Amarnath
"Sanjay" wrote:
> Hi,
> I have a simple requirement, I do want to show columns in collapsed
> mode(with +/-) when it is exported to excel.
> i.e I have some groups in report and by default they are in collapsed mode,
> so when we click on export to excel, data in excel also shows with +/- which
> I don't want.
> Any idea how this expected behaviour can be changed for export funtionality ?
> --
> Sanjay

Wednesday, March 21, 2012

I can't access cubes from excel

I try to register the dll in a remote machine but I couldn't.
Do I need to install something else in the remote machine?whats the message / error u r gett5ing. what exactly have u done?"|||The error is Load Library "C:\........................." failed
GetLastError returns 0x00000485
In the client I haven't installed anything. I only copied the dll and try to register it. Should I install something else?
Thanks in advance|||Does anyone has connected with Excel from other computer than the server?
From the server I can connect.
What whould I install in the computer to connect to the server with Excel?
Thanks in advance.|||

Before you can connect from Excel to the Olap 2005 server, you need to install Microsoft OLEDB for Olap 9.0.

The file you need to install is: pts9.msi - Located in
"En_SQL_DEV_x86_ctp_JUNE2005\Redist\Analysis Services\pts9.msi".

Best regards,

Jakobsgaard

|||Yes I have tried this with no luck.
I think is a version problem, my server is April CTP.
I'll try to install client tools in remote client.sql

Friday, March 9, 2012

I am Having an Odd Problem with Exporting to Excel.

The background:
Before I get into my error let me give you some background in what I am
required to do. All the text field parameters must be stored in the
database. What I mean by this is every text box's value, background
colour, font(weight, size and etc), TextAlign and TextDecoration
information is stored in the database. This includes the fields for
headers and footers. To get these parameters to work properly in
headers and footers I have set up report parameters that get the data
from the database and then feed it to the text fields inside the header
or footer.
The problem:
I am currently getting the following error while trying to export to
Excel:
--
Microsoft Internet Explorer
--
Internet Explorer cannot download Format=EXCEL from SERVERNAME.
Internet Explorer was not able to open this Internet site. The
requested site is either unavailable or cannot be found. Please try
again later.
--
OK
--
After some investigation I discovered that the appearance property
"TextAlign" for all footers is causing this error. So, if I put in
"Left", "Right" or "Center" text directly into the
"TextAlign" field for all the footer text boxes the report exports
into Excel properly. But if I use the property from the database it
will not load into Excel. I've checked to make sure the database
field is giving a valid value. In fact, I've tried all 3 values and
had no luck. I've also tried other TextAlign parameters from
different text fields on the report and received the same error as
stated above.
What I find odd about this is the fact it works fine for all the other
properties but TextAlign. Could this be an obscure bug?
Another thing to note is in Excel I can see the header all the time;
but, I can only see the footer when I am in print preview. Is there a
way to have the footer set up just like the header; so, it is just on
bottom of the page instead of being a "true" footer. It wouldn't
be a pretty way to solve my issue but I think it would at least allow
my clients to use Excel export for now.Oh I am using SQL Server 2000 Reporing Services with SP2.|||Hello!
I have encountered the same problem with export to Excel ("Internet Explorer
cannot download Format=EXCEL from SERVERNAME."). In my case the solution was
simple. I've had just to make the name of the report shorter. You can simply
upload your rdl under another (shorter) name to report manager and it will
possibly start working.
"Jeremy Balliston" wrote:
> Oh I am using SQL Server 2000 Reporing Services with SP2.
>|||Any ideas?

Friday, February 24, 2012

Hyperlink in Excel

Hi.

When creating a report builder and exporting to excel, the excel file keeps the hyperlinks. How can this be switched off ?

Many Thanks.

Sorry, hyperlinks are always included on all output formats. There isn't any way to turn them off for a particular renderer.

If you explain your scenario, we may consider it for a future release.|||We are having the same issue of clearing out the hyperlinks from excel sheet rendered using sql reporting services.

The scenario is once the report is generated in report viewer, we require the hyperlinks to navigate to other linked reports. But when we export the report by clicking on the export link available on report viewer, we want to remove the links in the excel worksheet.

When the export link is clicked on report viewer i do not have any exclusive control where in i could identify the click event of the export type as Excel selected from the drop down.

Thanks

Sups
|||I understand what is being asked, and would like to see it as a feature. I have many reports that link to other reports for drill-down. When view in the report viewer everything is great, however when exported the link is something like "http://reportserver/ReportName?parameters" which is not a valid URL. It would be nice if this was removed from excel so as not to confuse the end consumers of the report.

Hyperlink in Excel

Hi.

When creating a report builder and exporting to excel, the excel file keeps the hyperlinks. How can this be switched off ?

Many Thanks.

Sorry, hyperlinks are always included on all output formats. There isn't any way to turn them off for a particular renderer.

If you explain your scenario, we may consider it for a future release.