people follow up with a post like yours.
<RickHenry@discussions.microsoft.com> wrote:
>Sue,
>
>Thank you. What I failed to mention (didn't think it was relevant) was that
>somewhere along the line I installed Visual Studio 6.0 SP6. I was also having
>problems with the diagramming tools in SQL EM and read your other post
>regarding the version of mdt2df.dll that SP6 installs. So, I did get the MDAC
>Component Checker and indeed, the following DLLs:
>
>- Program Files\Common Files\system\ole db\OLEDB32.DLL
>- Program Files\Common Files\system\ole db\SQLOLEDB.DLL
>- System32\ODBC32.DLL
>- System32\odbccp32.dll
>- System32\SQLSRV32.DLL
>
>were found to be mismatched (all were newer versions than what was
>expected). I also had version 2.0.0.9586 of mdt2df.dll. I managed to get
>version 2.0.0.8908 from a colleague, renamed the newer version, and copied
>8909 into the right folder and that fixed this problem and the diagramming
>problem.
>
>Thanks again,
>
>Rick
>
>"Sue Hoegemeier" wrote:
>
>> In a lot of cases, this has been caused by MDAC issues. You
>> can check your MDAC installation with component checker
>> utility or reinstall the latest MDAC. You can download the
>> component check as well as MDAC installations from the links
>> at:
>>
http://msdn.microsoft.com/data/downloads/default.aspx >>
>> -Sue
>>
>> On Fri, 4 Mar 2005 11:31:08 -0800, "Rick Henry" <Rick
>> Henry@discussions.microsoft.com> wrote:
>>
>> >I just installed SQL Server 2000 Developer Edition on Windows XP SP1, then
>> >applied SQL Server SP3a. I registered my local database with EM and a
>> >database on another computer. The local registration is via Windows
>> >Authentication, the other via SQL Authentication. When I attempt any of the
>> >Open Table items from the context menu, I receive the following error:
>> >
>> >[Microsoft][ODBC Driver Manager] Only SQL_DRIVER_NOPROMPT is allowed when
>> >connection pooling is enabled.
>> >
>> >Doesn't matter which server, which database. Any ideas? I can open the
>> >tables fine from Visual Studio 6, Visual Studio.NET 2003 and via a query in
>> >Query Analyzer.
>>
>>
