Darvish Shadravan, our course instructor for our set of video tutorials on the methods available to electronic forms designers for designing forms for SharePoint Server 2013 claims Access 2013 is now the best method available for using no code development techniques to successfully deliver on forms creation objectives.
Certainly this is a big change from SharePoint Server 2007 and 2010. For both of these computing enivronments, InfoPath was the best choice available this task. But Darvish makes his claim in a video tutorial titled “SharePoint and Access 2013”, which is included in out video tutorial set, SharePoint 2013: Enterprise Forms DVD. This set is available for purchase for local viewing by individuals and/or groups.
Access 2013 offers developers a method to quickly develop cloud apps, which can be run in SharePoint 2013. Unfortunately, InfoPath 2013 does not offer this same capability. Darvish explains “Access 2013 has hooks into SharePoint 2013 that we haven’t had before, as the result of the app model”. Unfortunately, Darvish points out, Infopath is still built around the “legacy model of doing things inside of SharePoint. It does not use the clud app model. It publishes forms to a list. It uses well known technologies like XML, and, in many cases, that’s still fine. But there are still a number of really great advantages of moving forms to the new cloud app model.”
Other advantages of opting to use Access 2013 to build electronic forms for processing in a SharePoint 2013 environment include the ability to “quickly build app templates”, to repurpose existing Access content, and, finally, to develop apps to be used in SharePoint by users outfitted with web browsers as their universal clients.
Access apps work fine either on premises, or for SharePoint Online in the cloud. Darvish does note one important consideration. If apps are to be developed by forms designers, and not by SharePoint administrators, than the development process will be much easier if SharePoint Online is chosen for the computing platform, rather than SharePoint Server 2013, on premises.
© Rehmani Consulting, Inc. & Ira Michael Blonder, 2013 All Rights Reserved