Re: Connection to SQL Server on Vista


"William Vaughn" <billvaNoSPAM@xxxxxxxxx> wrote in message
news:AA97C19B-828E-435A-B7B9-A87F5C84CD9A@xxxxxxxxxxxxxxxx

http://staff.develop.com/bobb/weblog/PermaLink.aspx?guid=a7f64240-60ae-4031-9580-05bdc10e2c93

--


You missed the point. <g>

1) The OP is using SQL Server 2000 not 2005.
( and we don't know if he is using ADO or DAO - but that's beside the
point.)
2) The article itself is inaccurate because is says:
" ... Instead, the current components of MDAC (2.8 SP1?) will ship as part
of the Windows family of operating systems."
Note the question mark. The components that are shipped with Vista are in
fact functionally equivalent to "MDAC 2.8 SP1", but are slightly different
build versions and are now called "Data Access Components" (DAC).

Microsoft and others are a bit careless in their terminology here. For an
obvious reason. We all know the "DAC" is "MDAC". The various development
groups know it is "MDAC". We all call it "MDAC" - but marketing (?) wants it
called "DAC".

In addition just telling someone to change providers with a working app is
irresonsible without also alerting them to the possible problems with
earlier SQL Server versions:
http://msdn2.microsoft.com/en-us/library/ms131035.aspx

"SNAC" is just what "MDAC" might have included if there had been a newer
"MDAC", but instead we now have "DAC" and "SNAC". MS is no longer going to
supply "universal data access" packages, every datasource will supply its
own providers. I guess it won't be long before the Office team ships their
own providers so we will have SNAC, DAC (er, MDAC), and "ONAC". And soon
"OraNAC", "MySQLNAC", and "Patty-NAC". <g>

-ralph



.

Relevant Pages

  • Re: Sql Server Agent (2000) erroring out on DTS Packages
    ... DTSRun: Package execution complete. ... and a problem with a missing MDAC dll. ... On Sql Server 7, this was SQLAgentCmdExec. ... Specified driver could not be loaded due to system error 126 (MERANT MSSS ...
    (microsoft.public.sqlserver.dts)
  • Re: Enterprise Library - DataAccessApplicationBlock - MySql/DB2
    ... The fact that you set parameters differently for different providers isn't ... Oracle or Microsoft told me "We don't like the way you did that", ... ISDATE doesn't produce the same results in both Sql Server ... and Oracle both have a ton of specific features that others don't have. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Any help here???
    ... > start looking for things that are non standard (like having MDAC installed). ... > Format your drive, do a new/clean install of XP, and go from there. ... >>> data provider is optimized for SQL Server. ... >>> I've never had any SQL Server connectivity problems since I've switch to ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: SQL server Login connection failed sqlstate 28000 sql server e
    ... mdac 2.8 - ran the mdac checker and everything is fine ... and reconnect to the sql server using odbc - dsn connection. ... Now when we make mods to the database, reconnect, then we get that error. ... please download Component Checker from the link below to make sure ...
    (microsoft.public.sqlserver.odbc)
  • Re: Help Please Wit Error
    ... Occasionally I receive the error you are mentioning when the SQL Server ... I have had to completely remove the MDAC and re-install it as well ... see an example of the connection string you are using. ... Please install Microsoft Data Access Components ...
    (microsoft.public.dotnet.csharp.general)