December 11, 2011

We’re pleased to announce publication of a new, first-of-its-kind, book on Access 2010 and SharePoint 2010.

UtterAccess members and administrators Ben Clothier and George Hepworth have teamed with Tim Runcie, a former Access MVP and current Project MVP, to write “Microsoft Access in a SharePoint World”. Tim’s company, Advisicon, is publishing the book.

MASW covers the essentials of working with Access 2010 and SharePoint 2010 to create data-driven, web-enabled databases that run in the browser from a SharePoint Site. The goal was to place Access in context within the SharePoint world, so the book includes additional discussions about the other wonderful tools SharePoint brings to the table: project management, document management, and team collaboration.

MASW assesses the suitability of Access as a web or client solution in a SharePoint world and shows how they are a natural fit.

MASW also addresses design considerations that may challenge experienced developers designing a Access web application for the first time.

MASW discusses using Access as a client to SharePoint data, which offers several advantages, such as working offline, seamless synchronization, and a high level of integration. The book also addresses the ramifications of choosing SharePoint as a data source and the difference between SharePoint's architecture and ODBC data sources.

Finally, MASW offers a brief glimpse into using SharePoint tools such as SharePoint Designer and InfoPath and manipulating the SharePoint object model with SOAP and JavaScript to make your Access on SharePoint databases more professional, and conclude with a discussion of security and deployment.

For more details or to buy the book, you can visit the Advisicon store store. Tim has offered discount of $10 off to the first 10 buyers—use coupon code "save10bucks".

Congrats Gents!

Gord (IMG:style_emoticons/default/cheers.gif)

dg_moore -

I'm so gratified to hear that the book was of use to you and more importantly that it was accessible. I'll say that it was NOT easy to keep it approachable, given the natural complexity of SharePoint + web architecture and the change of paradigm.

If I may, what would make the book better?