I need some urgent advice. I used Crystal Reports 4.6 (distributed with Visual Studio 6) and designed a report containing saved data. By default the report prints to a window (Crystal Report Preview Window) from where the users can select to print the report to their printers. I need to remove the export and mail options from the Preview Window.
I understand that the later, more recent versions, of Crystal Reports allows for the export and mail buttons to be hidden, what about the version I have? Due to the fact that Crystal Reports 4.6 apparently does not facilitate for this function I considered moving the report to MS Data Report, but it contains export abilities as well. I am more than prepared to use either of the 2 as long as I know that the information contained within the report cannot be tampered with by way of file exports.
Can anybody please help me with this problem?I don't know anything about version 4.6, but maybe there's a way that you can trap the Export button being pushed and warn the user, then exit the function before the report is exported?|||I tried trapping it from within VB, but to no avail.
Showing posts with label containing. Show all posts
Showing posts with label containing. Show all posts
Thursday, March 29, 2012
Tuesday, March 27, 2012
Exporting Japanese characters to PDF
When I export my report containing Japanese characters to PDF, the Japanese
text gets translated to a string of question marks ("? ? ? ?"). Yet the
Japanese characters display just fine in Visual Studio Preview, or when I
export the report to Excel, or when I execute the report's stored proc in
Query Analyzer. Is this a bug in the PDF translator?i have the same problem.help!
"MattGauch" <MattGauch@.discussions.microsoft.com> дÈëÏûÏ¢
news:921D902A-FEE0-4B7E-A1F1-F4E158D9DF3C@.microsoft.com...
> When I export my report containing Japanese characters to PDF, the
Japanese
> text gets translated to a string of question marks ("? ? ? ?"). Yet the
> Japanese characters display just fine in Visual Studio Preview, or when I
> export the report to Excel, or when I execute the report's stored proc in
> Query Analyzer. Is this a bug in the PDF translator?
>|||Try the report after you changed the fonts to "Arial Unicode MS" font.
Eralper
http://www.kodyaz.com
"news.microsoft.com" wrote:
> i have the same problem.help!
> "MattGauch" <MattGauch@.discussions.microsoft.com> �´�ë�û�¢
> news:921D902A-FEE0-4B7E-A1F1-F4E158D9DF3C@.microsoft.com...
> > When I export my report containing Japanese characters to PDF, the
> Japanese
> > text gets translated to a string of question marks ("? ? ? ?"). Yet the
> > Japanese characters display just fine in Visual Studio Preview, or when I
> > export the report to Excel, or when I execute the report's stored proc in
> > Query Analyzer. Is this a bug in the PDF translator?
> >
> >
>
>|||That did the trick - THANKS!! Still don't understand why it would export and
show up fine in Excel, however?
- Matt
"eralper" wrote:
> Try the report after you changed the fonts to "Arial Unicode MS" font.
> Eralper
> http://www.kodyaz.com
>
> "news.microsoft.com" wrote:
> > i have the same problem.help!
> > "MattGauch" <MattGauch@.discussions.microsoft.com> �´�ë�û�¢
> > news:921D902A-FEE0-4B7E-A1F1-F4E158D9DF3C@.microsoft.com...
> > > When I export my report containing Japanese characters to PDF, the
> > Japanese
> > > text gets translated to a string of question marks ("? ? ? ?"). Yet the
> > > Japanese characters display just fine in Visual Studio Preview, or when I
> > > export the report to Excel, or when I execute the report's stored proc in
> > > Query Analyzer. Is this a bug in the PDF translator?
> > >
> > >
> >
> >
> >|||I can not answer why it works on VS.Net preview but the Arial Unicode MS is a
very huge fiel about 3 MB in size so containing nearly all fonts in many
languages.
"MattGauch" wrote:
> That did the trick - THANKS!! Still don't understand why it would export and
> show up fine in Excel, however?
> - Matt
>
> "eralper" wrote:
> >
> > Try the report after you changed the fonts to "Arial Unicode MS" font.
> >
> > Eralper
> > http://www.kodyaz.com
> >
> >
> > "news.microsoft.com" wrote:
> >
> > > i have the same problem.help!
> > > "MattGauch" <MattGauch@.discussions.microsoft.com> �´�ë�û�¢
> > > news:921D902A-FEE0-4B7E-A1F1-F4E158D9DF3C@.microsoft.com...
> > > > When I export my report containing Japanese characters to PDF, the
> > > Japanese
> > > > text gets translated to a string of question marks ("? ? ? ?"). Yet the
> > > > Japanese characters display just fine in Visual Studio Preview, or when I
> > > > export the report to Excel, or when I execute the report's stored proc in
> > > > Query Analyzer. Is this a bug in the PDF translator?
> > > >
> > > >
> > >
> > >
> > >|||This can be a problem with Acrobat itself. RS doesn't embed fonts into
its PDF reports. (Probably, to avoid copyright violation issues
arising from redistributing fonts along with documents.) When
displaying such documents, Acrobat is tailored to substitute fonts,
based on fonts' characteristics, not name. If no match is found, it
uses some generic font, and, if that font doesn't contain the
characters used in the document, guess what it is going to display?
Right, a bunch of question marks...
On Thu, 3 Feb 2005 01:25:03 -0800, "eralper"
<eralper@.discussions.microsoft.com> wrote:
>I can not answer why it works on VS.Net preview but the Arial Unicode MS is a
>very huge fiel about 3 MB in size so containing nearly all fonts in many
>languages.
>"MattGauch" wrote:
>> That did the trick - THANKS!! Still don't understand why it would export and
>> show up fine in Excel, however?
>> - Matt
>>
>> "eralper" wrote:
>> >
>> > Try the report after you changed the fonts to "Arial Unicode MS" font.
>> >
>> > Eralper
>> > http://www.kodyaz.com
>> >
>> >
>> > "news.microsoft.com" wrote:
>> >
>> > > i have the same problem.help!
>> > > "MattGauch" <MattGauch@.discussions.microsoft.com> дÈëÏûÏ¢
>> > > news:921D902A-FEE0-4B7E-A1F1-F4E158D9DF3C@.microsoft.com...
>> > > > When I export my report containing Japanese characters to PDF, the
>> > > Japanese
>> > > > text gets translated to a string of question marks ("? ? ? ?"). Yet the
>> > > > Japanese characters display just fine in Visual Studio Preview, or when I
>> > > > export the report to Excel, or when I execute the report's stored proc in
>> > > > Query Analyzer. Is this a bug in the PDF translator?
>> > > >
>> > > >
>> > >
>> > >
>> > >|||I have similar problem. My barcode font (C39HrP36DmTt) gets converted to
somewhat like Arial on export to PDF or printing. Although in IE font is
displayed well.
I experimented with preinstalled Windows fonts like Blackadder ITC and Curlz
MT and got the same.
I have Reporting Services with SP 2. My font is installed on server.
Andrej.
"Usenet User" wrote:
> This can be a problem with Acrobat itself. RS doesn't embed fonts into
> its PDF reports. (Probably, to avoid copyright violation issues
> arising from redistributing fonts along with documents.) When
> displaying such documents, Acrobat is tailored to substitute fonts,
> based on fonts' characteristics, not name. If no match is found, it
> uses some generic font, and, if that font doesn't contain the
> characters used in the document, guess what it is going to display?
> Right, a bunch of question marks...
>
> On Thu, 3 Feb 2005 01:25:03 -0800, "eralper"
> <eralper@.discussions.microsoft.com> wrote:
> >I can not answer why it works on VS.Net preview but the Arial Unicode MS is a
> >very huge fiel about 3 MB in size so containing nearly all fonts in many
> >languages.
> >
> >"MattGauch" wrote:
> >
> >> That did the trick - THANKS!! Still don't understand why it would export and
> >> show up fine in Excel, however?
> >>
> >> - Matt
> >>
> >>
> >> "eralper" wrote:
> >>
> >> >
> >> > Try the report after you changed the fonts to "Arial Unicode MS" font.
> >> >
> >> > Eralper
> >> > http://www.kodyaz.com
> >> >
> >> >
> >> > "news.microsoft.com" wrote:
> >> >
> >> > > i have the same problem.help!
> >> > > "MattGauch" <MattGauch@.discussions.microsoft.com> �´�ë�û�¢
> >> > > news:921D902A-FEE0-4B7E-A1F1-F4E158D9DF3C@.microsoft.com...
> >> > > > When I export my report containing Japanese characters to PDF, the
> >> > > Japanese
> >> > > > text gets translated to a string of question marks ("? ? ? ?"). Yet the
> >> > > > Japanese characters display just fine in Visual Studio Preview, or when I
> >> > > > export the report to Excel, or when I execute the report's stored proc in
> >> > > > Query Analyzer. Is this a bug in the PDF translator?
> >> > > >
> >> > > >
> >> > >
> >> > >
> >> > >
>|||Arial Unicode MS won't always work. In order to enable Japanese for
non-unicode programs (PDF), see the following url:
http://www.greggman.com/japan/xp-ime/xp-ime.htm.
"Andrej" wrote:
> I have similar problem. My barcode font (C39HrP36DmTt) gets converted to
> somewhat like Arial on export to PDF or printing. Although in IE font is
> displayed well.
> I experimented with preinstalled Windows fonts like Blackadder ITC and Curlz
> MT and got the same.
> I have Reporting Services with SP 2. My font is installed on server.
> Andrej.
>
>
> "Usenet User" wrote:
> > This can be a problem with Acrobat itself. RS doesn't embed fonts into
> > its PDF reports. (Probably, to avoid copyright violation issues
> > arising from redistributing fonts along with documents.) When
> > displaying such documents, Acrobat is tailored to substitute fonts,
> > based on fonts' characteristics, not name. If no match is found, it
> > uses some generic font, and, if that font doesn't contain the
> > characters used in the document, guess what it is going to display?
> > Right, a bunch of question marks...
> >
> >
> > On Thu, 3 Feb 2005 01:25:03 -0800, "eralper"
> > <eralper@.discussions.microsoft.com> wrote:
> >
> > >I can not answer why it works on VS.Net preview but the Arial Unicode MS is a
> > >very huge fiel about 3 MB in size so containing nearly all fonts in many
> > >languages.
> > >
> > >"MattGauch" wrote:
> > >
> > >> That did the trick - THANKS!! Still don't understand why it would export and
> > >> show up fine in Excel, however?
> > >>
> > >> - Matt
> > >>
> > >>
> > >> "eralper" wrote:
> > >>
> > >> >
> > >> > Try the report after you changed the fonts to "Arial Unicode MS" font.
> > >> >
> > >> > Eralper
> > >> > http://www.kodyaz.com
> > >> >
> > >> >
> > >> > "news.microsoft.com" wrote:
> > >> >
> > >> > > i have the same problem.help!
> > >> > > "MattGauch" <MattGauch@.discussions.microsoft.com> �´�ë�û�¢
> > >> > > news:921D902A-FEE0-4B7E-A1F1-F4E158D9DF3C@.microsoft.com...
> > >> > > > When I export my report containing Japanese characters to PDF, the
> > >> > > Japanese
> > >> > > > text gets translated to a string of question marks ("? ? ? ?"). Yet the
> > >> > > > Japanese characters display just fine in Visual Studio Preview, or when I
> > >> > > > export the report to Excel, or when I execute the report's stored proc in
> > >> > > > Query Analyzer. Is this a bug in the PDF translator?
> > >> > > >
> > >> > > >
> > >> > >
> > >> > >
> > >> > >
> >
> >
text gets translated to a string of question marks ("? ? ? ?"). Yet the
Japanese characters display just fine in Visual Studio Preview, or when I
export the report to Excel, or when I execute the report's stored proc in
Query Analyzer. Is this a bug in the PDF translator?i have the same problem.help!
"MattGauch" <MattGauch@.discussions.microsoft.com> дÈëÏûÏ¢
news:921D902A-FEE0-4B7E-A1F1-F4E158D9DF3C@.microsoft.com...
> When I export my report containing Japanese characters to PDF, the
Japanese
> text gets translated to a string of question marks ("? ? ? ?"). Yet the
> Japanese characters display just fine in Visual Studio Preview, or when I
> export the report to Excel, or when I execute the report's stored proc in
> Query Analyzer. Is this a bug in the PDF translator?
>|||Try the report after you changed the fonts to "Arial Unicode MS" font.
Eralper
http://www.kodyaz.com
"news.microsoft.com" wrote:
> i have the same problem.help!
> "MattGauch" <MattGauch@.discussions.microsoft.com> �´�ë�û�¢
> news:921D902A-FEE0-4B7E-A1F1-F4E158D9DF3C@.microsoft.com...
> > When I export my report containing Japanese characters to PDF, the
> Japanese
> > text gets translated to a string of question marks ("? ? ? ?"). Yet the
> > Japanese characters display just fine in Visual Studio Preview, or when I
> > export the report to Excel, or when I execute the report's stored proc in
> > Query Analyzer. Is this a bug in the PDF translator?
> >
> >
>
>|||That did the trick - THANKS!! Still don't understand why it would export and
show up fine in Excel, however?
- Matt
"eralper" wrote:
> Try the report after you changed the fonts to "Arial Unicode MS" font.
> Eralper
> http://www.kodyaz.com
>
> "news.microsoft.com" wrote:
> > i have the same problem.help!
> > "MattGauch" <MattGauch@.discussions.microsoft.com> �´�ë�û�¢
> > news:921D902A-FEE0-4B7E-A1F1-F4E158D9DF3C@.microsoft.com...
> > > When I export my report containing Japanese characters to PDF, the
> > Japanese
> > > text gets translated to a string of question marks ("? ? ? ?"). Yet the
> > > Japanese characters display just fine in Visual Studio Preview, or when I
> > > export the report to Excel, or when I execute the report's stored proc in
> > > Query Analyzer. Is this a bug in the PDF translator?
> > >
> > >
> >
> >
> >|||I can not answer why it works on VS.Net preview but the Arial Unicode MS is a
very huge fiel about 3 MB in size so containing nearly all fonts in many
languages.
"MattGauch" wrote:
> That did the trick - THANKS!! Still don't understand why it would export and
> show up fine in Excel, however?
> - Matt
>
> "eralper" wrote:
> >
> > Try the report after you changed the fonts to "Arial Unicode MS" font.
> >
> > Eralper
> > http://www.kodyaz.com
> >
> >
> > "news.microsoft.com" wrote:
> >
> > > i have the same problem.help!
> > > "MattGauch" <MattGauch@.discussions.microsoft.com> �´�ë�û�¢
> > > news:921D902A-FEE0-4B7E-A1F1-F4E158D9DF3C@.microsoft.com...
> > > > When I export my report containing Japanese characters to PDF, the
> > > Japanese
> > > > text gets translated to a string of question marks ("? ? ? ?"). Yet the
> > > > Japanese characters display just fine in Visual Studio Preview, or when I
> > > > export the report to Excel, or when I execute the report's stored proc in
> > > > Query Analyzer. Is this a bug in the PDF translator?
> > > >
> > > >
> > >
> > >
> > >|||This can be a problem with Acrobat itself. RS doesn't embed fonts into
its PDF reports. (Probably, to avoid copyright violation issues
arising from redistributing fonts along with documents.) When
displaying such documents, Acrobat is tailored to substitute fonts,
based on fonts' characteristics, not name. If no match is found, it
uses some generic font, and, if that font doesn't contain the
characters used in the document, guess what it is going to display?
Right, a bunch of question marks...
On Thu, 3 Feb 2005 01:25:03 -0800, "eralper"
<eralper@.discussions.microsoft.com> wrote:
>I can not answer why it works on VS.Net preview but the Arial Unicode MS is a
>very huge fiel about 3 MB in size so containing nearly all fonts in many
>languages.
>"MattGauch" wrote:
>> That did the trick - THANKS!! Still don't understand why it would export and
>> show up fine in Excel, however?
>> - Matt
>>
>> "eralper" wrote:
>> >
>> > Try the report after you changed the fonts to "Arial Unicode MS" font.
>> >
>> > Eralper
>> > http://www.kodyaz.com
>> >
>> >
>> > "news.microsoft.com" wrote:
>> >
>> > > i have the same problem.help!
>> > > "MattGauch" <MattGauch@.discussions.microsoft.com> дÈëÏûÏ¢
>> > > news:921D902A-FEE0-4B7E-A1F1-F4E158D9DF3C@.microsoft.com...
>> > > > When I export my report containing Japanese characters to PDF, the
>> > > Japanese
>> > > > text gets translated to a string of question marks ("? ? ? ?"). Yet the
>> > > > Japanese characters display just fine in Visual Studio Preview, or when I
>> > > > export the report to Excel, or when I execute the report's stored proc in
>> > > > Query Analyzer. Is this a bug in the PDF translator?
>> > > >
>> > > >
>> > >
>> > >
>> > >|||I have similar problem. My barcode font (C39HrP36DmTt) gets converted to
somewhat like Arial on export to PDF or printing. Although in IE font is
displayed well.
I experimented with preinstalled Windows fonts like Blackadder ITC and Curlz
MT and got the same.
I have Reporting Services with SP 2. My font is installed on server.
Andrej.
"Usenet User" wrote:
> This can be a problem with Acrobat itself. RS doesn't embed fonts into
> its PDF reports. (Probably, to avoid copyright violation issues
> arising from redistributing fonts along with documents.) When
> displaying such documents, Acrobat is tailored to substitute fonts,
> based on fonts' characteristics, not name. If no match is found, it
> uses some generic font, and, if that font doesn't contain the
> characters used in the document, guess what it is going to display?
> Right, a bunch of question marks...
>
> On Thu, 3 Feb 2005 01:25:03 -0800, "eralper"
> <eralper@.discussions.microsoft.com> wrote:
> >I can not answer why it works on VS.Net preview but the Arial Unicode MS is a
> >very huge fiel about 3 MB in size so containing nearly all fonts in many
> >languages.
> >
> >"MattGauch" wrote:
> >
> >> That did the trick - THANKS!! Still don't understand why it would export and
> >> show up fine in Excel, however?
> >>
> >> - Matt
> >>
> >>
> >> "eralper" wrote:
> >>
> >> >
> >> > Try the report after you changed the fonts to "Arial Unicode MS" font.
> >> >
> >> > Eralper
> >> > http://www.kodyaz.com
> >> >
> >> >
> >> > "news.microsoft.com" wrote:
> >> >
> >> > > i have the same problem.help!
> >> > > "MattGauch" <MattGauch@.discussions.microsoft.com> �´�ë�û�¢
> >> > > news:921D902A-FEE0-4B7E-A1F1-F4E158D9DF3C@.microsoft.com...
> >> > > > When I export my report containing Japanese characters to PDF, the
> >> > > Japanese
> >> > > > text gets translated to a string of question marks ("? ? ? ?"). Yet the
> >> > > > Japanese characters display just fine in Visual Studio Preview, or when I
> >> > > > export the report to Excel, or when I execute the report's stored proc in
> >> > > > Query Analyzer. Is this a bug in the PDF translator?
> >> > > >
> >> > > >
> >> > >
> >> > >
> >> > >
>|||Arial Unicode MS won't always work. In order to enable Japanese for
non-unicode programs (PDF), see the following url:
http://www.greggman.com/japan/xp-ime/xp-ime.htm.
"Andrej" wrote:
> I have similar problem. My barcode font (C39HrP36DmTt) gets converted to
> somewhat like Arial on export to PDF or printing. Although in IE font is
> displayed well.
> I experimented with preinstalled Windows fonts like Blackadder ITC and Curlz
> MT and got the same.
> I have Reporting Services with SP 2. My font is installed on server.
> Andrej.
>
>
> "Usenet User" wrote:
> > This can be a problem with Acrobat itself. RS doesn't embed fonts into
> > its PDF reports. (Probably, to avoid copyright violation issues
> > arising from redistributing fonts along with documents.) When
> > displaying such documents, Acrobat is tailored to substitute fonts,
> > based on fonts' characteristics, not name. If no match is found, it
> > uses some generic font, and, if that font doesn't contain the
> > characters used in the document, guess what it is going to display?
> > Right, a bunch of question marks...
> >
> >
> > On Thu, 3 Feb 2005 01:25:03 -0800, "eralper"
> > <eralper@.discussions.microsoft.com> wrote:
> >
> > >I can not answer why it works on VS.Net preview but the Arial Unicode MS is a
> > >very huge fiel about 3 MB in size so containing nearly all fonts in many
> > >languages.
> > >
> > >"MattGauch" wrote:
> > >
> > >> That did the trick - THANKS!! Still don't understand why it would export and
> > >> show up fine in Excel, however?
> > >>
> > >> - Matt
> > >>
> > >>
> > >> "eralper" wrote:
> > >>
> > >> >
> > >> > Try the report after you changed the fonts to "Arial Unicode MS" font.
> > >> >
> > >> > Eralper
> > >> > http://www.kodyaz.com
> > >> >
> > >> >
> > >> > "news.microsoft.com" wrote:
> > >> >
> > >> > > i have the same problem.help!
> > >> > > "MattGauch" <MattGauch@.discussions.microsoft.com> �´�ë�û�¢
> > >> > > news:921D902A-FEE0-4B7E-A1F1-F4E158D9DF3C@.microsoft.com...
> > >> > > > When I export my report containing Japanese characters to PDF, the
> > >> > > Japanese
> > >> > > > text gets translated to a string of question marks ("? ? ? ?"). Yet the
> > >> > > > Japanese characters display just fine in Visual Studio Preview, or when I
> > >> > > > export the report to Excel, or when I execute the report's stored proc in
> > >> > > > Query Analyzer. Is this a bug in the PDF translator?
> > >> > > >
> > >> > > >
> > >> > >
> > >> > >
> > >> > >
> >
> >
Exporting embedded images to PDF
Hi,
we experience problems whenever we try to export reports containing images
to a PDF-document. As far as we found out, this issue occurs only with images
set to 256 colours (8 bpp). Images set to 16.7 m pixels do not cause any
problems. Due to the fact that this is a mayor issue for our company weâ'd
like to know whether this problem will be fixed soon. Converting all images
to high colour is not a feasible workaround for us.
Regards,
Carsten Schlotmann
Informationstechnik & eBusiness
A. F. Dornbracht GmbH & Co. KGYou should report this as a bug... Then you can see the status...
http://lab.msdn.microsoft.com/productfeedback/default.aspx
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
I support the Professional Association for SQL Server ( PASS) and it''s
community of SQL Professionals.
"Markus Behde" wrote:
> Hi,
> we experience problems whenever we try to export reports containing images
> to a PDF-document. As far as we found out, this issue occurs only with images
> set to 256 colours (8 bpp). Images set to 16.7 m pixels do not cause any
> problems. Due to the fact that this is a mayor issue for our company weâ'd
> like to know whether this problem will be fixed soon. Converting all images
> to high colour is not a feasible workaround for us.
> Regards,
> Carsten Schlotmann
> Informationstechnik & eBusiness
> A. F. Dornbracht GmbH & Co. KG|||Sorry, but it's a problem on SQL Server 2000 with Reporting Services SP2 and
at the Product Feedback Center I can only report bugs for SQL Server 2005!
"Wayne Snyder" wrote:
> You should report this as a bug... Then you can see the status...
> http://lab.msdn.microsoft.com/productfeedback/default.aspx
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> I support the Professional Association for SQL Server ( PASS) and it''s
> community of SQL Professionals.
>
> "Markus Behde" wrote:
> > Hi,
> >
> > we experience problems whenever we try to export reports containing images
> > to a PDF-document. As far as we found out, this issue occurs only with images
> > set to 256 colours (8 bpp). Images set to 16.7 m pixels do not cause any
> > problems. Due to the fact that this is a mayor issue for our company weâ'd
> > like to know whether this problem will be fixed soon. Converting all images
> > to high colour is not a feasible workaround for us.
> >
> > Regards,
> >
> > Carsten Schlotmann
> > Informationstechnik & eBusiness
> >
> > A. F. Dornbracht GmbH & Co. KG|||Hi Carsten,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood you encounter problems when rendering
256 color images to PDF format. If I have misunderstood your concern,
please feel free to point it out.
I have generated a 256 colors bmp file with mspaint and inserted it into my
report as Embeded image. The rendered pdf file looks as expected.
You may send the sample files/solution based on sample database
AdventureWorks within a zipped package to me. My direct email address is
v-mingqc@.online.microsoft.com (make sure to REMOVE "online" before you
click SEND as "online" is only for SPAM), you may send the file to me
directly and I will keep secure.
You may also contact Microsoft Customer Service and Support and open a
support incident and work with a dedicated Support Professional.
Please be advised that contacting phone support will be a charged call.
However, if you are simply requesting a hotfix be sent to you and no other
support then charges are usually refunded or waived. if this turned out to
be a known issue/bug in our product, you will also be refunded or waived.
To obtain the phone numbers for specific technology request please take a
look at the web site listed below.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
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 Carsten,
Thanks for your email and sample.
This was confirmed to be a known issue and will be fixed in Reporting
Services 2005 Service Pack 1.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
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.
we experience problems whenever we try to export reports containing images
to a PDF-document. As far as we found out, this issue occurs only with images
set to 256 colours (8 bpp). Images set to 16.7 m pixels do not cause any
problems. Due to the fact that this is a mayor issue for our company weâ'd
like to know whether this problem will be fixed soon. Converting all images
to high colour is not a feasible workaround for us.
Regards,
Carsten Schlotmann
Informationstechnik & eBusiness
A. F. Dornbracht GmbH & Co. KGYou should report this as a bug... Then you can see the status...
http://lab.msdn.microsoft.com/productfeedback/default.aspx
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
I support the Professional Association for SQL Server ( PASS) and it''s
community of SQL Professionals.
"Markus Behde" wrote:
> Hi,
> we experience problems whenever we try to export reports containing images
> to a PDF-document. As far as we found out, this issue occurs only with images
> set to 256 colours (8 bpp). Images set to 16.7 m pixels do not cause any
> problems. Due to the fact that this is a mayor issue for our company weâ'd
> like to know whether this problem will be fixed soon. Converting all images
> to high colour is not a feasible workaround for us.
> Regards,
> Carsten Schlotmann
> Informationstechnik & eBusiness
> A. F. Dornbracht GmbH & Co. KG|||Sorry, but it's a problem on SQL Server 2000 with Reporting Services SP2 and
at the Product Feedback Center I can only report bugs for SQL Server 2005!
"Wayne Snyder" wrote:
> You should report this as a bug... Then you can see the status...
> http://lab.msdn.microsoft.com/productfeedback/default.aspx
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> I support the Professional Association for SQL Server ( PASS) and it''s
> community of SQL Professionals.
>
> "Markus Behde" wrote:
> > Hi,
> >
> > we experience problems whenever we try to export reports containing images
> > to a PDF-document. As far as we found out, this issue occurs only with images
> > set to 256 colours (8 bpp). Images set to 16.7 m pixels do not cause any
> > problems. Due to the fact that this is a mayor issue for our company weâ'd
> > like to know whether this problem will be fixed soon. Converting all images
> > to high colour is not a feasible workaround for us.
> >
> > Regards,
> >
> > Carsten Schlotmann
> > Informationstechnik & eBusiness
> >
> > A. F. Dornbracht GmbH & Co. KG|||Hi Carsten,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood you encounter problems when rendering
256 color images to PDF format. If I have misunderstood your concern,
please feel free to point it out.
I have generated a 256 colors bmp file with mspaint and inserted it into my
report as Embeded image. The rendered pdf file looks as expected.
You may send the sample files/solution based on sample database
AdventureWorks within a zipped package to me. My direct email address is
v-mingqc@.online.microsoft.com (make sure to REMOVE "online" before you
click SEND as "online" is only for SPAM), you may send the file to me
directly and I will keep secure.
You may also contact Microsoft Customer Service and Support and open a
support incident and work with a dedicated Support Professional.
Please be advised that contacting phone support will be a charged call.
However, if you are simply requesting a hotfix be sent to you and no other
support then charges are usually refunded or waived. if this turned out to
be a known issue/bug in our product, you will also be refunded or waived.
To obtain the phone numbers for specific technology request please take a
look at the web site listed below.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
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 Carsten,
Thanks for your email and sample.
This was confirmed to be a known issue and will be fixed in Reporting
Services 2005 Service Pack 1.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
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.
Sunday, March 11, 2012
Export to PDF/TIFF
When I try to export to PDF or TIFF the report seems to give me 1 page then
2 pages only containing the page header and page footer then the next page
followed by 2 pages with only header and footer and so forth.
We have just installed SP1 which did not fix this problem.
Another issue not fixed by SP1 is that we use a specific font which is
installed on both server and client that shows as a different font on the
PDF export however is fine on every other export.
Any ideas?
Regards
JonasHmm Sorry please disregard the header/footer page bit. However the font
issue is still an issue.
Regards
Jonas
"Jonas Larsen" <Jonas.Larsen@.Alcan.com> wrote in message
news:e67RXWKXEHA.1128@.TK2MSFTNGP10.phx.gbl...
> When I try to export to PDF or TIFF the report seems to give me 1 page
then
> 2 pages only containing the page header and page footer then the next page
> followed by 2 pages with only header and footer and so forth.
> We have just installed SP1 which did not fix this problem.
> Another issue not fixed by SP1 is that we use a specific font which is
> installed on both server and client that shows as a different font on the
> PDF export however is fine on every other export.
> Any ideas?
> Regards
> Jonas
>|||Can you give a specific example of the font issue? Is it a True Type font?
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jonas Larsen" <Jonas.Larsen@.Alcan.com> wrote in message
news:u8KyQNLXEHA.2816@.TK2MSFTNGP11.phx.gbl...
> Hmm Sorry please disregard the header/footer page bit. However the font
> issue is still an issue.
> Regards
> Jonas
> "Jonas Larsen" <Jonas.Larsen@.Alcan.com> wrote in message
> news:e67RXWKXEHA.1128@.TK2MSFTNGP10.phx.gbl...
>> When I try to export to PDF or TIFF the report seems to give me 1 page
> then
>> 2 pages only containing the page header and page footer then the next
>> page
>> followed by 2 pages with only header and footer and so forth.
>> We have just installed SP1 which did not fix this problem.
>> Another issue not fixed by SP1 is that we use a specific font which is
>> installed on both server and client that shows as a different font on the
>> PDF export however is fine on every other export.
>> Any ideas?
>> Regards
>> Jonas
>>
>|||This is a multi-part message in MIME format.
--=_NextPart_000_00A2_01C45D31.67ADF190
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Seems like the file was blocked but:
A is what it should look like but it looks like A in the PDF Export =where as it look fine before the export. Again we have installed SP1 and =the font is available on both server & client.
Regards
Jonas
"Jonas Larsen" <Jonas.Larsen@.Alcan.com> wrote in message =news:ueda9cNXEHA.4032@.TK2MSFTNGP11.phx.gbl...
Yes it is a true type font. My conmpay have their logo as a font but =once
exported to PDF it shows as a normal font. Where as it comes up ok in =eg
Excel.
From the Document Properties in Acrobat Reader it says
Type: True Type
Encoding: Ansi
Actual Font: Adibe Sans MM
In the attached file is how it looks once exported to pdf and how is =looks
before export.
Regards
Jonas
"Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in =message
news:uQVTQyMXEHA.1684@.tk2msftngp13.phx.gbl...
> Can you give a specific example of the font issue? Is it a True Type =font?
>
> -- > Brian Welcker
> Group Program Manager
> SQL Server Reporting Services
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Jonas Larsen" <Jonas.Larsen@.Alcan.com> wrote in message
> news:u8KyQNLXEHA.2816@.TK2MSFTNGP11.phx.gbl...
> > Hmm Sorry please disregard the header/footer page bit. However the =font
> > issue is still an issue.
> >
> > Regards
> > Jonas
> > "Jonas Larsen" <Jonas.Larsen@.Alcan.com> wrote in message
> > news:e67RXWKXEHA.1128@.TK2MSFTNGP10.phx.gbl...
> >> When I try to export to PDF or TIFF the report seems to give me 1 =page
> > then
> >> 2 pages only containing the page header and page footer then the =next
> >> page
> >> followed by 2 pages with only header and footer and so forth.
> >> We have just installed SP1 which did not fix this problem.
> >>
> >> Another issue not fixed by SP1 is that we use a specific font =which is
> >> installed on both server and client that shows as a different =font on
the
> >> PDF export however is fine on every other export.
> >>
> >> Any ideas?
> >>
> >> Regards
> >> Jonas
> >>
> >>
> >
> >
>
>
--=_NextPart_000_00A2_01C45D31.67ADF190
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Seems like the file was blocked =but:
A is =what it should look like but it looks like A in the PDF Export =where as it look fine before the export. Again we have installed SP1 and the font is =available on both server & client.
Regards
Jonas
"Jonas Larsen" =wrote in message news:ueda9cNXEHA.4032=@.TK2MSFTNGP11.phx.gbl...Yes it is a true type font. My conmpay have their logo as a font but onceexported to PDF it shows as a normal font. Where as it comes =up ok in egExcel.From the Document Properties in Acrobat Reader it says Type: True Type =Encoding: Ansi Actual Font: Adibe Sans MMIn the =attached file is how it looks once exported to pdf and how is looksbefore export.RegardsJonas"Brian Welcker [MSFT]" wrote in messagenews:uQVTQyMXEHA.1684@.tk2msftngp13.phx.gbl...> Can =you give a specific example of the font issue? Is it a True Type =font?>> -- > Brian Welcker> Group Program Manager> SQL =Server Reporting Services>> This posting is provided "AS IS" =with no warranties, and confers norights.>> "Jonas Larsen" wrote in message> news:u8KyQNLXEHA.2816@.TK2MSFTNGP11.phx.gbl...> > Hmm Sorry =please disregard the header/footer page bit. However the font> > =issue is still an issue.> >> > Regards> > =Jonas> > "Jonas Larsen" wrote in =message> > news:e67RXWKXEHA.1128@.TK2MSFTNGP10.phx.gbl...> >> =When I try to export to PDF or TIFF the report seems to give me 1 page> => then> >> 2 pages only containing the page header and page =footer then the next> >> page> >> followed by 2 =pages with only header and footer and so forth.> >> We have just =installed SP1 which did not fix this problem.> >>> >> =Another issue not fixed by SP1 is that we use a specific font which is> = >> installed on both server and client that shows as a different =font onthe> >> PDF export however is fine on every other export.> >>> >> Any ideas?> =>>> >> Regards> >> Jonas> >>> >>> >> >>>
--=_NextPart_000_00A2_01C45D31.67ADF190--|||This is a multi-part message in MIME format.
--=_NextPart_000_0297_01C45DAF.830CCA50
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Can you send me the font and the report directly? My address is =bwelcker@.microsoft.com. The only workaround I can think of for now is to =use an image.
-- Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no =rights.
"Jonas Larsen" <Jonas.Larsen@.Alcan.com> wrote in message =news:OWSTV3NXEHA.2716@.tk2msftngp13.phx.gbl...
Seems like the file was blocked but:
A is what it should look like but it looks like A in the PDF Export =where as it look fine before the export. Again we have installed SP1 and =the font is available on both server & client.
Regards
Jonas
"Jonas Larsen" <Jonas.Larsen@.Alcan.com> wrote in message =news:ueda9cNXEHA.4032@.TK2MSFTNGP11.phx.gbl...
Yes it is a true type font. My conmpay have their logo as a font but =once
exported to PDF it shows as a normal font. Where as it comes up ok =in eg
Excel.
From the Document Properties in Acrobat Reader it says
Type: True Type
Encoding: Ansi
Actual Font: Adibe Sans MM
In the attached file is how it looks once exported to pdf and how is =looks
before export.
Regards
Jonas
"Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in =message
news:uQVTQyMXEHA.1684@.tk2msftngp13.phx.gbl...
> Can you give a specific example of the font issue? Is it a True =Type font?
>
> -- > Brian Welcker
> Group Program Manager
> SQL Server Reporting Services
>
> This posting is provided "AS IS" with no warranties, and confers =no
rights.
>
> "Jonas Larsen" <Jonas.Larsen@.Alcan.com> wrote in message
> news:u8KyQNLXEHA.2816@.TK2MSFTNGP11.phx.gbl...
> > Hmm Sorry please disregard the header/footer page bit. However =the font
> > issue is still an issue.
> >
> > Regards
> > Jonas
> > "Jonas Larsen" <Jonas.Larsen@.Alcan.com> wrote in message
> > news:e67RXWKXEHA.1128@.TK2MSFTNGP10.phx.gbl...
> >> When I try to export to PDF or TIFF the report seems to give me =1 page
> > then
> >> 2 pages only containing the page header and page footer then =the next
> >> page
> >> followed by 2 pages with only header and footer and so forth.
> >> We have just installed SP1 which did not fix this problem.
> >>
> >> Another issue not fixed by SP1 is that we use a specific font =which is
> >> installed on both server and client that shows as a different =font on
the
> >> PDF export however is fine on every other export.
> >>
> >> Any ideas?
> >>
> >> Regards
> >> Jonas
> >>
> >>
> >
> >
>
>
--=_NextPart_000_0297_01C45DAF.830CCA50
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Can you send me the font and the report =directly? My address is bwelcker@.microsoft.com. T=he only workaround I can think of for now is to use an image.
-- Brian WelckerGroup Program ManagerSQL Server =Reporting Services
This posting is provided "AS IS" with no warranties, and confers no =rights.
"Jonas Larsen" =wrote in message news:OWSTV3NXEHA.2716=@.tk2msftngp13.phx.gbl...
Seems like the file was blocked =but:
A is what it should look like but it looks like A in the PDF Export =where as it look fine before the export. Again we have installed SP1 and the =font is available on both server & client.
Regards
Jonas
"Jonas Larsen" =wrote in message news:ueda9cNXEHA.4032=@.TK2MSFTNGP11.phx.gbl...Yes it is a true type font. My conmpay have their logo as a font but onceexported to PDF it shows as a normal font. Where as it comes =up ok in egExcel.From the Document Properties in Acrobat =Reader it says Type: True Type =Encoding: Ansi Actual Font: Adibe Sans MMIn the =attached file is how it looks once exported to pdf and how is looksbefore = export.RegardsJonas"Brian Welcker [MSFT]" wrote in messagenews:uQVTQyMXEHA.1684@.tk2msftngp13.phx.gbl...> Can =you give a specific example of the font issue? Is it a True Type font?>> -- > Brian Welcker> Group =Program Manager> SQL Server Reporting Services>> This =posting is provided "AS IS" with no warranties, and confers norights.>> "Jonas Larsen" = wrote in message> news:u8KyQNLXEHA.2816@.TK2MSFTNGP11.phx.gbl...> > Hmm Sorry =please disregard the header/footer page bit. However the font> > =issue is still an issue.> >> > Regards> > =Jonas> > "Jonas Larsen" wrote in =message> > news:e67RXWKXEHA.1128@.TK2MSFTNGP10.phx.gbl...> >> =When I try to export to PDF or TIFF the report seems to give me 1 =page> > then> >> 2 pages only containing the page header and =page footer then the next> >> page> >> followed =by 2 pages with only header and footer and so forth.> >> We =have just installed SP1 which did not fix this problem.> =>>> >> Another issue not fixed by SP1 is that we use a specific =font which is> >> installed on both server and client that shows =as a different font onthe> >> PDF export however is fine =on every other export.> >>> >> Any =ideas?> >>> >> Regards> >> Jonas> >>> >>> >> =>>>=
--=_NextPart_000_0297_01C45DAF.830CCA50--
2 pages only containing the page header and page footer then the next page
followed by 2 pages with only header and footer and so forth.
We have just installed SP1 which did not fix this problem.
Another issue not fixed by SP1 is that we use a specific font which is
installed on both server and client that shows as a different font on the
PDF export however is fine on every other export.
Any ideas?
Regards
JonasHmm Sorry please disregard the header/footer page bit. However the font
issue is still an issue.
Regards
Jonas
"Jonas Larsen" <Jonas.Larsen@.Alcan.com> wrote in message
news:e67RXWKXEHA.1128@.TK2MSFTNGP10.phx.gbl...
> When I try to export to PDF or TIFF the report seems to give me 1 page
then
> 2 pages only containing the page header and page footer then the next page
> followed by 2 pages with only header and footer and so forth.
> We have just installed SP1 which did not fix this problem.
> Another issue not fixed by SP1 is that we use a specific font which is
> installed on both server and client that shows as a different font on the
> PDF export however is fine on every other export.
> Any ideas?
> Regards
> Jonas
>|||Can you give a specific example of the font issue? Is it a True Type font?
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jonas Larsen" <Jonas.Larsen@.Alcan.com> wrote in message
news:u8KyQNLXEHA.2816@.TK2MSFTNGP11.phx.gbl...
> Hmm Sorry please disregard the header/footer page bit. However the font
> issue is still an issue.
> Regards
> Jonas
> "Jonas Larsen" <Jonas.Larsen@.Alcan.com> wrote in message
> news:e67RXWKXEHA.1128@.TK2MSFTNGP10.phx.gbl...
>> When I try to export to PDF or TIFF the report seems to give me 1 page
> then
>> 2 pages only containing the page header and page footer then the next
>> page
>> followed by 2 pages with only header and footer and so forth.
>> We have just installed SP1 which did not fix this problem.
>> Another issue not fixed by SP1 is that we use a specific font which is
>> installed on both server and client that shows as a different font on the
>> PDF export however is fine on every other export.
>> Any ideas?
>> Regards
>> Jonas
>>
>|||This is a multi-part message in MIME format.
--=_NextPart_000_00A2_01C45D31.67ADF190
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Seems like the file was blocked but:
A is what it should look like but it looks like A in the PDF Export =where as it look fine before the export. Again we have installed SP1 and =the font is available on both server & client.
Regards
Jonas
"Jonas Larsen" <Jonas.Larsen@.Alcan.com> wrote in message =news:ueda9cNXEHA.4032@.TK2MSFTNGP11.phx.gbl...
Yes it is a true type font. My conmpay have their logo as a font but =once
exported to PDF it shows as a normal font. Where as it comes up ok in =eg
Excel.
From the Document Properties in Acrobat Reader it says
Type: True Type
Encoding: Ansi
Actual Font: Adibe Sans MM
In the attached file is how it looks once exported to pdf and how is =looks
before export.
Regards
Jonas
"Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in =message
news:uQVTQyMXEHA.1684@.tk2msftngp13.phx.gbl...
> Can you give a specific example of the font issue? Is it a True Type =font?
>
> -- > Brian Welcker
> Group Program Manager
> SQL Server Reporting Services
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Jonas Larsen" <Jonas.Larsen@.Alcan.com> wrote in message
> news:u8KyQNLXEHA.2816@.TK2MSFTNGP11.phx.gbl...
> > Hmm Sorry please disregard the header/footer page bit. However the =font
> > issue is still an issue.
> >
> > Regards
> > Jonas
> > "Jonas Larsen" <Jonas.Larsen@.Alcan.com> wrote in message
> > news:e67RXWKXEHA.1128@.TK2MSFTNGP10.phx.gbl...
> >> When I try to export to PDF or TIFF the report seems to give me 1 =page
> > then
> >> 2 pages only containing the page header and page footer then the =next
> >> page
> >> followed by 2 pages with only header and footer and so forth.
> >> We have just installed SP1 which did not fix this problem.
> >>
> >> Another issue not fixed by SP1 is that we use a specific font =which is
> >> installed on both server and client that shows as a different =font on
the
> >> PDF export however is fine on every other export.
> >>
> >> Any ideas?
> >>
> >> Regards
> >> Jonas
> >>
> >>
> >
> >
>
>
--=_NextPart_000_00A2_01C45D31.67ADF190
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Seems like the file was blocked =but:
A is =what it should look like but it looks like A in the PDF Export =where as it look fine before the export. Again we have installed SP1 and the font is =available on both server & client.
Regards
Jonas
"Jonas Larsen"
--=_NextPart_000_00A2_01C45D31.67ADF190--|||This is a multi-part message in MIME format.
--=_NextPart_000_0297_01C45DAF.830CCA50
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Can you send me the font and the report directly? My address is =bwelcker@.microsoft.com. The only workaround I can think of for now is to =use an image.
-- Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no =rights.
"Jonas Larsen" <Jonas.Larsen@.Alcan.com> wrote in message =news:OWSTV3NXEHA.2716@.tk2msftngp13.phx.gbl...
Seems like the file was blocked but:
A is what it should look like but it looks like A in the PDF Export =where as it look fine before the export. Again we have installed SP1 and =the font is available on both server & client.
Regards
Jonas
"Jonas Larsen" <Jonas.Larsen@.Alcan.com> wrote in message =news:ueda9cNXEHA.4032@.TK2MSFTNGP11.phx.gbl...
Yes it is a true type font. My conmpay have their logo as a font but =once
exported to PDF it shows as a normal font. Where as it comes up ok =in eg
Excel.
From the Document Properties in Acrobat Reader it says
Type: True Type
Encoding: Ansi
Actual Font: Adibe Sans MM
In the attached file is how it looks once exported to pdf and how is =looks
before export.
Regards
Jonas
"Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in =message
news:uQVTQyMXEHA.1684@.tk2msftngp13.phx.gbl...
> Can you give a specific example of the font issue? Is it a True =Type font?
>
> -- > Brian Welcker
> Group Program Manager
> SQL Server Reporting Services
>
> This posting is provided "AS IS" with no warranties, and confers =no
rights.
>
> "Jonas Larsen" <Jonas.Larsen@.Alcan.com> wrote in message
> news:u8KyQNLXEHA.2816@.TK2MSFTNGP11.phx.gbl...
> > Hmm Sorry please disregard the header/footer page bit. However =the font
> > issue is still an issue.
> >
> > Regards
> > Jonas
> > "Jonas Larsen" <Jonas.Larsen@.Alcan.com> wrote in message
> > news:e67RXWKXEHA.1128@.TK2MSFTNGP10.phx.gbl...
> >> When I try to export to PDF or TIFF the report seems to give me =1 page
> > then
> >> 2 pages only containing the page header and page footer then =the next
> >> page
> >> followed by 2 pages with only header and footer and so forth.
> >> We have just installed SP1 which did not fix this problem.
> >>
> >> Another issue not fixed by SP1 is that we use a specific font =which is
> >> installed on both server and client that shows as a different =font on
the
> >> PDF export however is fine on every other export.
> >>
> >> Any ideas?
> >>
> >> Regards
> >> Jonas
> >>
> >>
> >
> >
>
>
--=_NextPart_000_0297_01C45DAF.830CCA50
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Can you send me the font and the report =directly? My address is bwelcker@.microsoft.com. T=he only workaround I can think of for now is to use an image.
-- Brian WelckerGroup Program ManagerSQL Server =Reporting Services
This posting is provided "AS IS" with no warranties, and confers no =rights.
"Jonas Larsen"
Seems like the file was blocked =but:
A is what it should look like but it looks like A in the PDF Export =where as it look fine before the export. Again we have installed SP1 and the =font is available on both server & client.
Regards
Jonas
"Jonas Larsen"
--=_NextPart_000_0297_01C45DAF.830CCA50--
Wednesday, March 7, 2012
Export to Excel Spreadsheet
I am going to export a numeric(14,2) field that containing
the Balance to a CSV file. It will be opened by the
Finance Staff with Excel.
They would like to get the Balance Field opened as
Currency Field (With $ sign). Is it possible for us to
convert the Balance Field or do some manuipulation so that
it means her need ?
ThanksYou might try just prefixing it with a $ e.g. Instead of
SELECT numeric_column
Use
SELECT '$' + RTRIM(numeric_column)
Not sure if Excel will automatically recognize it as currency as a string,
but that's probably as close as you're going to get--SQL Server doesn't have
any clue what Excel is, never mind what Excel commands you would embed to
force the confusion. Besides, since you're exporting to CSV, there's
nothing you can embed anyway... It won't process any Excel commands you
include in a plain text CSV file...
On 3/13/05 7:12 PM, in article 7c4301c5282a$88d2c8e0$a601280a@.phx.gbl,
"Paul" <anonymous@.discussions.microsoft.com> wrote:
> I am going to export a numeric(14,2) field that containing
> the Balance to a CSV file. It will be opened by the
> Finance Staff with Excel.
> They would like to get the Balance Field opened as
> Currency Field (With $ sign). Is it possible for us to
> convert the Balance Field or do some manuipulation so that
> it means her need ?
> Thanks|||Thank you for your advice and it seems work properly.
However, I would like to know why we have to use RTRIM. I
have attempted not to use RTRIM, it gives me an error
message.
>--Original Message--
>You might try just prefixing it with a $ e.g. Instead of
>SELECT numeric_column
>Use
>SELECT '$' + RTRIM(numeric_column)
>Not sure if Excel will automatically recognize it as
currency as a string,
>but that's probably as close as you're going to get--SQL
Server doesn't have
>any clue what Excel is, never mind what Excel commands
you would embed to
>force the confusion. Besides, since you're exporting to
CSV, there's
>nothing you can embed anyway... It won't process any
Excel commands you
>include in a plain text CSV file...
>
>On 3/13/05 7:12 PM, in article 7c4301c5282a$88d2c8e0
$a601280a@.phx.gbl,
>"Paul" <anonymous@.discussions.microsoft.com> wrote:
>> I am going to export a numeric(14,2) field that
containing
>> the Balance to a CSV file. It will be opened by the
>> Finance Staff with Excel.
>> They would like to get the Balance Field opened as
>> Currency Field (With $ sign). Is it possible for us to
>> convert the Balance Field or do some manuipulation so
that
>> it means her need ?
>> Thanks
>.
>|||SQL needs to convert your numeric_column to a string/char/varchar before it
can perform string manipulations on it. RTRIM does the job, as will CAST(
... AS VARCHAR(xx)).
"Paul" <anonymous@.discussions.microsoft.com> wrote in message
news:7c5f01c52833$8a494d30$a601280a@.phx.gbl...
> Thank you for your advice and it seems work properly.
> However, I would like to know why we have to use RTRIM. I
> have attempted not to use RTRIM, it gives me an error
> message.
>
>>--Original Message--
>>You might try just prefixing it with a $ e.g. Instead of
>>SELECT numeric_column
>>Use
>>SELECT '$' + RTRIM(numeric_column)
>>Not sure if Excel will automatically recognize it as
> currency as a string,
>>but that's probably as close as you're going to get--SQL
> Server doesn't have
>>any clue what Excel is, never mind what Excel commands
> you would embed to
>>force the confusion. Besides, since you're exporting to
> CSV, there's
>>nothing you can embed anyway... It won't process any
> Excel commands you
>>include in a plain text CSV file...
>>
>>On 3/13/05 7:12 PM, in article 7c4301c5282a$88d2c8e0
> $a601280a@.phx.gbl,
>>"Paul" <anonymous@.discussions.microsoft.com> wrote:
>> I am going to export a numeric(14,2) field that
> containing
>> the Balance to a CSV file. It will be opened by the
>> Finance Staff with Excel.
>> They would like to get the Balance Field opened as
>> Currency Field (With $ sign). Is it possible for us to
>> convert the Balance Field or do some manuipulation so
> that
>> it means her need ?
>> Thanks
>>.|||> However, I would like to know why we have to use RTRIM.
RTRIM implicitly casts the numeric value as a string. There are several
other functions you can use to do this, such as LTRIM, or you can cast it
explicitly using CAST or CONVERT (I just find those more cumbersome).
If you don't change the numeric value to a varchar, SQL Server will cock up
an eyebrow and look at you funny, asking how you expect it to add '$' to
4.75... They are incompatible types for the addition and/or string
concatenation operator.
A
the Balance to a CSV file. It will be opened by the
Finance Staff with Excel.
They would like to get the Balance Field opened as
Currency Field (With $ sign). Is it possible for us to
convert the Balance Field or do some manuipulation so that
it means her need ?
ThanksYou might try just prefixing it with a $ e.g. Instead of
SELECT numeric_column
Use
SELECT '$' + RTRIM(numeric_column)
Not sure if Excel will automatically recognize it as currency as a string,
but that's probably as close as you're going to get--SQL Server doesn't have
any clue what Excel is, never mind what Excel commands you would embed to
force the confusion. Besides, since you're exporting to CSV, there's
nothing you can embed anyway... It won't process any Excel commands you
include in a plain text CSV file...
On 3/13/05 7:12 PM, in article 7c4301c5282a$88d2c8e0$a601280a@.phx.gbl,
"Paul" <anonymous@.discussions.microsoft.com> wrote:
> I am going to export a numeric(14,2) field that containing
> the Balance to a CSV file. It will be opened by the
> Finance Staff with Excel.
> They would like to get the Balance Field opened as
> Currency Field (With $ sign). Is it possible for us to
> convert the Balance Field or do some manuipulation so that
> it means her need ?
> Thanks|||Thank you for your advice and it seems work properly.
However, I would like to know why we have to use RTRIM. I
have attempted not to use RTRIM, it gives me an error
message.
>--Original Message--
>You might try just prefixing it with a $ e.g. Instead of
>SELECT numeric_column
>Use
>SELECT '$' + RTRIM(numeric_column)
>Not sure if Excel will automatically recognize it as
currency as a string,
>but that's probably as close as you're going to get--SQL
Server doesn't have
>any clue what Excel is, never mind what Excel commands
you would embed to
>force the confusion. Besides, since you're exporting to
CSV, there's
>nothing you can embed anyway... It won't process any
Excel commands you
>include in a plain text CSV file...
>
>On 3/13/05 7:12 PM, in article 7c4301c5282a$88d2c8e0
$a601280a@.phx.gbl,
>"Paul" <anonymous@.discussions.microsoft.com> wrote:
>> I am going to export a numeric(14,2) field that
containing
>> the Balance to a CSV file. It will be opened by the
>> Finance Staff with Excel.
>> They would like to get the Balance Field opened as
>> Currency Field (With $ sign). Is it possible for us to
>> convert the Balance Field or do some manuipulation so
that
>> it means her need ?
>> Thanks
>.
>|||SQL needs to convert your numeric_column to a string/char/varchar before it
can perform string manipulations on it. RTRIM does the job, as will CAST(
... AS VARCHAR(xx)).
"Paul" <anonymous@.discussions.microsoft.com> wrote in message
news:7c5f01c52833$8a494d30$a601280a@.phx.gbl...
> Thank you for your advice and it seems work properly.
> However, I would like to know why we have to use RTRIM. I
> have attempted not to use RTRIM, it gives me an error
> message.
>
>>--Original Message--
>>You might try just prefixing it with a $ e.g. Instead of
>>SELECT numeric_column
>>Use
>>SELECT '$' + RTRIM(numeric_column)
>>Not sure if Excel will automatically recognize it as
> currency as a string,
>>but that's probably as close as you're going to get--SQL
> Server doesn't have
>>any clue what Excel is, never mind what Excel commands
> you would embed to
>>force the confusion. Besides, since you're exporting to
> CSV, there's
>>nothing you can embed anyway... It won't process any
> Excel commands you
>>include in a plain text CSV file...
>>
>>On 3/13/05 7:12 PM, in article 7c4301c5282a$88d2c8e0
> $a601280a@.phx.gbl,
>>"Paul" <anonymous@.discussions.microsoft.com> wrote:
>> I am going to export a numeric(14,2) field that
> containing
>> the Balance to a CSV file. It will be opened by the
>> Finance Staff with Excel.
>> They would like to get the Balance Field opened as
>> Currency Field (With $ sign). Is it possible for us to
>> convert the Balance Field or do some manuipulation so
> that
>> it means her need ?
>> Thanks
>>.|||> However, I would like to know why we have to use RTRIM.
RTRIM implicitly casts the numeric value as a string. There are several
other functions you can use to do this, such as LTRIM, or you can cast it
explicitly using CAST or CONVERT (I just find those more cumbersome).
If you don't change the numeric value to a varchar, SQL Server will cock up
an eyebrow and look at you funny, asking how you expect it to add '$' to
4.75... They are incompatible types for the addition and/or string
concatenation operator.
A
Friday, February 17, 2012
Export table containing BIT data
I'm trying to export a table that contains a bit field into a text file to be used for a bulk insert into another database.
Using CONVERT
when i export the data from SQL enterprise manager, the bit field is exported as the text TRUE or FALSE ?!!!
this data then cant be bulk inserted as its not a BIT anymore.
how can bit fields be properly exported as 1 or 0 ?Are you doing this in a DTS Package? Use CAST or CONVERT on the BIT field and change the output to an INTEGER or CHAR(1). They are basically the same thing but in this scenario either or is fine; since BIT transformation are not explicit and generally require no intervention to get the value of 1 or 0, however if I'm not mistaken, using a Text ODBC driver causes BITs to be converted to TRUE/FALSE. That's why I asked if you are using DTS, it's ODBC driven. If you are using DTS, you will need to write a query in the Source tab using one of the functions below.
Using CAST
CAST(bYourBit AS INTEGER) AS bYourBit
Using CONVERT
CONVERT(CHAR(1),bYourBit) AS bYourBit
Export sql query to excel vba easier way
Hi,
I have a query ( Using sql) containing data that i need to export into excel.
I am currently exporting it by cut and paste the data, it is
not a very intuitive way of doing things, what i would prefer is if i
could have a button on a form which when it was clicked, it
automatically exported the query to a Excel file. Can anyone help me
with the VBA that would be neccessary, so i can connect excel and ms sql.Have you tried using MS query from Excel? Open a blank worksheet, click on "Data", "Import External Data", then "New Database Query". That will open up MS-Query with the query wizard. You can use the wizard to recreate your sql query from you db tables, or just stop the wizard, click on the SQL button in MS query and you can actually paste the sql code there. Will probably have some syntax issues, but those are pretty easy to solve. Once the query is created in MS-Query and you export the results to Excel, the query will be saved with the worksheet and you can use VB to simply refresh the query by the name you assign. Will need to set up an OBDC SQL driver to your db for this to work.
Note: If you can possibly create the query via the MSquery wizard, that is best, since you can then use fields from the Excel sheet to contain variable parameters to pass through to the query if you need to. If there are no variables to change on the sql query, it doesn't matter then.|||Another possibility is to use ODBC an call with an Access DB. Then use a form to export the data to excel.
We do that a lot with SQL and Oracle databases.|||You Can also use Ms SQL Server DTS.
Open the Export Wizard and set the source and destination. then enter your Query to run. at the Final Step Save the package as Vbscript.
now you can use this Code in your VB program and Run In your desired Time. you can also schedule it that SQL Server exports your data to Excel file in specified Times.
hope to be useful
I have a query ( Using sql) containing data that i need to export into excel.
I am currently exporting it by cut and paste the data, it is
not a very intuitive way of doing things, what i would prefer is if i
could have a button on a form which when it was clicked, it
automatically exported the query to a Excel file. Can anyone help me
with the VBA that would be neccessary, so i can connect excel and ms sql.Have you tried using MS query from Excel? Open a blank worksheet, click on "Data", "Import External Data", then "New Database Query". That will open up MS-Query with the query wizard. You can use the wizard to recreate your sql query from you db tables, or just stop the wizard, click on the SQL button in MS query and you can actually paste the sql code there. Will probably have some syntax issues, but those are pretty easy to solve. Once the query is created in MS-Query and you export the results to Excel, the query will be saved with the worksheet and you can use VB to simply refresh the query by the name you assign. Will need to set up an OBDC SQL driver to your db for this to work.
Note: If you can possibly create the query via the MSquery wizard, that is best, since you can then use fields from the Excel sheet to contain variable parameters to pass through to the query if you need to. If there are no variables to change on the sql query, it doesn't matter then.|||Another possibility is to use ODBC an call with an Access DB. Then use a form to export the data to excel.
We do that a lot with SQL and Oracle databases.|||You Can also use Ms SQL Server DTS.
Open the Export Wizard and set the source and destination. then enter your Query to run. at the Final Step Save the package as Vbscript.
now you can use this Code in your VB program and Run In your desired Time. you can also schedule it that SQL Server exports your data to Excel file in specified Times.
hope to be useful
Subscribe to:
Posts (Atom)