Databases
StackOverflow2013
Postsdbo
POConnect to Access database that links to SharePoint lists using C#
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POConnect to Access database that links to SharePoint lists using C#
    text
    copied!<p>I have an window application in which I am trying to connect to a Access Database that has a table linking to a SharePoint list using OLEDB in C#</p> <p>My attempts:</p> <ol> <li>Use <strong>Access 2007 format</strong> for the database and <strong>Microsoft.ACE.OLEDB.12.0</strong> for the ConnectionString <ul> <li>Everything works perfectly okay, until there's one guy reports the error "<strong>The 'Microsolf.ACE.OLEDB.12.0' provider is not registered on the local machine</strong>"</li> <li>Check: he has Windows x86, Access 2003, but not 2007, and does not have "2007 Office System Driver: Data Connectivity Components" installed</li> <li>Really troublesome and time-consuming to get these installed (Company's machine)</li> </ul></li> <li>Use <strong>Access 2003 format</strong> for the database and <strong>Microsoft.ACE.OLEDB.12.0</strong> for the ConnectionString <ul> <li>Same error as the above. So I guess it is the "Microsoft.ACE.OLEDB.12.0" that causes the problem. But I don't know how to get it fixed.</li> </ul></li> <li>Using <strong>Access 2003 format</strong> for the database and <strong>Microsoft.Jet.OLEDB.4.0</strong> for the ConnectionString <ul> <li>Error on my machine: "<strong>Could not find installable ISAM</strong>" (I don't have Access 2003, but only Access 2007)</li> <li>His machine: works perfectly</li> </ul></li> </ol> <p>Please help me point out what I can do to fix this problem without having every one update their Office version to 2007 or having the application check people's Office version before connecting to the Access database.</p> <p>Thanks in advance.</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload