RE: Upsizing Access 2000 to SQL Server 2000

From: Cindy Gross (cgross_at_online.microsoft.com)
Date: 03/10/04 

Date: Wed, 10 Mar 2004 17:15:58 GMT

It might be related to your MDAC version, older MDAC versions cannot
recognize named instances.

274383 ACC2000: Cannot Connect to Instance of SQL Server 2000
http://support.microsoft.com/?id=274383

Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Relevant Pages

  • Re: MDAC 2.1 and SQL Server 2000
    ... But are there any issues specific to using it with SQL Server 2000, ... other than its inability to handle named instances? ... > MDAC 2.1 is fraught with problems. ...
    (microsoft.public.data.ado)
  • RE: Linked Server and Server Registration
    ... It may have to do with your MDAC version. ... Can you make an OSQL connection ... from the SQL7 box to the SQL2K box? ... because older versions of MDAC don't know about named instances. ...
    (microsoft.public.sqlserver.connect)
  • Re: NT4 client connecting to SQL2000 named instance
    ... You need to be using at least MDAC ... to connect to named instances. ... connection is fine, can ping to the SQL Server. ... Connecting by TCP/IP network ...
    (microsoft.public.sqlserver.clients)
  • Re: Version of MDAC for SQL 2005?
    ... The minimum version for named instances is 2.71. ... I would recommend the ... latest MDAC 2.8 SP1. ... Check out this blog about SQL Native Client. ...
    (microsoft.public.sqlserver.clients)
  • 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)