connection pooling for access jet connected ODBC tables?

Is 'connection pooling' available when using an access front end connecting
to sql server 2000 tables via jet connected ODBC (not an access
project/ado)?
If yes, is there any configurable options? if yes where? On client side or
server side or both?
any help is appreciated. Thanks.
You can configure ODBC connection properties in an Access mdb in
several places -- database options, query options, and in an ODBC
connection string (or DSN). However, I'm not sure about
resource/connection pooling. Access handles a lot of that under the
covers, spawning additonal connections when needed, say for opening a
complex form. What exactly are you trying to dos?
--Mary
On Mon, 24 May 2004 16:37:11 -0400, "djc" <noone@.nowhere.com> wrote:

>Is 'connection pooling' available when using an access front end connecting
>to sql server 2000 tables via jet connected ODBC (not an access
>project/ado)?
>If yes, is there any configurable options? if yes where? On client side or
>server side or both?
>any help is appreciated. Thanks.
>
sqlsql

connection pooling for access jet connected ODBC tables?

Is 'connection pooling' available when using an access front end connecting
to sql server 2000 tables via jet connected ODBC (not an access
project/ado)?
If yes, is there any configurable options? if yes where? On client side or
server side or both?
any help is appreciated. Thanks.You can configure ODBC connection properties in an Access mdb in
several places -- database options, query options, and in an ODBC
connection string (or DSN). However, I'm not sure about
resource/connection pooling. Access handles a lot of that under the
covers, spawning additonal connections when needed, say for opening a
complex form. What exactly are you trying to dos?
--Mary
On Mon, 24 May 2004 16:37:11 -0400, "djc" <noone@.nowhere.com> wrote:

>Is 'connection pooling' available when using an access front end connecting
>to sql server 2000 tables via jet connected ODBC (not an access
>project/ado)?
>If yes, is there any configurable options? if yes where? On client side or
>server side or both?
>any help is appreciated. Thanks.
>

connection manager in SQL 2005

I am writing a new Ole DB connection thru connection manager in Visual
Studio in SQL 2005. I used Native OLE DB\MS Jet 4.0 OLE DB Provider and I
specify a database path as d:\temp\database.dbf and set up the extended
proporties in advance tab to dBase 5.0 and when I click "test connection"
button, I gives me an error:
"Test connection failed because of an error in initializing provider.
'd:\temp\database.dbf ' is not a valid path. Mare sure that path name is
spelled correctly and that you are connected to the server on which the file
resided. "
I used browser button to get the file and path and therefore I am sure it is
correct. Can anyone please help to fix this problem? Many thanks.
Hi
"00EricClapton" wrote:

> I am writing a new Ole DB connection thru connection manager in Visual
> Studio in SQL 2005. I used Native OLE DB\MS Jet 4.0 OLE DB Provider and I
> specify a database path as d:\temp\database.dbf and set up the extended
> proporties in advance tab to dBase 5.0 and when I click "test connection"
> button, I gives me an error:
> "Test connection failed because of an error in initializing provider.
> 'd:\temp\database.dbf ' is not a valid path. Mare sure that path name is
> spelled correctly and that you are connected to the server on which the file
> resided. "
>
> I used browser button to get the file and path and therefore I am sure it is
> correct. Can anyone please help to fix this problem? Many thanks.
>
Are you sure that the file has the correct permissions and is not locked by
another application?
John

connection manager in SQL 2005

I am writing a new Ole DB connection thru connection manager in Visual
Studio in SQL 2005. I used Native OLE DB\MS Jet 4.0 OLE DB Provider and I
specify a database path as d:\temp\database.dbf and set up the extended
proporties in advance tab to dBase 5.0 and when I click "test connection"
button, I gives me an error:
"Test connection failed because of an error in initializing provider.
'd:\temp\database.dbf ' is not a valid path. Mare sure that path name is
spelled correctly and that you are connected to the server on which the file
resided. "
I used browser button to get the file and path and therefore I am sure it is
correct. Can anyone please help to fix this problem? Many thanks.Hi
"00EricClapton" wrote:

> I am writing a new Ole DB connection thru connection manager in Visual
> Studio in SQL 2005. I used Native OLE DB\MS Jet 4.0 OLE DB Provider and I
> specify a database path as d:\temp\database.dbf and set up the extended
> proporties in advance tab to dBase 5.0 and when I click "test connection"
> button, I gives me an error:
> "Test connection failed because of an error in initializing provider.
> 'd:\temp\database.dbf ' is not a valid path. Mare sure that path name is
> spelled correctly and that you are connected to the server on which the fi
le
> resided. "
>
> I used browser button to get the file and path and therefore I am sure it
is
> correct. Can anyone please help to fix this problem? Many thanks.
>
Are you sure that the file has the correct permissions and is not locked by
another application?
John

connection manager in SQL 2005

I am writing a new Ole DB connection thru connection manager in Visual
Studio in SQL 2005. I used Native OLE DB\MS Jet 4.0 OLE DB Provider and I
specify a database path as d:\temp\database.dbf and set up the extended
proporties in advance tab to dBase 5.0 and when I click "test connection"
button, I gives me an error:
"Test connection failed because of an error in initializing provider.
'd:\temp\database.dbf ' is not a valid path. Mare sure that path name is
spelled correctly and that you are connected to the server on which the file
resided. "
I used browser button to get the file and path and therefore I am sure it is
correct. Can anyone please help to fix this problem? Many thanks.Hi
"00EricClapton" wrote:
> I am writing a new Ole DB connection thru connection manager in Visual
> Studio in SQL 2005. I used Native OLE DB\MS Jet 4.0 OLE DB Provider and I
> specify a database path as d:\temp\database.dbf and set up the extended
> proporties in advance tab to dBase 5.0 and when I click "test connection"
> button, I gives me an error:
> "Test connection failed because of an error in initializing provider.
> 'd:\temp\database.dbf ' is not a valid path. Mare sure that path name is
> spelled correctly and that you are connected to the server on which the file
> resided. "
>
> I used browser button to get the file and path and therefore I am sure it is
> correct. Can anyone please help to fix this problem? Many thanks.
>
Are you sure that the file has the correct permissions and is not locked by
another application?
John