Office and Adobe Compatibiiltly

SQL Server Reporting Services can export to Excel and Adobe. Which versions
of these products are supported?for rs 2005
pdf is 1.3
i have tested xls only on Offce 2003 and above
"Dave" wrote:
> SQL Server Reporting Services can export to Excel and Adobe. Which versions
> of these products are supported?|||Actually, the Adobe version supported is 4.x and above. For Excel, it's what
they call the 97-2003 .xls format in Excel 2007 (which works fine in Excel
2007, btw).
Alain Quesnel
alainsansspam@.logiquel.com
www.logiquel.com
"Jimbo" <Jimbo@.discussions.microsoft.com> wrote in message
news:744AC534-34CF-4EC5-8518-95C41E29E617@.microsoft.com...
> for rs 2005
> pdf is 1.3
> i have tested xls only on Offce 2003 and above
>
>
>
> "Dave" wrote:
>> SQL Server Reporting Services can export to Excel and Adobe. Which
>> versions
>> of these products are supported?|||Hi Alain,
Yes, you are right. I just would like to clarify that although PDF 1.3 is
compatible with Adobe Acrobat 4, Reporting Services supports Adobe Acrobat
6 or later.
You can refer to:
Designing for PDF Output
http://msdn2.microsoft.com/en-us/library/ms159713.aspx
Exporting Reports (Reporting Services)
http://msdn2.microsoft.com/en-us/library/ms157153(SQL.100).aspx
Thank you and have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
===========================================================Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@.microsoft.com.
===========================================================Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
============================================================This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================|||Great stuff. Thanks all!
"Charles Wang[MSFT]" wrote:
> Hi Alain,
> Yes, you are right. I just would like to clarify that although PDF 1.3 is
> compatible with Adobe Acrobat 4, Reporting Services supports Adobe Acrobat
> 6 or later.
> You can refer to:
> Designing for PDF Output
> http://msdn2.microsoft.com/en-us/library/ms159713.aspx
> Exporting Reports (Reporting Services)
> http://msdn2.microsoft.com/en-us/library/ms157153(SQL.100).aspx
> Thank you and have a nice day!
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ===========================================================> Delighting our customers is our #1 priority. We welcome your
> comments and suggestions about how we can improve the
> support we provide to you. Please feel free to let my manager
> know what you think of the level of service provided. You can
> send feedback directly to my manager at: msdnmg@.microsoft.com.
> ===========================================================> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications.
> Note: The MSDN Managed Newsgroup support offering is for
> non-urgent issues where an initial response from the community
> or a Microsoft Support Engineer within 1 business day is acceptable.
> Please note that each follow up response may take approximately
> 2 business days as the support professional working with you may
> need further investigation to reach the most efficient resolution.
> The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by
> contacting Microsoft Customer Support Services (CSS) at
> http://msdn.microsoft.com/subscriptions/support/default.aspx.
> ============================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> =========================================================>

of the 8 versions of sql server 2000...

which one would I use to get used to the general interface of sql server programming on? -Standard and enterprise seem a little over the top for this purpose,
-it sounds like developer is for built for engineering 3rd party apps
-personal is geared toward roadwarriors...maybe it will work?
The programming interface is basically the same on all versions. Developer
Edition is a full-featured edition, targeted at people who build ANY apps
for SQL Server not just ISVs if that's what you mean by 3rd party apps.
Regards,
Greg Linwood
SQL Server MVP
"supernaut" <supernaut@.discussions.microsoft.com> wrote in message
news:90E5ABA4-BB05-4AB7-9CAA-85E92870B791@.microsoft.com...
> which one would I use to get used to the general interface of sql server
programming on? -Standard and enterprise seem a little over the top for
this purpose,
> -it sounds like developer is for built for engineering 3rd party apps
> -personal is geared toward roadwarriors...maybe it will work?
>
|||Beauty! Thanks for the info!
"Greg Linwood" wrote:

