Why do I get 80040E37 errors?

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 'AddNew'. Make sure it exists and that  its name is spelled correctly.    or    Microsoft OLE DB Provider for ODBC Drivers error '80040e37'  [Microsoft][ODBC Excel Driver] The Microsoft Jet database engine could  not find the object '<file>.xls'. Make sure the object exists and that  you spell its name and the path name correctly.    or    Microsoft OLE DB Provider for ODBC Drivers error '80040e37'  [Microsoft][ODBC Visual FoxPro Driver]File '<file>.dbf' does not exist.    or    Microsoft OLE DB Provider for ODBC Drivers error '80040e37'   [OpenLink][ODBC][Progress Server]** Table item does not exist or  cannot be accessed. (962)

 
Make sure that the table exists, and that the file exists in the path specified. If you are using a linked table, make sure that IUSR_machineName has permissions on the folder(s) hosting the 'remote' database files, and that the links are still pointing to a valid location... use Access' 'Linked Table Manager' to correct this situation. 
 

Microsoft OLE DB Provider for ODBC Drivers error '80040e37'  [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'object'.

 
Make sure that the object exists *as you spelled it*, that the owner name is specified in your query (e.g. dbo.tablename), that you are in the correct database (use databasename.ownername.tablename), and that the user in your ASP page (e.g. the UID or User ID in your connection string) has access to the object. If you are sure the object exists, see Article #2284. 
 
If you are trying to use a variable for a table name in a query, use dynamic SQL instead; for example: 
 

EXEC('SELECT columns FROM ['+ @table +']')

 
For more information on using dynamic SQL, see http://www.sommarskog.se/dynamic_sql.htm.... 
 

Microsoft OLE DB Provider for ODBC Drivers error '80040e37'   [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name '1'.

 
If you are trying to access a table, column or procedure name that begins with numerics, consider changing the table name. You should never name objects with numbers... however in the meantime, you can probably surround the object's name with [] square brackers to keep SQL Server quiet about it.