Re: SQL Server client versions

From: Mike Epprecht (SQL MVP) (mike_at_epprecht.net)
Date: 09/23/04


Date: Thu, 23 Sep 2004 06:45:04 -0700

Hi

Not 2005. 2005 is in beta and the client drivers will still change. SQL 6.0
to SQL 2000 work with MDAC 2.8 and below.

You may want to look at OLE DB as ODBC is outdated.

Regards
Mike

"Paul Power" wrote:

> Hi Mike,
>
> thanks, I definitly will be testing against &, 2000
> and 2005.
>
> So if I'm following all this correctly - if I build my
> application to use ODBC and install the latest MDAC on
> my client test machine I should be able to connect to
> SQL 7, 2000 and 2005 servers ?
>
> cheers,
>
> Paul
>
>
> On Thu, 23 Sep 2004 04:55:03 -0700, Mike Epprecht (SQL MVP)
> <mike@epprecht.net> wrote:
>
> > Hi
> >
> > MDAC v2.1 to v2.8 are all compatible as they use the MDAC v1.5 binary
> > object
> > DLL.
> > MDAC that ships wil SQL 2005 is v9.0, and is a side-by-side installation
> > with prior versions.
> >
> > You need to test to be 100% sure that you are not relying on
> > functionality
> > supplied by a bug. In general, I have never had a problem.
> >
> > Regards
> > Mike
> >
> > "Paul Power" wrote:
> >
> >>
> >> Hi all,
> >>
> >> I am currently porting some software to support SQL Server.
> >> The software will act as a client and I'm having no problem
> >> with that.
> >>
> >> My problem is that I currently build and test my application
> >> with the SQL Server 7 client. I don't ship the client on the
> >> assumption that the customer has it already if they have a SQL
> >> Server instance to connect to :-) However, what if the customer
> >> has a SQL Server 2000 or 2005 client ? How confident can I be
> >> that my software will work ?
> >>
> >> Any ideas, suggestions etc are much appreciated. Ideally I'd
> >> love to find something like the Oracle client/server
> >> compatability matrix where they state which clients have been
> >> tested with which servers and vice versa.
> >>
> >> thanks in advance,
> >>
> >> Paul Power
> >>
> >>
> >> --
> >> Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
> >>
>
>
>
> --
> Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
>



Relevant Pages

  • Re: Word mail merge with foxpro
    ... I did come across an article about using FoxPro with earlier Word ... > The dbf is not attached to a dbc as I have always found that more ... The MDAC 2.5 installaion helpded greatly I am just a bit worried ... >> is to switch on ODBC logging in the ODBC administrator. ...
    (microsoft.public.word.mailmerge.fields)
  • Re: Any idea about this error?
    ... > What is occring when you get the error processing or querying or what? ... To migrate the repository to SQL Right ... > datasource if you have chosen to use an ODBC driver. ... > MDAC you could have a mismatched version of the dlls. ...
    (microsoft.public.sqlserver.olap)
  • Re: ODBC call failed - weird behavior
    ... It could be an MDAC issue. ... checker on a machine where the app works and another machine ... You could also turn on ODBC tracing then reproduce your ... >ODBC tables to connect to an SQL Server 2000. ...
    (microsoft.public.sqlserver.odbc)
  • Re: ODBC Test
    ... Windows Server 2003 comes with MDAC 2.8. ... > I just got a new Windows Server 2003 on Itanium 64bit platform. ... except ODBC access. ... use ODBC Test to troubleshoot this connection problem. ...
    (microsoft.public.data.odbc)
  • Re: Probleme beim Erstellen eines Setup
    ... > auch nicht mehr im MDAC 2.8. ... > "This release does not include Microsoft Jet, ... > Provider or ODBC driver, the Desktop Database ODBC Drivers, or the ...
    (microsoft.public.de.german.entwickler.dotnet.vb)