>-----Original Message-----
>Thanks for your help. upon further investigation it was
>only happening when the added SQL enterprise manager to
a
>mmc console. We dreleted the MMC console and recreated
it
>and the problem has since gone away.
>
>Again thank you.
>
>Steve
>>-----Original Message-----
>>Normally this would happen when an application is
written
>to ask the user
>>for his db credentials every time it needs to log on to
>the database, and at
>>the same time has connection pooling enabled. Those two
>options are
>>incompatible.
>>
>>If the app in questions opens & closes many connections
>throughout it's
>>lifetime, you'll definitely want to have connection
>pooling enabled. You
>>might want to refer to online info such as
>>http://support.microsoft.com/default.aspx?scid=kb;en-
>us;169470 or
>>http://msdn.microsoft.com/library/default.asp?
>url=/library/en-
>us/odbc/htm/odbcodbc_connection_pooling.asp.
>>
>>SQL_DRIVER_NOPROMPT should be specified to your call to
>SQLDriverConnect
>>when connection pooling is enabled.
>>
>>Hope that helps.
>>
>>- Dave
>>
>>
>>"Steve" <sr@vincentinc.com> wrote in message
>>news:f17101c43d9d$1ca5e350$a101280a@phx.gbl...
>>> We have windows xp pro running on a laptop. I can
>connect
>>> to the server and our databases but when I try to
open a
>>> table I get the following message
>>>
>>>
>>> "[Microsoft][ODBC Driver manager] Only
>SQL_DRIVER_NOPROMPT
>>> is allowed when connection pooling is enabled"
>>>
>>> Does anybody know why this is happening. I
downloaded
>the
>>> mdac 2.7 sp1 and installed it. Still the same issue.
>>>
>>> thanks
>>>
>>>
>>
>>
>>.
>>
>.