Connect your Access 2013 Web Apps to SharePoint Lists

re: Connect your Access 2013 Web Apps to SharePoint Lists

FinMtl — Fri, 07 Sep 2012 10:16:01 GMT

I am unable to link to any SharePoint 2010 lists.

Are SharePoint 2010 lists supported?

What happens with Attachment fields?

re: Connect your Access 2013 Web Apps to SharePoint Lists

husonov — Thu, 06 Sep 2012 09:01:05 GMT

А мне нравиться

re: Connect your Access 2013 Web Apps to SharePoint Lists

jdowski@gmail.com — Mon, 03 Sep 2012 21:43:15 GMT

I'll be honest....the complicating factor in all of this from my point of view is the whole "web app" part. Correct me if I'm wrong but if I can move my native tables to either SP lists or SQL Azure tables, I will just post my Access FE to SharePoint and let user save a copy locally and then all my VBA code will still work and I can be linked to SP & SQL Azure ?? I am just playing around with Access/SharePoint 2010 now and creating web apps with all macros is not worth the effort. You got us to the web Microsoft but right now I'll stick with accdb format & all my VBA code I've written over the years.

re: Connect your Access 2013 Web Apps to SharePoint Lists

Jeff Cate — Fri, 31 Aug 2012 21:34:10 GMT

OK, I'll bite.

What if the SharePoint List is backed by a BCS External Content Type?

Will the Access Web App still be able to link to the SharePoint List?

You didn't specify that this wouldn't work in this post, but you did in answers to comments in a different post on this blog in August.

re: Connect your Access 2013 Web Apps to SharePoint Lists

Frederic Forest — Thu, 30 Aug 2012 12:31:02 GMT

Unless I'm mistaken, I think an important "gotcha" to mention is that since the new Access App are stored in Azure SQL instead of SharePoint lists, there's currently no way link two Access App together.

In other word, any table that has a remote chance to be reused by more than one Access App (i.e: Employee, Clients, Products, Assets, etc.) should be stored in an SharePoint list... where sadly it'll live only as a read-only object in the Access App.

To be honest, I'm still a bit puzzle on how to best use the new Access Apps because of these limitations. I was thrilled to learn that the new web DB would be backed by Azure which I personally believe to be the way of the future, but their present implementations have, in all respect, trun this into a real head-scratcher for me.