Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
BUG: No ADO Connection Error When Excel Workbook Is Not Found
Article ID: 316809 - View products that this article applies to.
This article was previously published under Q316809
When you attempt to make an ADO connection to a Microsoft Excel workbook, and the path and file name supplied in the ADO connection string are invalid, or the Excel file is missing, ADO does not generate an error message as expected when the connection fails.
You receive the following error message only when you attempt to open a recordset from the Excel workbook, and the error message does not clearly reveal the underlying cause of the problem:
This behavior occurs with both the Microsoft Jet OLE DB Provider 4.0 and the Microsoft Excel ODBC Driver.
Runtime error '-2147217865 (80040e37)': The Microsoft Jet database engine could not find the object 'Sheet1$'. Make sure the object exists and that you spell its name and the path name correctly.
To work around this issue, carefully verify not only the name and spelling of the source table (or tables) named in your query, but the name and spelling of the Excel path and file name supplied in your ADO connection string.
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
Steps to Reproduce the Problem
For additional information about the use of ADO with Excel, click the article number below to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/257819/EN-US/ )HOWTO: Use ADO with Excel Data from Visual Basic or VBA
Article ID: 316809 - Last Review: January 31, 2002 - Revision: 1.0