[thelist] ASP and MS Access Problem

[Ken Schaefer]

As someone mentioned, "unspecified errors" are one of the banes of using Jet

Suggestions:
a) make sure you are using the OLEDB Provider not the ODBC driver. A number
of fixes have been make to the OLEBD Provider that are not in the
corresponding ODBC driver
b) ensure that you have the latest MDAC (v2.8)
c) update to the latest Jet Service Pack (SP8) on top of MDAC 2.8
d) run the ComCheck tool from the Microsoft site to validate that you have
correct and matching versions of the MDAC .dlls

If you are still having issues, you are either using a debugging tool like
IISState, or move to MSDE.

Lastly, can I strongly recommend that you implement a custom 500-100 error
handler for your site (eg an ASP page). You can have that page log errors to
a DB, or email you the details of the error. Then you'll at least be aware of
when these errors are occurring, and how many times (as well as being able to
display a nice message to the end user). Depending on the number you get, you
can determine whether you need to build a business case to migrate to another
backend datastore.

Cheers
Ken

[1] http://support.microsoft.com/?id=239114
Jet Service Pack 8

[2] ComCheck:
http://www.microsoft.com/downloads/details.aspx?FamilyId=8F0A8DF6-4A21-4B43-B
F53-14332EF092C9&displaylang=en

[3] IISState:
http://www.iisfaq.com/default.aspx?view=P197

: -----Original Message-----
: From: thelist-bounces at lists.evolt.org
[mailto:thelist-bounces at lists.evolt.org] On
: Behalf Of Hershel Robinson
: Sent: Thursday, 10 February 2005 11:06 PM
: To: thelist at lists.evolt.org
: Subject: RE: [thelist] ASP and MS Access Problem
: 
: > > ---
: > > Provider error '80004005'
: > > Unspecified error
: > > /global.inc, line 7
: 
: > What's causing the problem is the record locking in MS
: > Access. It seems to
: > come and go because (I think) the record lock times out
: 
: Today there is no problem. The code simply works. My only conclusion is
that
: there was some sort of issue with the database and that it has been solved.
: We did compact and repair it 3 different times and I also deleted the DB
and
: copied a copy of into the directory where it belongs.
: 
: Nothing changed (not the code not the server) save the database, so it
seems
: logical that that was the culprit.
: 
: What precisely it was, however, I do not know.
: 
: Hershel