OLAP / Analysis services version checking by client

The problem is that i would like to integrate a code to the file in net where MS Office Web Components and OLAP services are beeing used.
Code should automatically detect a version of olap client and office web service components (OWC) and if newer version is needed, then it should download it.
Good instructions were @. http://support.microsoft.com/default.aspx?scid=kb;en-us;312876
where ptssetup.exe included all necessary information, but it was applied to Microsoft SQL Server 2000 Analysis Services. Now what i need to know is how to write a code which is working on Microsoft SQL Server 2005. Or how the old code can be changed to get it work on sql server 2005?

Hello,

I'm going to move your question to one of the SQL Server forums were they should be able to help you.

Daniel Roth

|||

Erkki wrote:

The problem is that i would like to integrate a code to the file in net where MS Office Web Components and OLAP services are beeing used.
Code should automatically detect a version of olap client and office web service components (OWC) and if newer version is needed, then it should download it.
Good instructions were @. http://support.microsoft.com/default.aspx?scid=kb;en-us;312876
where ptssetup.exe included all necessary information, but it was applied to Microsoft SQL Server 2000 Analysis Services. Now what i need to know is how to write a code which is working on Microsoft SQL Server 2005. Or how the old code can be changed to get it work on sql server 2005?

I would like to know that too. Anyway, how is it possible to verify the version of OLAP ? How can it be done? Maybe to somehow connect to server where the olap is being used?

Ok button not responding

I installed the developer version of reporting services
and I am having problems getting things entered in the
admin screens. When I go to the "New Data Source"
screen, the OK button does nothing. I have no script
errors on the page, and have other .net applications
running on the web server. I also have problems when
trying to update roles/security. I get an error when
click the ok button telling me that I need to select at
least 1 role even though I have them selected.I ran this command and all my .net pages stopped
responding. I had to uninstall .net and reinstall, and
then uninstall RS and reinstall and I still have the same
problem.
Any suggestions?
Thanks,
Dan J
>--Original Message--
>Dan
>I also encountered this problem.
>Sometimes during the install the IIS registration fails.
If you run the
>following at the command line this resolves the problem.
>C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
\aspnet_regiis.exe -i
>This should fix your problem
>Cheers
>
>"Dan J" wrote:
>> I installed the developer version of reporting
services
>> and I am having problems getting things entered in the
>> admin screens. When I go to the "New Data Source"
>> screen, the OK button does nothing. I have no script
>> errors on the page, and have other .net applications
>> running on the web server. I also have problems when
>> trying to update roles/security. I get an error when
>> click the ok button telling me that I need to select
at
>> least 1 role even though I have them selected.
>>
>.
>|||Dan,
I ran into something like this before. Reporting services installs to your
default website. When things get moved around (like I tried to do), your root
website can be missing the aspnet_client folder (usually found in
c:\inetpub\wwwroot). Just copy this folder over to the root of your website.
That folder contains some java scripts that contain some generic code which
is required for RS to execute the commands in the manager.
- Matt
"Dan J" wrote:
> I ran this command and all my .net pages stopped
> responding. I had to uninstall .net and reinstall, and
> then uninstall RS and reinstall and I still have the same
> problem.
> Any suggestions?
> Thanks,
> Dan J
> >--Original Message--
> >Dan
> >
> >I also encountered this problem.
> >
> >Sometimes during the install the IIS registration fails.
> If you run the
> >following at the command line this resolves the problem.
> >
> >C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
> \aspnet_regiis.exe -i
> >
> >This should fix your problem
> >
> >Cheers
> >
> >
> >"Dan J" wrote:
> >
> >> I installed the developer version of reporting
> services
> >> and I am having problems getting things entered in the
> >> admin screens. When I go to the "New Data Source"
> >> screen, the OK button does nothing. I have no script
> >> errors on the page, and have other .net applications
> >> running on the web server. I also have problems when
> >> trying to update roles/security. I get an error when
> >> click the ok button telling me that I need to select
> at
> >> least 1 role even though I have them selected.
> >>
> >>
> >.
> >
>|||I havent moved any websites on my server. I tried
copying the aspnet_client to the root of both of the RS
virtual directories (out of frustration) but still no
luck. I assume it is an asp problem, just not sure what
it needs. I havent done anything "wierd" with the server
or any of the installs.
Please help!!!
Dan
>--Original Message--
>Dan,
>I ran into something like this before. Reporting
services installs to your
>default website. When things get moved around (like I
tried to do), your root
>website can be missing the aspnet_client folder (usually
found in
>c:\inetpub\wwwroot). Just copy this folder over to the
root of your website.
>That folder contains some java scripts that contain some
generic code which
>is required for RS to execute the commands in the
manager.
>- Matt
>"Dan J" wrote:
>> I ran this command and all my .net pages stopped
>> responding. I had to uninstall .net and reinstall,
and
>> then uninstall RS and reinstall and I still have the
same
>> problem.
>> Any suggestions?
>> Thanks,
>> Dan J
>> >--Original Message--
>> >Dan
>> >
>> >I also encountered this problem.
>> >
>> >Sometimes during the install the IIS registration
fails.
>> If you run the
>> >following at the command line this resolves the
problem.
>> >
>> >C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
>> \aspnet_regiis.exe -i
>> >
>> >This should fix your problem
>> >
>> >Cheers
>> >
>> >
>> >"Dan J" wrote:
>> >
>> >> I installed the developer version of reporting
>> services
>> >> and I am having problems getting things entered in
the
>> >> admin screens. When I go to the "New Data Source"
>> >> screen, the OK button does nothing. I have no
script
>> >> errors on the page, and have other .net
applications
>> >> running on the web server. I also have problems
when
>> >> trying to update roles/security. I get an error
when
>> >> click the ok button telling me that I need to
select
>> at
>> >> least 1 role even though I have them selected.
>> >>
>> >>
>> >.
>> >
>.
>sql