> The programming interface is basically the same on all versions. Developer
> Edition is a full-featured edition, targeted at people who build ANY apps
> for SQL Server not just ISVs if that's what you mean by 3rd party apps.
> Regards,
> Greg Linwood
> SQL Server MVP
> "supernaut·" <supernaut@.discussions.microsoft.com> wrote in message
> news:90E5ABA4-BB05-4AB7-9CAA-85E92870B791@.microsoft.com...
> programming on? -Standard and enterprise seem a little over the top for
> this purpose,
>
>

of the 8 versions of sql server 2000...

which one would I use to get used to the general interface of sql server pro
gramming on? -Standard and enterprise seem a little over the top for this p
urpose,
-it sounds like developer is for built for engineering 3rd party apps
-personal is geared toward roadwarriors...maybe it will work?The programming interface is basically the same on all versions. Developer
Edition is a full-featured edition, targeted at people who build ANY apps
for SQL Server not just ISVs if that's what you mean by 3rd party apps.
Regards,
Greg Linwood
SQL Server MVP
"supernaut" <supernaut@.discussions.microsoft.com> wrote in message
news:90E5ABA4-BB05-4AB7-9CAA-85E92870B791@.microsoft.com...
> which one would I use to get used to the general interface of sql server
programming on? -Standard and enterprise seem a little over the top for
this purpose,
> -it sounds like developer is for built for engineering 3rd party apps
> -personal is geared toward roadwarriors...maybe it will work?
>|||Beauty! Thanks for the info!
"Greg Linwood" wrote:

> The programming interface is basically the same on all versions. Developer
> Edition is a full-featured edition, targeted at people who build ANY apps
> for SQL Server not just ISVs if that's what you mean by 3rd party apps.
> Regards,
> Greg Linwood
> SQL Server MVP
> "supernaut·" <supernaut@.discussions.microsoft.com> wrote in message
> news:90E5ABA4-BB05-4AB7-9CAA-85E92870B791@.microsoft.com...
> programming on? -Standard and enterprise seem a little over the top for
> this purpose,
>
>sql

ODBC Woes

I am a programmer but I have many years of experience with Sql Server from
6.5, 7, and 2000 versions.
I have a problem I have never seen before, the first I have been unable to
resolve myself.
After installing the latest Micrsoft Windows XP patches (issued this past
month) and rebooting the Sql Server 2000 on my development computer (Windows
XP SP1) failed to start.
After trying for several days to resolve the situation I decided to
reinstall Sql Server 2000. I also reinstalled MDAC.
Once I was done the Sql Server tried to boot but gave the message ... does
not exits or permision denied.
I went to check ODBC keys in the registry and they are corrupt. Some are
missing and some have bad values.
Is there a tool or article that will help me rebuild the keys? I tried
various aricles all day today but none seems to relate to the problem I
have?
Some other symptoms:
From ODBC Data Source Manager:
I can seem previously setup DSNs.
If I try to Romove or Configure an existing DSN one I get this error:
"The Setup Routine for Sql Server ODBC Driver could not be found. Please
reinstall the driver."
I click OK and get a Windows titled: "Driver's ConfigDSN, ConfigDriver, or
ConfigTranslator failed." In the window is the message: "Component not
found in the registry."
If I try to add a DSN the Create Data Source windows opens but NO drivers
are listed.
Thank you,
Mike
Installing MDAC should fix this.
If it doesn't, you can try running the following command from a command
prompt (in your c:\windows\system32 directory):
odbcconf.exe /F odbcconf.rsp
That should rebuild your registry (try renaming or deleting the existing
\Software\ODBC key first).
Note: this is not supported by Microsoft. This is the same command that
MDAC setup will run on your machine, but it is not "officially" intended
for use outside MDAC setup.
Brannon
Mike McIntyre wrote:

> I am a programmer but I have many years of experience with Sql Server from
> 6.5, 7, and 2000 versions.
> I have a problem I have never seen before, the first I have been unable to
> resolve myself.
> After installing the latest Micrsoft Windows XP patches (issued this past
> month) and rebooting the Sql Server 2000 on my development computer (Windows
> XP SP1) failed to start.
> After trying for several days to resolve the situation I decided to
> reinstall Sql Server 2000. I also reinstalled MDAC.
> Once I was done the Sql Server tried to boot but gave the message ... does
> not exits or permision denied.
> I went to check ODBC keys in the registry and they are corrupt. Some are
> missing and some have bad values.
> Is there a tool or article that will help me rebuild the keys? I tried
> various aricles all day today but none seems to relate to the problem I
> have?
> Some other symptoms:
> From ODBC Data Source Manager:
> I can seem previously setup DSNs.
> If I try to Romove or Configure an existing DSN one I get this error:
> "The Setup Routine for Sql Server ODBC Driver could not be found. Please
> reinstall the driver."
> I click OK and get a Windows titled: "Driver's ConfigDSN, ConfigDriver, or
> ConfigTranslator failed." In the window is the message: "Component not
> found in the registry."
> If I try to add a DSN the Create Data Source windows opens but NO drivers
> are listed.
> Thank you,
> Mike
>
>

ODBC Woes

I am a programmer but I have many years of experience with Sql Server from
6.5, 7, and 2000 versions.
I have a problem I have never seen before, the first I have been unable to
resolve myself.
After installing the latest Micrsoft Windows XP patches (issued this past
month) and rebooting the Sql Server 2000 on my development computer (Windows
XP SP1) failed to start.
After trying for several days to resolve the situation I decided to
reinstall Sql Server 2000. I also reinstalled MDAC.
Once I was done the Sql Server tried to boot but gave the message ... does
not exits or permision denied.
I went to check ODBC keys in the registry and they are corrupt. Some are
missing and some have bad values.
Is there a tool or article that will help me rebuild the keys? I tried
various aricles all day today but none seems to relate to the problem I
have?
Some other symptoms:
From ODBC Data Source Manager:
I can seem previously setup DSNs.
If I try to Romove or Configure an existing DSN one I get this error:
"The Setup Routine for Sql Server ODBC Driver could not be found. Please
reinstall the driver."
I click OK and get a Windows titled: "Driver's ConfigDSN, ConfigDriver, or
ConfigTranslator failed." In the window is the message: "Component not
found in the registry."
If I try to add a DSN the Create Data Source windows opens but NO drivers
are listed.
Thank you,
MikeInstalling MDAC should fix this.
If it doesn't, you can try running the following command from a command
prompt (in your c:\windows\system32 directory):
odbcconf.exe /F odbcconf.rsp
That should rebuild your registry (try renaming or deleting the existing
\Software\ODBC key first).
Note: this is not supported by Microsoft. This is the same command that
MDAC setup will run on your machine, but it is not "officially" intended
for use outside MDAC setup.
Brannon
Mike McIntyre wrote:

> I am a programmer but I have many years of experience with Sql Server from
> 6.5, 7, and 2000 versions.
> I have a problem I have never seen before, the first I have been unable to
> resolve myself.
> After installing the latest Micrsoft Windows XP patches (issued this past
> month) and rebooting the Sql Server 2000 on my development computer (Windo
ws
> XP SP1) failed to start.
> After trying for several days to resolve the situation I decided to
> reinstall Sql Server 2000. I also reinstalled MDAC.
> Once I was done the Sql Server tried to boot but gave the message ... does
> not exits or permision denied.
> I went to check ODBC keys in the registry and they are corrupt. Some are
> missing and some have bad values.
> Is there a tool or article that will help me rebuild the keys? I tried
> various aricles all day today but none seems to relate to the problem I
> have?
> Some other symptoms:
> From ODBC Data Source Manager:
> I can seem previously setup DSNs.
> If I try to Romove or Configure an existing DSN one I get this error:
> "The Setup Routine for Sql Server ODBC Driver could not be found. Please
> reinstall the driver."
> I click OK and get a Windows titled: "Driver's ConfigDSN, ConfigDriver, or
> ConfigTranslator failed." In the window is the message: "Component not
> found in the registry."
> If I try to add a DSN the Create Data Source windows opens but NO drivers
> are listed.
> Thank you,
> Mike
>
>