Just a quick note in a busy day to state unequivocally that my experience with Access Services in Access and SharePoint 2010 has been a huge success so far !!
I have now worked for several months on a conversion of a large application from Access 2007 with linked tables to a “Hybrid” app using Access 2010 with Access Services. Although there are not a lot of users (15+), these users are spread out World-Wide and are usually connecting through a VPN from outside a corporate office (including myself). Several have been working off-line successfully.
The performance is exceptional, since the users are effectively running everything off their local cache of the database. Updates to forms, reports and tables are quick and efficient. While major “batch” data updates take longer than if using a SQL backend, the performance of these MAJOR data upgrades is better than I expected and will only get better over time.
I have had quite a few people reach out to me asking about this technology. Most are asking about the issues involved in a “write-one-sell-many” scenario, where there are multiple indivdual databases who use the same exact Front-End code. I am working on that and hope to come with a logical solution soon.
But for “one-offs” where there is a single dedicated Custom application for one specific Audience within a business, I am having trouble finding a downside to Access Services. In fact I enjoy working in Access Service applications more than a traditional Access application, because changes CAN be propagated instantly to the users. And of course the Deployment story for Access Services “Hybrid” apps is a true “No-Brainer”.