Registry error with ADO access to Access 2k3

Hi, all! Still working on the Access 2k3 database corruption issue...
Using plain ol' ASP with Access 2k3 database on the back end (hosted offsite
with GoDaddy.com).

It seems regularly this error is occuring when any attempt at accessing data
is made:

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[Microsoft][ODBC Microsoft Access Driver]General error Unable to open
registry key 'Temporary (volatile) Jet DSN for process 0x43c0 Thread 0x34a0
DBC 0x9e2c73c Jet'.

This occurs on any ADO call. Additionally, when I download the online
database, there is inevitably some record corruption in one or more tables
in the database. The online provider claims to be using Jet version
4.0.8618.0. Uploading a backup of the database will cause the error to go
away, but that does little if new data has been applied.

Suggestions?
Thanks!
Jack

Re: Registry error with ADO access to Access 2k3

"Jack Black" wrote in message
news:Ooq58PJTHHA.3592@TK2MSFTNGP06.phx.gbl...
> Hi, all! Still working on the Access 2k3 database corruption issue...
> Using plain ol' ASP with Access 2k3 database on the back end (hosted
> offsite with GoDaddy.com).
>
> It seems regularly this error is occuring when any attempt at accessing
> data is made:
>
> Microsoft OLE DB Provider for ODBC Drivers error '80004005'
>
> [Microsoft][ODBC Microsoft Access Driver]General error Unable to open
> registry key 'Temporary (volatile) Jet DSN for process 0x43c0 Thread
> 0x34a0 DBC 0x9e2c73c Jet'.
>
> This occurs on any ADO call. Additionally, when I download the online
> database, there is inevitably some record corruption in one or more tables
> in the database. The online provider claims to be using Jet version
> 4.0.8618.0. Uploading a backup of the database will cause the error to go
> away, but that does little if new data has been applied.
>
> Suggestions?
> Thanks!
> Jack
>
>


Use a dsn-less connection and you will have one less thing to worry about.

e.g.:

Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=C:\yourfolder\yourdb.mdb;Persist Security Info=False





--
John Blessing

http://www.LbeHelpdesk.com - Help Desk software priced to suit all
businesses
http://www.room-booking-software.com - Schedule rooms & equipment bookings
for your meeting/class over the web.
http://www.lbetoolbox.com - Remove Duplicates from MS Outlook, find/replace,
send newsletters

Re: Registry error with ADO access to Access 2k3

"Jack Black" wrote in message
news:Ooq58PJTHHA.3592@TK2MSFTNGP06.phx.gbl...
> Hi, all! Still working on the Access 2k3 database corruption issue...
> Using plain ol' ASP with Access 2k3 database on the back end (hosted
> offsite with GoDaddy.com).
>
> It seems regularly this error is occuring when any attempt at accessing
> data is made:
>
> Microsoft OLE DB Provider for ODBC Drivers error '80004005'
>
> [Microsoft][ODBC Microsoft Access Driver]General error Unable to open
> registry key 'Temporary (volatile) Jet DSN for process 0x43c0 Thread
> 0x34a0 DBC 0x9e2c73c Jet'.
>
> This occurs on any ADO call. Additionally, when I download the online
> database, there is inevitably some record corruption in one or more tables
> in the database. The online provider claims to be using Jet version
> 4.0.8618.0. Uploading a backup of the database will cause the error to go
> away, but that does little if new data has been applied.
>
> Suggestions?

In my reply to your previous query, I oofered this link:
http://support.microsoft.com/default.aspx/kb/303528, which would have
porvided a link to this:
http://support.microsoft.com/default.aspx/kb/303528, which includes this:

"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)."

System DSNs use ODBC to get to OLEDB.

Use the (DSN-Less) OLEDB connection string suggested by John.

--
Mike Brind