Dated: November 15, 2004
The Microsoft Access ODBC driver is one of the most unreliable drivers to use to interface with your MS Access database. We strongly discourage customers from using this driver and instead use the Jet OLEDB driver. Access ODBC has known problems in shared environments and Windows 2003/Access ODBC is a terrible combination. Jet OLEDB has better connection handling and connection pooling capabilities and has better overal reliability
Microsoft also discourages the use of Access ODBC as stated here: http://support.microsoft.com/kb/299973/EN-US/
Customers on Win7 encounted an Access ODBC driver crash a few hours ago (which we promptly fixed). However the only permanent solution to this issue is switching to Jet OLEDB or going for MS SQL.
The Microsoft Access ODBC driver is one of the most unreliable drivers to use to interface with your MS Access database. We strongly discourage customers from using this driver and instead use the Jet OLEDB driver. Access ODBC has known problems in shared environments and Windows 2003/Access ODBC is a terrible combination. Jet OLEDB has better connection handling and connection pooling capabilities and has better overal reliability
Microsoft also discourages the use of Access ODBC as stated here: http://support.microsoft.com/kb/299973/EN-US/
Customers on Win7 encounted an Access ODBC driver crash a few hours ago (which we promptly fixed). However the only permanent solution to this issue is switching to Jet OLEDB or going for MS SQL.