Any Way to Force Default Connection to SQLOLEDB Driver?

After upgrading machines to Windows 2003 SP1, we are noticing strange
behavior of recordsets in Access 2003. There are many similar reports on
the Internet, and it appears that these trace to the fact that the default
connection in Access is not using the SQLOLEDB driver. Apparently the ODBC
driver is not very stable, and the SQLOLEDB driver is what we want to be
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/information-technology/14022-any-way-force-default-connection-sqloledb.html
using. Is there a way to force Access to use SQLOLEDB for its *default*
connection, or do we just have to use our own custom connection if we want
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=14022
to control driver selection?

My programmer had the concern that even if we could force the default
connection to use OLEDB that this might cause the bound forms to start
behaving unpredictably.

Any advice on how to get Access using SQLOLEDB across the board is
appreciated.

--
Will

 
Do share your immediate thoughts or reactions on this issue? We value your views! Login Now! or Sign Up Today! to share your views with us.. Gurfateh!

Will wrote:
> After upgrading machines to Windows 2003 SP1, we are noticing strange
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=14022
> behavior of recordsets in Access 2003. There are many similar
> reports on the Internet, and it appears that these trace to the fact
> that the default connection in Access is not using the SQLOLEDB
> driver. Apparently the ODBC driver is not very stable, and the
> SQLOLEDB driver is what we want to be using. Is there a way to
> force Access to use SQLOLEDB for its *default* connection, or do we
> just have to use our own custom connection if we want to control
> driver selection?
>
> My programmer had the concern that even if we could force the default
> connection to use OLEDB that this might cause the bound forms to start
> behaving unpredictably.
>
> Any advice on how to get Access using SQLOLEDB across the board is
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=14022
> appreciated.

You can't. And there is nothing "unstable" about the ODBC driver.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

If your are talking Access front end connecting to SQL Server, you have two
ways: with *.mdb, you connect via ODBC, no other option; with *.adp, you use
SQL OLEDB, no other option, agian.

"Will" wrote in message
news:OBd24PUsGHA.904@TK2MSFTNGP03.phx.gbl...
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=14022
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=14022
> After upgrading machines to Windows 2003 SP1, we are noticing strange
> behavior of recordsets in Access 2003. There are many similar reports
> on
> the Internet, and it appears that these trace to the fact that the default
> connection in Access is not using the SQLOLEDB driver. Apparently the
> ODBC
> driver is not very stable, and the SQLOLEDB driver is what we want to be
> using. Is there a way to force Access to use SQLOLEDB for its *default*
> connection, or do we just have to use our own custom connection if we want
> to control driver selection?
>
> My programmer had the concern that even if we could force the default
> connection to use OLEDB that this might cause the bound forms to start
> behaving unpredictably.
>
> Any advice on how to get Access using SQLOLEDB across the board is
> appreciated.
>
> --
> Will
>
>