Hi,
Does anyone know if Microsoft is planning to support embedded fonts in the
near future?
We have been using Crystal Reports for our reporting. We are trying out
Reporting Services for the new reports and we like what we see so far, but
there is one major issue: embedded fonts.
We have lots of customers lined up that require the use of OCRA and Barcode
fonts in their pdf documents. Installing these fonts on each client machine
is not an option.
If there is no such plan to include embedded fonts in the near future, we
may have to go back to Crystal Reports.
Thanks,
George
Thanks,
GeorgeGeorge,
From what I understand, the font must be installed on the report server
itself and of course, you must have had it installed on your designer
workstation when you designed the report. Have you done a test?
As an example, we use the font Ariel Unicode to properly display our
diatrics properly - but the legal way to have this font is to install
Microsoft Word - so we now have our customers install MS Word 2003 on the
web server to get this font.
=-Chris
"george tharakan" <georgetharakan@.discussions.microsoft.com> wrote in
message news:C7373491-754E-4F4F-A277-7BF35840E4E5@.microsoft.com...
> Hi,
> Does anyone know if Microsoft is planning to support embedded fonts in the
> near future?
> We have been using Crystal Reports for our reporting. We are trying out
> Reporting Services for the new reports and we like what we see so far, but
> there is one major issue: embedded fonts.
> We have lots of customers lined up that require the use of OCRA and
> Barcode
> fonts in their pdf documents. Installing these fonts on each client
> machine
> is not an option.
> If there is no such plan to include embedded fonts in the near future, we
> may have to go back to Crystal Reports.
> Thanks,
> George
> Thanks,
> George|||Hi Chris,
I do have the font installed on the reportserver and on the designer
workstation. My reports are exported to PDF. When I view the reports on my
machine I get to see the Barcode and OCRA fonts. When I view the report on a
machine which doesnt have these fonts , the fonts just don't show up. The
issue has to do with embedding fonts with the pdf, in which case the fonts
will show up on all client machines. I know that currently RS doesnt support
embedding fonts. There were some rumours that they might consider something
in a future release. Would just like to hear from them regarding a more
specific timeframe.
If it's like in a couple of months, we could wait, else we have to do this
in crystal.
Thanks|||George - what would happen if you save that PDF file on your local machine,
then go over to the machine that doesn't have this font and open the PDF
document - does it render the PDF correctly?
=-Chris
"george tharakan" <georgetharakan@.discussions.microsoft.com> wrote in
message news:53CD3E02-4BE2-4B5A-A337-EC0D5D005739@.microsoft.com...
> Hi Chris,
> I do have the font installed on the reportserver and on the designer
> workstation. My reports are exported to PDF. When I view the reports on my
> machine I get to see the Barcode and OCRA fonts. When I view the report on
> a
> machine which doesnt have these fonts , the fonts just don't show up. The
> issue has to do with embedding fonts with the pdf, in which case the fonts
> will show up on all client machines. I know that currently RS doesnt
> support
> embedding fonts. There were some rumours that they might consider
> something
> in a future release. Would just like to hear from them regarding a more
> specific timeframe.
> If it's like in a couple of months, we could wait, else we have to do this
> in crystal.
> Thanks|||Chris,
No lucj with that either. The pdf shows correctly only on the machine that
has the font installed.
Thanks,
George
Showing posts with label planning. Show all posts
Showing posts with label planning. Show all posts
Tuesday, March 27, 2012
Wednesday, February 15, 2012
Edition Question for Analysis Services
Hi All
I come with Oracle background and we are planning to use SQL Server 2000 Analysis Services for OLAP.
Brief background on our app: The largest of our fact tables has about 500,000 rows per month. We plan to store three years worth of data. We will have other smaller cubes that we will have to build in addition to this. The source data will come from Oracle tables.
I am struggling to decide between the two SQL Server editions (Standard and Enterprise). I'm highlighting the things that I need some help with in order to make the decision:
Memory Limitation
------
Standard Edition only supports up to 2GB. Considering relatively large cube size (is it?), is this a limitation in our case?
Calcualted Cells (only in Enterprise Edition)
------
I didn't fully understand this one in the documentation, not having spent a lot of time. We do have a number of calculations such as the Revenue/Expense, Margin calculations, etc. Is this an important feature that I should consider?
Partitions:
----
I doubt that we will be partitioning across multiple servers (may not need distributed partioning, linked cubes). However, within a single database/instance, do I have the option to partition the cube (does it help to do so for cube manageability) if I went with Standard Edition? Also, given the large fact tables, I may want to incrementally add monthly data to the cube. Would it help to partition the cube in this case and, do I need Enterprise Edition for this?
HTTP Internet Support: (Enterprise Edition only)
-------
I would think that the HTTP access is applicable to intranet applications (ours is one). Does this support in Enterprise Edition automatically means that the data is available for analysis over the web? What tool would I use to access the data (other than the third party tools such as Crystal Analysis, Brio, etc)? I am trying to see what this means and how this relates to my decision on Std Vs Enterprise Editions.
I really appreciate any input you may have on this.
Thanks in advance
Murthy JarugumilliI would suggest to adopt Enterprise Edition as you already know the limitaitons of Standard edition.
In general Standard edition is used as a database server for a small workgroup or department.
I come with Oracle background and we are planning to use SQL Server 2000 Analysis Services for OLAP.
Brief background on our app: The largest of our fact tables has about 500,000 rows per month. We plan to store three years worth of data. We will have other smaller cubes that we will have to build in addition to this. The source data will come from Oracle tables.
I am struggling to decide between the two SQL Server editions (Standard and Enterprise). I'm highlighting the things that I need some help with in order to make the decision:
Memory Limitation
------
Standard Edition only supports up to 2GB. Considering relatively large cube size (is it?), is this a limitation in our case?
Calcualted Cells (only in Enterprise Edition)
------
I didn't fully understand this one in the documentation, not having spent a lot of time. We do have a number of calculations such as the Revenue/Expense, Margin calculations, etc. Is this an important feature that I should consider?
Partitions:
----
I doubt that we will be partitioning across multiple servers (may not need distributed partioning, linked cubes). However, within a single database/instance, do I have the option to partition the cube (does it help to do so for cube manageability) if I went with Standard Edition? Also, given the large fact tables, I may want to incrementally add monthly data to the cube. Would it help to partition the cube in this case and, do I need Enterprise Edition for this?
HTTP Internet Support: (Enterprise Edition only)
-------
I would think that the HTTP access is applicable to intranet applications (ours is one). Does this support in Enterprise Edition automatically means that the data is available for analysis over the web? What tool would I use to access the data (other than the third party tools such as Crystal Analysis, Brio, etc)? I am trying to see what this means and how this relates to my decision on Std Vs Enterprise Editions.
I really appreciate any input you may have on this.
Thanks in advance
Murthy JarugumilliI would suggest to adopt Enterprise Edition as you already know the limitaitons of Standard edition.
In general Standard edition is used as a database server for a small workgroup or department.
Subscribe to:
Posts (Atom)