Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

2010 share point saturday deck enterprise office applications


Published on

  • Be the first to comment

  • Be the first to like this

2010 share point saturday deck enterprise office applications

  1. 1. Enterprise Friendly Office Applications<br />Garry Stewart – Ajilon<br />
  2. 2. Who are you?<br />Garry Stewart<br /><br /><br />
  3. 3. What is an “Enterprise Friendly Application”?<br />Provides a home for a concept within a business<br />Plays nice with others<br />Allows IT to do their job<br />
  4. 4. Application Maturity Model<br />Opportunistic<br />Tactical<br />Strategic<br />
  5. 5. Why can’t everything be strategic?<br />
  6. 6. How can we have our cake & eat it?<br />In scope:<br />Reduce the cost of tactical systems<br />Empower the end users<br />Out of scope:<br />Encourage an environment where users feel comfortable approaching IT with their business needs<br />Educate and train users on how they can solve their own issues using the tools provided by IT<br />
  7. 7. How can SharePoint 2010 help?<br />SharePoint provides tools for the 3 main data concepts that users are familiar with<br />Documents<br />Form Libraries & InfoPath<br />Document Libraries & Word/PDF etc.<br />Reporting Services/ PerformancePoint Reports<br />Visio Services<br />Spread sheets<br />Excel Services<br />Document Libraries & Excel<br />Tables<br />Access Services<br />SharePoint List based applications<br />You are here<br />
  8. 8. What is Access Services?<br />Think InfoPath Form Services but for Access<br />Allows hosting of Access tables, reports and forms in SharePoint<br />Let’s you look at Access Forms & Reports through a browser without having Access on the client<br />
  9. 9. So what is it doing?<br />Generates a new SharePoint Site for your application<br />Access Tables becomes SharePoint lists<br />Data Macros become SharePoint Workflows<br />Access Forms become ASPX pages<br />UI Macros become JavaScript<br />Access Reports become Reporting Services RDL Files<br />Access objects are serialised and put into a SharePoint List (MSysASO)<br />
  10. 10. Didn’t MOSS 2007 do this?<br />Yes and no…<br />Hosting Access tables as SharePoint lists is not new<br />Web Forms and reports are new<br />UI and Data Macros are new<br />
  11. 11. Can I just migrate old Access DBs?<br />Yes and no…<br />Tables must be compatible with SharePoint lists otherwise they will not migrate<br />New “Web” forms and reports end up on the web<br />Client based forms/reports/external tables can co-exist, but you need to open Access to use them<br />No VBA on the server<br />
  12. 12. What happens to objects I can’t migrate?<br />By opening the database in Access you can still use:<br />Client based forms and reports<br />Linked tables<br />Custom code (e.g. VBA)<br />Uses the Microsoft Sync Framework to ferry data and structure between the client and server<br />Important: Can only have Web or client tables, not both. <br />
  13. 13. How is this “Enterprise Friendly”?<br />Allows a traditionally opportunistic tool to create tactical applications<br />Applications can still be created by “power users” in a tool they are familiar with<br />
  14. 14. What type of applications can I build with this?<br />Table Centric<br />“Leaf Node” Applications<br />“Access Style” Reports, Forms and Navigation<br />
  15. 15. Can I integrate Access Services with other applications?<br />External data from within Access<br />Access data from other applications<br />
  16. 16. Why not create SharePoint apps?<br />Access Services is effectively a SharePoint application generator<br />One tool for end users to use<br />Standard architectural framework<br />It’s a familiar tool to many business users<br />
  17. 17. Choice is not always good<br />Endless debate is not appropriate for small scale projects<br />Constraints make for predictable results<br />Predictable results make for predictable costs<br />They also make it easier to train both users of the system and the people creating the system<br />
  18. 18. Can I leverage all the features of SharePoint Lists?<br />Most standard list features are available<br />SharePoint will only let you modify certain objects<br />External Content Types don’t work out of the box<br />
  19. 19. Demo<br />
  20. 20. How does dev/test/prod work?<br />First ask yourself “Does it need to?”<br />If it does:<br />Databases can be republished between environments<br />Can test in Access then publish when ready<br />Can use versioning on SharePoint lists<br />Consider data migration!<br />
  21. 21. What about source control?<br />Use Access Developer Extensions for Source Control support<br /><br />Primarily TFS & VSS<br />
  22. 22. <Insert Standard Anti-Access Comment Here /><br />Think bigger than the individual application<br />Stick to the golden path<br />Developers are not the big winner here; the Enterprise is<br />This is about being able to respond quickly to work requests that provide real business value without costing the world<br />
  23. 23. Questions<br />
  24. 24. More Info<br />Channel 9 Access Services Demo<br /><br />MS Access Blog<br /><br />MS Access on Twitter (Ryan McMinn)<br /><br />Using TFS with Access<br /><br />