Office 2003 Web Service Reference Tool fails on ReportingService

I am trying to add a web reference to an Access 2003 database form using the
latest version of the Web Services Toolkit. When I try to add the reference
it runs for a while and then blows up with the following message.
Cannot Create Class.
The Web Service References Tool could not generate the requested code. Any
changes that were made to your project have been rolled back.
Any help would be appreciated.this newsgroup is for SQL Server Reporting Services. You will get better
responses if you post this in one of the Access newsgroups.
"TMesich" <TMesich@.discussions.microsoft.com> wrote in message
news:6EB2929F-C179-4348-B931-E15451985189@.microsoft.com...
>I am trying to add a web reference to an Access 2003 database form using
>the
> latest version of the Web Services Toolkit. When I try to add the
> reference
> it runs for a while and then blows up with the following message.
> Cannot Create Class.
> The Web Service References Tool could not generate the requested code.
> Any
> changes that were made to your project have been rolled back.
> Any help would be appreciated.

of upgrade options

Hi all, we are currently exploring developing a new .net 1.1 application
using a sql 2005 database. We have a copy of the April CTP Version and
wanted to know the following:-
1. Does MS have a ship date for SQL 2005?
2. Will an upgrade path be available from CTP to Release Version? We do not
want to have to re-build the server if we deploy.
3. Are significant code changes anticipated between CTP & Release?
Furthermore, will MS provide an upgrade path from existing sql2k databases
to 2005?
thanks!> 1. Does MS have a ship date for SQL 2005?
The oficial line is "second half of 2005".
> 2. Will an upgrade path be available from CTP to Release Version? We do
> not
> want to have to re-build the server if we deploy.
The CTP is licensed for development and testing purposes only (except
Express Edition, which includes a go-live licence) so you can't actually
deploy it prior to official release without special licence from Microsoft.
In the past the usual position is that upgrades from pre-release software
aren't supported but if you are supported by MS as an early adopter then
they may take a different line. You'd have to ask them.
> 3. Are significant code changes anticipated between CTP & Release?
MS says the April release is feature complete. Any change may be significant
if it affects the functionality you are using. It's always a possibility.
> Furthermore, will MS provide an upgrade path from existing sql2k databases
> to 2005?
Yes.
--
David Portas
SQL Server MVP
--|||In addition to David's repsonse, MS has said that from now on, future CTPs
will include upgrade from the prior CTP... Whether that includes a final
upgrade to production I do not know ( but perhaps it will.)
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:Jf2dnWaEyackrD7fRVn-ig@.giganews.com...
>> 1. Does MS have a ship date for SQL 2005?
> The oficial line is "second half of 2005".
>> 2. Will an upgrade path be available from CTP to Release Version? We do
>> not
>> want to have to re-build the server if we deploy.
> The CTP is licensed for development and testing purposes only (except
> Express Edition, which includes a go-live licence) so you can't actually
> deploy it prior to official release without special licence from
> Microsoft. In the past the usual position is that upgrades from
> pre-release software aren't supported but if you are supported by MS as an
> early adopter then they may take a different line. You'd have to ask them.
>> 3. Are significant code changes anticipated between CTP & Release?
> MS says the April release is feature complete. Any change may be
> significant if it affects the functionality you are using. It's always a
> possibility.
>> Furthermore, will MS provide an upgrade path from existing sql2k
>> databases to 2005?
> Yes.
> --
> David Portas
> SQL Server MVP
> --
>|||I love how everyone says "2nd half of 2005". A specific date/month would be
useful since that is the sole consideration on whether we can deploy or not.
thanks
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:Jf2dnWaEyackrD7fRVn-ig@.giganews.com...
>> 1. Does MS have a ship date for SQL 2005?
> The oficial line is "second half of 2005".
>> 2. Will an upgrade path be available from CTP to Release Version? We do
>> not
>> want to have to re-build the server if we deploy.
> The CTP is licensed for development and testing purposes only (except
> Express Edition, which includes a go-live licence) so you can't actually
> deploy it prior to official release without special licence from
> Microsoft. In the past the usual position is that upgrades from
> pre-release software aren't supported but if you are supported by MS as an
> early adopter then they may take a different line. You'd have to ask them.
>> 3. Are significant code changes anticipated between CTP & Release?
> MS says the April release is feature complete. Any change may be
> significant if it affects the functionality you are using. It's always a
> possibility.
>> Furthermore, will MS provide an upgrade path from existing sql2k
>> databases to 2005?
> Yes.
> --
> David Portas
> SQL Server MVP
> --
>|||A date is only useful if it's accurate. That's why MS won't commit
until they are ready. Even if you had an expected date would you really
want to bet the success of your project on it?
--
David Portas
SQL Server MVP
--|||http://www.microsoft.com/presspass/misc/06-07flessner-teched05.mspx
Second week of November.
--
David Portas
SQL Server MVP
--

