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.
thanksNormally 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/defaul...kb;en-us;169470 or
_connection_pooling.asp." target="_blank">http://msdn.microsoft.com/library/d...on_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
>|||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...
connect[vbcol=seagreen]
SQL_DRIVER_NOPROMPT[vbcol=seagreen]
the[vbcol=seagreen]
>
>.
>|||Ok its back.
The Enterprise manager snap when used in a customized MMC
window... Very odd the default console that launches
with the Enterprise Manager icon works fine and only
fails intermittently with MMC. It is odd because it only
happens when I try reviewing all rows in a table. I can
change the structure of a table just not view the data?
>--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
written[vbcol=seagreen]
>to ask the user
>the database, and at
>options are
>throughout it's
>pooling enabled. You
>us;169470 or
>url=/library/en-
>us/odbc/htm/odbcodbc_connection_pooling.asp.
>SQLDriverConnect
>connect
open a[vbcol=seagreen]
>SQL_DRIVER_NOPROMPT
downloaded[vbcol=seagreen]
>the
>.
>
Showing posts with label connectto. Show all posts
Showing posts with label connectto. Show all posts
Thursday, March 22, 2012
connection pooling
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
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...b;en-us;169470 or
http://msdn.microsoft.com/library/de...n_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
>
|||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[vbcol=seagreen]
>when connection pooling is enabled.
>Hope that helps.
>- Dave
>
>"Steve" <sr@.vincentinc.com> wrote in message
>news:f17101c43d9d$1ca5e350$a101280a@.phx.gbl...
connect[vbcol=seagreen]
SQL_DRIVER_NOPROMPT[vbcol=seagreen]
the
>
>.
>
|||Ok its back.
The Enterprise manager snap when used in a customized MMC
window... Very odd the default console that launches
with the Enterprise Manager icon works fine and only
fails intermittently with MMC. It is odd because it only
happens when I try reviewing all rows in a table. I can
change the structure of a table just not view the data?
>--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[vbcol=seagreen]
>and the problem has since gone away.
>Again thank you.
>Steve
written[vbcol=seagreen]
>to ask the user
>the database, and at
>options are
>throughout it's
>pooling enabled. You
>us;169470 or
>url=/library/en-
>us/odbc/htm/odbcodbc_connection_pooling.asp.
>SQLDriverConnect
>connect
open a[vbcol=seagreen]
>SQL_DRIVER_NOPROMPT
downloaded
>the
>.
>
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
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...b;en-us;169470 or
http://msdn.microsoft.com/library/de...n_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
>
|||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[vbcol=seagreen]
>when connection pooling is enabled.
>Hope that helps.
>- Dave
>
>"Steve" <sr@.vincentinc.com> wrote in message
>news:f17101c43d9d$1ca5e350$a101280a@.phx.gbl...
connect[vbcol=seagreen]
SQL_DRIVER_NOPROMPT[vbcol=seagreen]
the
>
>.
>
|||Ok its back.
The Enterprise manager snap when used in a customized MMC
window... Very odd the default console that launches
with the Enterprise Manager icon works fine and only
fails intermittently with MMC. It is odd because it only
happens when I try reviewing all rows in a table. I can
change the structure of a table just not view the data?
>--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[vbcol=seagreen]
>and the problem has since gone away.
>Again thank you.
>Steve
written[vbcol=seagreen]
>to ask the user
>the database, and at
>options are
>throughout it's
>pooling enabled. You
>us;169470 or
>url=/library/en-
>us/odbc/htm/odbcodbc_connection_pooling.asp.
>SQLDriverConnect
>connect
open a[vbcol=seagreen]
>SQL_DRIVER_NOPROMPT
downloaded
>the
>.
>
Sunday, February 19, 2012
Connection between Active Directory and SQL server in VB6
Hello,
I have a couple VB6 projects in which I need to connect to the SQL
server. Due to security reason I wonder what is the best way to connect
to the SQL server.
I understand using Window Authentication is really a good way to
connect to the SQL server, however, if the # of users grow, I then have
to create a large number of users in the SQL server which is not
preferable.
Instead I wonder if the following is doable:
Can I create security group in Active Directory which allows certain
groups connect to only certain DBs in the SQL server? But how can I do
with the connectionstring when I connect to the SQL server in my VB6
code.
I really wish this is workable. If so, how can I do it? If not, is
there any other suggestion that I can make certain groups of ppl
connect only to certain DBs?
Thanks in advance. Your help would be greatly appreciated.
WandaHi,
kindly check books online> index> search for
Windows NT groups
thanks,
Jose de Jesus Jr. Mcp,Mcdba
Data Architect
Sykes Asia (Manila philippines)
MCP #2324787
"wandali@.rogers.com" wrote:
> Hello,
> I have a couple VB6 projects in which I need to connect to the SQL
> server. Due to security reason I wonder what is the best way to connect
> to the SQL server.
> I understand using Window Authentication is really a good way to
> connect to the SQL server, however, if the # of users grow, I then have
> to create a large number of users in the SQL server which is not
> preferable.
> Instead I wonder if the following is doable:
> Can I create security group in Active Directory which allows certain
> groups connect to only certain DBs in the SQL server? But how can I do
> with the connectionstring when I connect to the SQL server in my VB6
> code.
> I really wish this is workable. If so, how can I do it? If not, is
> there any other suggestion that I can make certain groups of ppl
> connect only to certain DBs?
> Thanks in advance. Your help would be greatly appreciated.
> Wanda
>|||Can't find it, can you please provide me a link? Any more help?
I have a couple VB6 projects in which I need to connect to the SQL
server. Due to security reason I wonder what is the best way to connect
to the SQL server.
I understand using Window Authentication is really a good way to
connect to the SQL server, however, if the # of users grow, I then have
to create a large number of users in the SQL server which is not
preferable.
Instead I wonder if the following is doable:
Can I create security group in Active Directory which allows certain
groups connect to only certain DBs in the SQL server? But how can I do
with the connectionstring when I connect to the SQL server in my VB6
code.
I really wish this is workable. If so, how can I do it? If not, is
there any other suggestion that I can make certain groups of ppl
connect only to certain DBs?
Thanks in advance. Your help would be greatly appreciated.
WandaHi,
kindly check books online> index> search for
Windows NT groups
thanks,
Jose de Jesus Jr. Mcp,Mcdba
Data Architect
Sykes Asia (Manila philippines)
MCP #2324787
"wandali@.rogers.com" wrote:
> Hello,
> I have a couple VB6 projects in which I need to connect to the SQL
> server. Due to security reason I wonder what is the best way to connect
> to the SQL server.
> I understand using Window Authentication is really a good way to
> connect to the SQL server, however, if the # of users grow, I then have
> to create a large number of users in the SQL server which is not
> preferable.
> Instead I wonder if the following is doable:
> Can I create security group in Active Directory which allows certain
> groups connect to only certain DBs in the SQL server? But how can I do
> with the connectionstring when I connect to the SQL server in my VB6
> code.
> I really wish this is workable. If so, how can I do it? If not, is
> there any other suggestion that I can make certain groups of ppl
> connect only to certain DBs?
> Thanks in advance. Your help would be greatly appreciated.
> Wanda
>|||Can't find it, can you please provide me a link? Any more help?
Connection between Active Directory and SQL server in VB6
Hello,
I have a couple VB6 projects in which I need to connect to the SQL
server. Due to security reason I wonder what is the best way to connect
to the SQL server.
I understand using Window Authentication is really a good way to
connect to the SQL server, however, if the # of users grow, I then have
to create a large number of users in the SQL server which is not
preferable.
Instead I wonder if the following is doable:
Can I create security group in Active Directory which allows certain
groups connect to only certain DBs in the SQL server? But how can I do
with the connectionstring when I connect to the SQL server in my VB6
code.
I really wish this is workable. If so, how can I do it? If not, is
there any other suggestion that I can make certain groups of ppl
connect only to certain DBs?
Thanks in advance. Your help would be greatly appreciated.
Wanda
Hi,
kindly check books online> index> search for
Windows NT groups
thanks,
Jose de Jesus Jr. Mcp,Mcdba
Data Architect
Sykes Asia (Manila philippines)
MCP #2324787
"wandali@.rogers.com" wrote:
> Hello,
> I have a couple VB6 projects in which I need to connect to the SQL
> server. Due to security reason I wonder what is the best way to connect
> to the SQL server.
> I understand using Window Authentication is really a good way to
> connect to the SQL server, however, if the # of users grow, I then have
> to create a large number of users in the SQL server which is not
> preferable.
> Instead I wonder if the following is doable:
> Can I create security group in Active Directory which allows certain
> groups connect to only certain DBs in the SQL server? But how can I do
> with the connectionstring when I connect to the SQL server in my VB6
> code.
> I really wish this is workable. If so, how can I do it? If not, is
> there any other suggestion that I can make certain groups of ppl
> connect only to certain DBs?
> Thanks in advance. Your help would be greatly appreciated.
> Wanda
>
|||Can't find it, can you please provide me a link? Any more help?
I have a couple VB6 projects in which I need to connect to the SQL
server. Due to security reason I wonder what is the best way to connect
to the SQL server.
I understand using Window Authentication is really a good way to
connect to the SQL server, however, if the # of users grow, I then have
to create a large number of users in the SQL server which is not
preferable.
Instead I wonder if the following is doable:
Can I create security group in Active Directory which allows certain
groups connect to only certain DBs in the SQL server? But how can I do
with the connectionstring when I connect to the SQL server in my VB6
code.
I really wish this is workable. If so, how can I do it? If not, is
there any other suggestion that I can make certain groups of ppl
connect only to certain DBs?
Thanks in advance. Your help would be greatly appreciated.
Wanda
Hi,
kindly check books online> index> search for
Windows NT groups
thanks,
Jose de Jesus Jr. Mcp,Mcdba
Data Architect
Sykes Asia (Manila philippines)
MCP #2324787
"wandali@.rogers.com" wrote:
> Hello,
> I have a couple VB6 projects in which I need to connect to the SQL
> server. Due to security reason I wonder what is the best way to connect
> to the SQL server.
> I understand using Window Authentication is really a good way to
> connect to the SQL server, however, if the # of users grow, I then have
> to create a large number of users in the SQL server which is not
> preferable.
> Instead I wonder if the following is doable:
> Can I create security group in Active Directory which allows certain
> groups connect to only certain DBs in the SQL server? But how can I do
> with the connectionstring when I connect to the SQL server in my VB6
> code.
> I really wish this is workable. If so, how can I do it? If not, is
> there any other suggestion that I can make certain groups of ppl
> connect only to certain DBs?
> Thanks in advance. Your help would be greatly appreciated.
> Wanda
>
|||Can't find it, can you please provide me a link? Any more help?
Subscribe to:
Posts (Atom)