Re: Connecting to an Access database
- From: brian.lukoff@xxxxxxxxx
- Date: 18 Sep 2006 09:44:56 -0700
This may be a silly question, but does a corrupted MDB file just mean
that I won't be able to open the file (or will receive errors when I
do), or could I be left with a database that can be read without errors
but that contains incorrect values? (If so, would the user that caused
such a problem have received an error from their web browser when it
occurred?)
Mike Brind wrote:
brian.lukoff@xxxxxxxxx wrote:
In a KB article (http://support.microsoft.com/kb/299974/), it is
stated:
"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....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."
In basic usage (just simple retrieving of rows or tables, and executing
INSERT or UPDATE statements), what "unpredictable results" are possible
that could affect data integrity?
You won't get too many problems with SELECT statements, apart from Jet
eventually running out of resources in a high-user environment. Having
said that, I have an Access 2000 db humming along quite nicely serving
up over 1/2 a million recordsets a month, and has done so for a few
years with no problems.
INSERTS and UPDATES are the potential killer for Jet. Incomplete
operations could leave you with a corrupted mdb file.
More info:
http://databases.aspfaq.com/database/what-are-the-limitations-of-ms-access.html
--
Mike Brind
.
- Follow-Ups:
- Re: Connecting to an Access database
- From: Mike Brind
- Re: Connecting to an Access database
- References:
- Connecting to an Access database
- From: brian . lukoff
- Re: Connecting to an Access database
- From: Mike Brind
- Connecting to an Access database
- Prev by Date: Re: Date Range lookup between tables in asp 2.0
- Next by Date: Re: Connecting to an Access database
- Previous by thread: Re: Connecting to an Access database
- Next by thread: Re: Connecting to an Access database
- Index(es):
Relevant Pages
|