Opendatasource microsoft.jet.oledb.4.0

Next, check file permissions in Windows until you are blue in the face. Most likely this where the problem lies. And check not only your own permission, but the permissions for the SQL Server account. But most of all, you should ask yourself: am I really on the right solution. Even if you get it to work, you may run into the same issue on the next machine you migrate.

Or, if the issue is file permissions, it may start to fail again, because some gets the idea to harden the machine and removes permissions that seems to be out of place.

Maybe SSIS is an option. Maybe just an external program in C or Powershell that accesses both the database and Access. Finally, keep in mind that when Will says that it works on his side, all this tells you that this is overall possible. But Will does not see your machine, and don't know what issues that might be hiding there. Office Office Exchange Server. Not an IT pro? Resources for IT Professionals. Sign in. United States English. Ask a question. Quick access. Search related threads.

Remove From My Forums. Answered by:. Archived Forums. Sign in to vote. If I try and use Microsoft. I would be most appreciative for any assistance in sorting out this problem. Thank you. Friday, December 14, PM. I hope this helps someone out there. Marked as answer by infrazee Saturday, January 5, AM. Saturday, January 5, AM. Hi infrazee, Thanks for posting here. According to the error message above, have you installed Microsoft Access Database Engine?

Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown.

The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually.

Related 1. Hot Network Questions. Question feed. Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy. Provides ad hoc connection information as part of a four-part object name without using a linked server name. This documentation defines the basic syntax. When these options are not set, the default behavior does not allow for ad hoc access.

Define a linked server for any data sources accessed more than several times. You should use Windows Authentication whenever possible. The connection requirements for each provider are similar to the requirements for those parameters when creating linked servers.