Client connectivity to SQL Server 2005

Hello!
I am developing an application that will connect to a SQL Server 2005
(including Analysis Services) database. The SQL database will reside on
a server, not on the client my app will be installed on.
I am creating a setup program and I guess that I need to redistribute
the client connectivity components in mysetup program. The problem is
that I don't know which files contains the client connectivity. As my
software might be downloaded from the internet, I need a fool-prof
solution.
I've searched msdn, but not found any useful info regarding this
delicate matter.
TIA
Clarkieclarkbones@.rocketmail.com schrieb:
> Hello!
> I am developing an application that will connect to a SQL Server 2005
> (including Analysis Services) database. The SQL database will reside on
> a server, not on the client my app will be installed on.
> I am creating a setup program and I guess that I need to redistribute
> the client connectivity components in mysetup program. The problem is
> that I don't know which files contains the client connectivity. As my
> software might be downloaded from the internet, I need a fool-prof
> solution.
> I've searched msdn, but not found any useful info regarding this
> delicate matter.
>
> TIA
> Clarkie
For general SQL Server connectivity (pre Sql Server 2005) you need to
link them to the MDAC Download Site available to the public:
http://www.msdn.microsoft.com/data/mdac/
For SQL Server 2005 Client connectivity you need to link them to the
SQL Native Client
http://www.msdn.microsoft.com/data/...ve/default.aspx
btw: On these sites you may also find information on howto include these
packages direcly into your own software and if its allowed to do so or not.
hth
Stefka

Client / server data retrieval

I have a Client/Server application where the Client is MS-ACCESS 2000 and
the Server is SQL SERVER 2000. The two entities reside on separate
platforms(Machines). The server contains tables in which some
columns(fields) are encrypted and must therefore be decrypted to view them.
This works great when using UDF procedures to do the encrypting/decrypting.
My question is: How can I access the data either encrypted or decrypted from
the MS-ACCESS client using SQL via an ODBC connection. The normal data
transfer between the Client/Server is achieved using a Linked Database. The
normal SQL's utilizing the UDF's on SQL server do not seem to be accessible
using the normal MS-ACCESS Sql's.
Thanks in advance for any helpful suggestions...
Hans Munkwitz
Pace Data Systems, Inc.
Hans,
You 'should' still be able to use the UDF to encrypt/decrypt the data. You
may need to create views that allow the decryption -but if the security
isn't done correctly, then any protection provided by encrypting the data
could be lost.
Please post the entire SELECT query, table definitions (DDL), and some
sample data.
See: http://www.aspfaq.com/5006
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Hans Munkwitz" <msnews.microsoft.com> wrote in message
news:u8ytHKWGHHA.2456@.TK2MSFTNGP06.phx.gbl...
>I have a Client/Server application where the Client is MS-ACCESS 2000 and
> the Server is SQL SERVER 2000. The two entities reside on separate
> platforms(Machines). The server contains tables in which some
> columns(fields) are encrypted and must therefore be decrypted to view
> them.
> This works great when using UDF procedures to do the
> encrypting/decrypting.
> My question is: How can I access the data either encrypted or decrypted
> from
> the MS-ACCESS client using SQL via an ODBC connection. The normal data
> transfer between the Client/Server is achieved using a Linked Database.
> The
> normal SQL's utilizing the UDF's on SQL server do not seem to be
> accessible
> using the normal MS-ACCESS Sql's.
> Thanks in advance for any helpful suggestions...
>
> --
> Hans Munkwitz
> Pace Data Systems, Inc.
>