<div>
I am not sure why you are trying to access the database through your SQL Logon. &nbsp;The access database is not part of the SQL database and will not recognize the security of SQL. &nbsp;<br />
From my experience I would do one of two things. I would either bring all of my windows authentication into SQL Secutiry and set it up there and assign appropriate permissions to the databases under SQL that you have linked. Or as a second option (which might be more time consuming and also create more problems with your queries), bring all of your databases from Access into SQL so that they are not split between the two.<br />
A third more controversial option would be to bring all of the databases into SQL and convert all of your queries into SQL Views and Stored Procedures to end up creating an Access Data Project instead.<br />
&nbsp;<br />

</div>


<div>
None of those is an option for me as I do not &quot;own&quot; the Access database.. I just need data from it periodically when the owners update it. &nbsp;SQL server supports linking to an access database out of the box, I just can't get the settings correct. &nbsp;
</div>


<div>
<div class="content wysiwyg-content">
I have an SQL database which is linked to an access database. &nbsp;I have the link all setup which works in the server management studio when I log on using Windows Authentication but not when I log on using SQL Server Authentication. &nbsp;I assume this is due to folder permissions but I can't figure out how to setup the link so that I can get this to work. &nbsp;I get the following error when trying to access the table using SQL Server Authentication:<br />
<br />
The OLE DB provider &quot;Microsoft.Jet.OLEDB.4.0&quot; for linked server &quot;ACCESSDB&quot; reported an error. Authentication failed. Cannot initialize the data source object of OLE DB provider &quot;Microsoft.Jet.OLEDB.4.0&quot; for linked server &quot;ACCESSDB&quot;.<br />
<br />
Then when I try to assign an impersonated ID to is I get <br />
<br />
OLE DB provider &quot;Microsoft.Jet.OLEDB.4.0&quot; for linked server &quot;ACCESSDB&quot; returned message &quot;Cannot start your application. The workgroup information file is missing or opened exclusively by another user.&quot;.
</div>
</div>


I have an SQL database which is linked to an access database.  I have the link all setup which works in the server management studio when I log on using Windows Authentication but not when I log on using SQL Server Authentication.  I assume this is due to folder permissions but I can't figure out how to setup the link so that I can get this to work.  I get the following error when trying to access the table using SQL Server Authentication:

The OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "ACCESSDB" reported an error. Authentication failed. Cannot initialize the data source object of OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "ACCESSDB".

Then when I try to assign an impersonated ID to is I get 

OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "ACCESSDB" returned message "Cannot start your application. The workgroup information file is missing or opened exclusively by another user.".

SQL Server linked to Access Database table problem

Microsoft SQL Server 2008 is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning. Major improvements include the  Always On technologies and support for unstructured data types.

Microsoft SQL Server 2008

SQL (Structured Query Language) is designed to be used in conjunction with relational database products as of a means of working with sets of data. SQL consists of data definition, data manipulation, and procedural elements. Its scope includes data insert, query, update and delete, schema creation and modification, and data access control.