Re: Microsoft OLE DB Provider for ODBC Drivers error '80040e37'


Ad

Advertisements

A

Andrew Bagley

Will do, thanks.
BJ Freeman said:
might try the access, IIS, and/or oledb group
Andrew Bagley said:
I have a website and test code using PWS on my local PC.

It has worked absolutely fine for about 2.5 years but I have suddenly get
the message:

"
Microsoft OLE DB Provider for ODBC Drivers error '80040e37'

[Microsoft][ODBC Microsoft Access Driver] The Microsoft Jet database engine
cannot find the input table or query 'Check_It'. Make sure it exists and
that its name is spelled correctly.

"

The table 'Check_It' does exist in the Access database. I restored the
database to the previous day but still have the problem. I wondered if it
was some kind of DSN corruption so deleted my DSN, rebooted and recreated
the DSN, but still have the problem.

The page producing the error hasn't been changed for about 18 months. The
error also occurs on other pages accessing the database so it looks like it
isn't an ASP problem but is some kind of DSN or ODBC driver problem. The
Access database has 2 large tables attached each with about 2 million
records although the table 'Check_It' is not one of the attached tables and
only has 1 record. I also wonder if it is running out of steam or timing
out. I'm using an Athlon 1600+ processor with a 6 month old Seagate ATA 100
drive.

I'd be grateful for any advice on dealing with this.

Thanks

Andrew
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top