of upgrade options

Hi all, we are currently exploring developing a new .net 1.1 application
using a sql 2005 database. We have a copy of the April CTP Version and
wanted to know the following:-
1. Does MS have a ship date for SQL 2005?
2. Will an upgrade path be available from CTP to Release Version? We do not
want to have to re-build the server if we deploy.
3. Are significant code changes anticipated between CTP & Release?
Furthermore, will MS provide an upgrade path from existing sql2k databases
to 2005?
thanks!
> 1. Does MS have a ship date for SQL 2005?
The oficial line is "second half of 2005".

> 2. Will an upgrade path be available from CTP to Release Version? We do
> not
> want to have to re-build the server if we deploy.
The CTP is licensed for development and testing purposes only (except
Express Edition, which includes a go-live licence) so you can't actually
deploy it prior to official release without special licence from Microsoft.
In the past the usual position is that upgrades from pre-release software
aren't supported but if you are supported by MS as an early adopter then
they may take a different line. You'd have to ask them.

> 3. Are significant code changes anticipated between CTP & Release?
MS says the April release is feature complete. Any change may be significant
if it affects the functionality you are using. It's always a possibility.

> Furthermore, will MS provide an upgrade path from existing sql2k databases
> to 2005?
Yes.
David Portas
SQL Server MVP
|||In addition to David's repsonse, MS has said that from now on, future CTPs
will include upgrade from the prior CTP... Whether that includes a final
upgrade to production I do not know ( but perhaps it will.)
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:Jf2dnWaEyackrD7fRVn-ig@.giganews.com...
> The oficial line is "second half of 2005".
>
> The CTP is licensed for development and testing purposes only (except
> Express Edition, which includes a go-live licence) so you can't actually
> deploy it prior to official release without special licence from
> Microsoft. In the past the usual position is that upgrades from
> pre-release software aren't supported but if you are supported by MS as an
> early adopter then they may take a different line. You'd have to ask them.
>
> MS says the April release is feature complete. Any change may be
> significant if it affects the functionality you are using. It's always a
> possibility.
>
> Yes.
> --
> David Portas
> SQL Server MVP
> --
>
|||I love how everyone says "2nd half of 2005". A specific date/month would be
useful since that is the sole consideration on whether we can deploy or not.
thanks
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:Jf2dnWaEyackrD7fRVn-ig@.giganews.com...
> The oficial line is "second half of 2005".
>
> The CTP is licensed for development and testing purposes only (except
> Express Edition, which includes a go-live licence) so you can't actually
> deploy it prior to official release without special licence from
> Microsoft. In the past the usual position is that upgrades from
> pre-release software aren't supported but if you are supported by MS as an
> early adopter then they may take a different line. You'd have to ask them.
>
> MS says the April release is feature complete. Any change may be
> significant if it affects the functionality you are using. It's always a
> possibility.
>
> Yes.
> --
> David Portas
> SQL Server MVP
> --
>
|||A date is only useful if it's accurate. That's why MS won't commit
until they are ready. Even if you had an expected date would you really
want to bet the success of your project on it?
David Portas
SQL Server MVP
|||http://www.microsoft.com/presspass/m...-teched05.mspx
Second week of November.
David Portas
SQL Server MVP

of upgrade options

Hi all, we are currently exploring developing a new .net 1.1 application
using a sql 2005 database. We have a copy of the April CTP Version and
wanted to know the following:-
1. Does MS have a ship date for SQL 2005?
2. Will an upgrade path be available from CTP to Release Version? We do not
want to have to re-build the server if we deploy.
3. Are significant code changes anticipated between CTP & Release?
Furthermore, will MS provide an upgrade path from existing sql2k databases
to 2005?
thanks!> 1. Does MS have a ship date for SQL 2005?
The oficial line is "second half of 2005".

> 2. Will an upgrade path be available from CTP to Release Version? We do
> not
> want to have to re-build the server if we deploy.
The CTP is licensed for development and testing purposes only (except
Express Edition, which includes a go-live licence) so you can't actually
deploy it prior to official release without special licence from Microsoft.
In the past the usual position is that upgrades from pre-release software
aren't supported but if you are supported by MS as an early adopter then
they may take a different line. You'd have to ask them.

> 3. Are significant code changes anticipated between CTP & Release?
MS says the April release is feature complete. Any change may be significant
if it affects the functionality you are using. It's always a possibility.

> Furthermore, will MS provide an upgrade path from existing sql2k databases
> to 2005?
Yes.
David Portas
SQL Server MVP
--|||In addition to David's repsonse, MS has said that from now on, future CTPs
will include upgrade from the prior CTP... Whether that includes a final
upgrade to production I do not know ( but perhaps it will.)
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:Jf2dnWaEyackrD7fRVn-ig@.giganews.com...
> The oficial line is "second half of 2005".
>
> The CTP is licensed for development and testing purposes only (except
> Express Edition, which includes a go-live licence) so you can't actually
> deploy it prior to official release without special licence from
> Microsoft. In the past the usual position is that upgrades from
> pre-release software aren't supported but if you are supported by MS as an
> early adopter then they may take a different line. You'd have to ask them.
>
> MS says the April release is feature complete. Any change may be
> significant if it affects the functionality you are using. It's always a
> possibility.
>
> Yes.
> --
> David Portas
> SQL Server MVP
> --
>|||I love how everyone says "2nd half of 2005". A specific date/month would be
useful since that is the sole consideration on whether we can deploy or not.
thanks
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:Jf2dnWaEyackrD7fRVn-ig@.giganews.com...
> The oficial line is "second half of 2005".
>
> The CTP is licensed for development and testing purposes only (except
> Express Edition, which includes a go-live licence) so you can't actually
> deploy it prior to official release without special licence from
> Microsoft. In the past the usual position is that upgrades from
> pre-release software aren't supported but if you are supported by MS as an
> early adopter then they may take a different line. You'd have to ask them.
>
> MS says the April release is feature complete. Any change may be
> significant if it affects the functionality you are using. It's always a
> possibility.
>
> Yes.
> --
> David Portas
> SQL Server MVP
> --
>|||A date is only useful if it's accurate. That's why MS won't commit
until they are ready. Even if you had an expected date would you really
want to bet the success of your project on it?
David Portas
SQL Server MVP
--|||http://www.microsoft.com/presspass/...r-teched05.mspx
Second week of November.
David Portas
SQL Server MVP
--

ODBC, SQL Server, "FOR XML" & Cursors error

Hi,


Has anybody had any luck using the Microsoft SQLServer ODBC drivers (Driver version: 03.81.9030, ODBC version : 03.52)

to connect to a SQL Server 2000 database and passing in a SELECT with a FOR XML clause. I keep

getting Error [Microsoft][ODBC SQL Server Driver][SQL Server]The FOR XML clause is not allowed in a CURSOR statement

., State: 42000, Error: 6819.

Is there a work around (eg putting the select in a stored procedure) or am I missing something ?

I am using SQLExecDirect() to execute the statement.

Or could any one suggest a better way to retrieve data from a standard table in XML formated string?


Please Help!!If you are using a cursor or a loop (it may actually work in a loop, but methinks NOT), then create a stored procedure that contains just SELECT...FOR XML AUTO/RAW/whatever. But I don't see a point doing that because further processing of the data retrieved in XML format within a stored procedure is not supported. Check this site for general guidelines on using FOR XML clause:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xmlsql/ac_openxml_0alh.asp

ODBC Version with MDAC 2.8?

I am unable to determine what version of Microsoft's SQL Server ODBC
driver comes with MDAC 2.8.
Currently I'm using driver "SQL SERVER" SQLSRV32.DLL, 10/27/2003,
version 2000.81.9042.00 (with Windows 2000, SQL Server 2000, Access XP)
and I only want to upgrade to MDAC 2.8 if it updates this ODBC driver.
Any ideas?
MDAC 2.8 installs version 2000.85.1022.0
-Sue
On Fri, 16 Apr 2004 18:40:42 GMT, John Smith
<JohnSmith@.hotmail.com> wrote:

>I am unable to determine what version of Microsoft's SQL Server ODBC
>driver comes with MDAC 2.8.
>Currently I'm using driver "SQL SERVER" SQLSRV32.DLL, 10/27/2003,
>version 2000.81.9042.00 (with Windows 2000, SQL Server 2000, Access XP)
>and I only want to upgrade to MDAC 2.8 if it updates this ODBC driver.
>Any ideas?

ODBC Version with MDAC 2.8?

I am unable to determine what version of Microsoft's SQL Server ODBC
driver comes with MDAC 2.8.
Currently I'm using driver "SQL SERVER" SQLSRV32.DLL, 10/27/2003,
version 2000.81.9042.00 (with Windows 2000, SQL Server 2000, Access XP)
and I only want to upgrade to MDAC 2.8 if it updates this ODBC driver.
Any ideas?MDAC 2.8 installs version 2000.85.1022.0
-Sue
On Fri, 16 Apr 2004 18:40:42 GMT, John Smith
<JohnSmith@.hotmail.com> wrote:

>I am unable to determine what version of Microsoft's SQL Server ODBC
>driver comes with MDAC 2.8.
>Currently I'm using driver "SQL SERVER" SQLSRV32.DLL, 10/27/2003,
>version 2000.81.9042.00 (with Windows 2000, SQL Server 2000, Access XP)
>and I only want to upgrade to MDAC 2.8 if it updates this ODBC driver.
>Any ideas?

ODBC Linked Server & DSN

Hi,
Short version of question:
For linked servers to ODBC DSN data sources, does the DSN have to be setup
on the same windows server as the sql server 2005 instance? Or is only
requirment that the DSN is setup from the workstaing that is luanching SSMS?
Longer Background for question:
I'm attempting to setup a linked server in SQL Server 2005 to an ODBC
datasource which is Centura SQLbase database.
On my workstation, I have a DSN setup with the odbc drivers to connect to
the SQLbase db. The driver was "Centura SQLBase 3.60 32-bit Driver -NT &
Win95"
I can successfully import that tables from SQLBase using Access.
I'm using the SQL Server Managment Studio from my desktop to connect to the
SQL 2005 Server on a Windows 2003 Server.
When testing the Linked server by using a query, I use the following syntax
in a query in SSMS:
SELECT LastName, FirstName FROM LINK2SQLBASE.COMPANYDB.dbo.tblEmployee
I receive an Error:
*OLE DB provider "MSDASQL" for linked server... returned message
"[Microsoft][ODBC Driver Manager] Data source name not found and no
default
driver specified".
*Msg 7303, Level 16, State 1, Line 1
*Cannot initialize the data source object of OLE DB provider "MSDASQL" for
linked server...
Again, i'm using the SSMS from my workstation that has the DSN setup and
works fine when importing from access. I do NOT have the DSN or drivers on
the actual windwows 2003 Server where the SQL Sever 2005 instance is on.
Is that my promblem? Do I need the DSN on the actual windows 2003 server, or
should I be albe to use the DSN from my workstation?
Thanks in advanced!On Fri, 12 Jan 2007 14:11:04 -0800,
labsRcoolcommunitynospan@.discussions.microsoft.com wrote:
You will need to setup the driver and DSN on the SQL Server machine.
When you issue a query to a linked server, the client machine only knows
that it is talking to a SQL Server. The SQL Server then makes the request
to the remote data source. So the SQL Server has to have all the required
drivers, DSNs and privileges required to access the remote data source.
Darren Gosbell
SQL Server MVP

> Hi,
> Short version of question:
> For linked servers to ODBC DSN data sources, does the DSN have to be
setup
> on the same windows server as the sql server 2005 instance? Or is only
> requirment that the DSN is setup from the workstaing that is luanching
SSMS?
>
> Longer Background for question:
> I'm attempting to setup a linked server in SQL Server 2005 to an ODBC
> datasource which is Centura SQLbase database.
> On my workstation, I have a DSN setup with the odbc drivers to connect to
> the SQLbase db. The driver was "Centura SQLBase 3.60 32-bit Driver -NT &
> Win95"
> I can successfully import that tables from SQLBase using Access.
> I'm using the SQL Server Managment Studio from my desktop to connect to
the
> SQL 2005 Server on a Windows 2003 Server.
> When testing the Linked server by using a query, I use the following
syntax
> in a query in SSMS:
> SELECT LastName, FirstName FROM LINK2SQLBASE.COMPANYDB.dbo.tblEmployee
> I receive an Error:
> *OLE DB provider "MSDASQL" for linked server... returned message
> "[Microsoft][ODBC Driver Manager] Data source name not found and no[/vbcol
]
default[vbcol=seagreen]
> driver specified".
> *Msg 7303, Level 16, State 1, Line 1
> *Cannot initialize the data source object of OLE DB provider "MSDASQL"
for
> linked server...
> Again, i'm using the SSMS from my workstation that has the DSN setup and
> works fine when importing from access. I do NOT have the DSN or drivers
on
> the actual windwows 2003 Server where the SQL Sever 2005 instance is on.
> Is that my promblem? Do I need the DSN on the actual windows 2003 server,
or
> should I be albe to use the DSN from my workstation?
> Thanks in advanced!