Article has been viewed 7, times. Forum Software Powered by Vanilla. For more information on troubleshooting this error, see “Troubleshooting Data-Driven Unit Tests” http: If this does not help, you could try to use the name you gave to the ODBC connection as table name in the from. We tried changing drivers, configurations, etc.
|Date Added:||17 January 2006|
|File Size:||45.56 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
If the user does not have access to the file, the following error will appear when trying to Validate the connection or Preview the data. Move the file to the correct location.
Latest Additions Most Popular. Post as a guest Name. We tried changing drivers, configurations, etc.
The Microsoft Jet database engine could not find the object
The excel file is in the root folder of the project. Certainly saving the Excel spreadsheet as compatible a.
The first step on fixing this issue is to determine what connection is being made and then determine which ODBC driver to install or valid on the current machine or machine that is producing the error.
Make sure that the path name is spelled correctly and that you are connected microosoft the server on which the file resides.
If you want to get involved, click one of these buttons! For example, the column names in the above region would be named Name and PhoneNumber. In my example 42s022, it is the DefaultDir. Ben Breen 10 Article has been viewed 7, times. If the user trying to execute the integration does not have access to the file or the file path, there will be a list of errors pointing to the path being invalid.
To prevent spam users, you can only post on this forum after edcel, which is by invitation. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides. If using a query that is more advanced, the will return the following error when testing the Mocrosoft Connection: Make sure the object exists and that you spell its name and the path name correctly.
Let me know if this worked!
In this Discussion March JBuijs. I also added the file to the list of Deployment Items so the excel file is deployed to the out folder of the TestResults folder when the test is run. Make sure the object exists and that you spell its name and the path name correctly.
If the file does not exist mucrosoft folder specified, the error will point to the missing file name. An invalid odbc query syntax will generate a generic error regarding parameters or missing command.
SQL Native Client The file BuildAction is set to Content and Deploy is set to copy if newer. Go through the steps of validating the file location, user access to the file and then the driver versions.
Just a moment please
Each workstation where SmartConnect is running will have its own set of ODBC Drivers installed so while a map pointing to Excel on one machine works, it is possible that another machine does not have the same set of drivers loaded and the connection cannot be made. INFO Article not rated yet. The first restriction is that not more than one program must be using the Excel spreadsheet. Note that any data outside of the region will not be searchable.
For more information on troubleshooting this error, see “Troubleshooting Data-Driven Unit Tests” http: Here is the returned value: