Article ID: 299974 - View products that this article applies to.
This article was previously published under Q299974
Advanced: Requires expert coding, interoperability, and multiuser skills.
For a Microsoft Access 2000 version of this article, see 299973
When you need unlimited users, 24x7 support, and ACID transactions, we recommend that you use Microsoft SQL Server with Internet Information Server (IIS). Although Active Server Pages (ASP) works with any OLE DB and ODBC-compliant database, IIS has been extensively tested and is designed to work with Microsoft SQL Server with high transaction traffic and unlimited users that can occur in an Internet scenario.
Note "ACID" is an acronym for the four properties of transaction-processing systems: Atomicity, Consistency, Isolation, Durability.
ASP also supports using the Microsoft Jet database engine as a valid data source. The Access ODBC Driver and Microsoft OLE DB Provider for Microsoft Jet are not intended to be used with high-stress, high-concurrency, 24x7 server applications, such as web, commerce, transactional, messaging servers, and so on.
When you run Microsoft Jet in an IIS environment, it is recommended that you use the native Jet OLE DB Provider in place of the Microsoft Access ODBC driver. The Microsoft Access ODBC driver (Jet ODBC driver) can have stability issues due to the version of Visual Basic for Applications that is invoked because the version is not thread safe. As a result, when multiple concurrent users make requests of a Microsoft Access database, unpredictable results may occur. The native Jet OLE DB Provider includes fixes and enhancements for stability, performance, and thread pooling (including calling a thread-safe version of Visual Basic for Applications).
Both the ODBC driver and OLE DB Provider provide a wrapper around the Microsoft Jet database engine, which provides the core functionality of both the Access ODBC driver and Jet OLE DB Provider. While Microsoft Jet is consciously (and continually) updated with many quality, functional, and performance improvements, it was not intended (or architected) for the high-stress performance required by 24x7 scenarios, ACID transactions, or unlimited users, that is, scenarios where there has to be absolute data integrity or very high concurrency. Microsoft has performed very robust Multi-User/Stress scenarios that are designed to verify functionality in the appropriate usage space of Microsoft Jet, and addresses any issues that may be revealed.
You can obtain the latest OLE DB provider for Microsoft Jet from the following sources:
For additional information about using the Microsoft Jet database engine and the native Jet OLE DB Provider, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/191754/ )How to open a secured Access database in ADO through OLE DB
172403Information about Microsoft Jet and the native Jet OLE DB Provider can also be found in the following documentation:
(http://support.microsoft.com/kb/172403/ )How to use ADO with Visual Basic
Article ID: 299974 - Last Review: December 3, 2007 - Revision: 7.2