So I have a custom list in SharePoint 2010 with 10 or so columns. I then link the list within MS Access 2007. Works just fine until I try adding a look-up or people-type column to the list, then the next time I refresh the MS Access table link I get the following message:
Error: "The Microsoft datbase engine cannot find the object 'TMP%.MAU@'. Make sure the object exists..." blah, blah, blah
Then of course, the data is inaccessible through MS Access after that point. If I then go back to SharePoint and delete the new column, it starts working again in MS Access.
I can add any other kind of columns, and it works fine.
What gives? Is there s limit to the number of people columns you can have in an MS Access linked SharePoint List?
========
So I deleted all of the data from the sharepoint list, and the error went away, no matter how many people columns I added. But as soon as you add a single record back in, the error returns... :(
Found the solution.
The error stems from a "hidden" threshold limit set within SharePoint Central Administration that limits the number of lookup columns returned within a given query. This means linked MS Access lists to SharePoint would be limited as well, hence the error. The problem is MS Access 2007 doesn't give you a nice error message to explain this to you, whereas SharePoint 2010 does.
The fix is simple--just bump up the threshold and you're good to go. Here is how: enter link description here