CSC203. Mbwana Alliy Product Manager- Office Managed Business Microsoft Corporation

Transcription

1 CSC203 Mbwana Alliy Product Manager- Office Managed Business Microsoft Corporation

2 Why use Access and SharePoint Key Capabilities Key Scenarios Customer Case Study Questions & Feedback

3 Data is Relational Data integrity is more important than flexibility Calculations not the emphasis Multi-user Scenarios Frequent need for query Create and view reports

4 A growing number of enterprises are using Microsoft's Access desktop database. Yuhanna says 25 percent used Access in some form three years ago, and now that figure is up to 40 percent. Forrester quote, Redmond Developer December 2007

5 Too much information to track Where do I start? Database software is too hard to use Most of my information is already stored in another application Access 2007 offers: A library of prebuilt applications Results-oriented user interface Paste your data from Office Excel contacts from Office Outlook or import Make sense of complex information Little time for decision making Decisions have many dependencies Same data feeds different decisions Access 2007 offers: One click report creation WYSIWYG Report editing Grouping Pane simplifies changing views Filter options adapt to data type Sharing and managing information Increased reliance on others Too much data is scattered in hard disks Increased pressure from compliance and regulations Access 2007 offers: Easy data migration to Windows SharePoint Services keeping Work online or offline Permission-based Web access to data Records revision history tracking

6 Lowers the bar for end users and information workers to create and share applications. Risk of poorly designed applications created that are business critical. Sharing and managing information Increased reliance on others Too much data is scattered in hard disks Increased pressure from compliance and regulations Access 2007 offers: Easy data migration to Windows SharePoint Services keeping Work online or offline Permission-based Web access to data Records revision history tracking

7 Complexity Security Reliability Scalability Cost Enterprise Department Workgroup/Team Small Group Individual Flexibility & Rapid Application Development

8 Applications that are based on tracking data about concepts like Orders Customers Documents Processes Used by Teams Departments Enterprises Application Type Line of business applications High volume Mini LOB applications Low volume Tracking applications Lists Number of applications

9 Rich client development environment: Codeless development Single or multi-user applications Connects to different data storages Integration with Microsoft Office system Excel, InfoPath and Outlook integration

10 Getting Started with Access 2003 New! Start with prebuilt applications with Access 2007

11 Microsoft Office Access 2007 Rich visualizations Easy to build Easy to use Use multiple data sources Collect data via Use the application offline Windows SharePoint Services Collaboration and workflow IT Managed data source Security Web permissions List item permissions Archived IT archives the server Version history Recycle bin Build and deploy, reliable, IT managed applications easily

12

13

14 Allows end users to easily track information, build quick business applications, and collaborate via Windows SharePoint Services Gives professional developers and IT easy to customize and manage business applications that combine the best of the client and server End Users Much easier to use Out-of-the-box apps Easy to add a field, form, and report Power Users SharePoint for collaboration WYSIWYG authoring for forms and reports Codeless macros Outlook data collection Pro Developers / IT Whole new class of apps integrated with WSS Rich and reach interfaces Server-side manageability Utilize managed code Confident upgrade path

15 Dual entry mode Move data from Access applications to server Open WSS lists with Access and extend with richer Access objects Access as rich front end to WSS Reach web access to data Report and form views published on web site Integrated workflow: solutions can integrate predefined workflow for rich scenarios Extend work offline

16 Data Server Backup: Migrate data from your local database file to a server with Windows SharePoint Services Permission Setting: Manage which users have access to your data Recycle Bin: Recover lost data Revision History: Track records and see who created, edited, or deleted information.

17 Avoid chasing coworkers for updated information. Collect new information by Keep information up to date Use automatically generated Microsoft Office InfoPath or HTML

18 Access Client App stored in Table stored in 1 Single MDB file Logic runs Comments Solution is fully contained in one file Scenario Classic Access 2 MDB file Separate MDB Easier to migrate to SQL 3 MDB file Linked tables to Improved SQL or connect Performance to ODBC Less corruption N/A Improved client multi user experience. 4 MDB file Linked tables to 5 MDB stored in WSS WSS lists MDB/SQL/SP lists Data can be accessed from SharePoint App logic is stored on a managed server. Great for collaboration Thin experience Meet compliance needs Fully centralized and better scalability.

19 Export Access data table Export entire database to SharePoint Importing from Access Web Datasheet Capability Publish table or report as a SharePoint list Data as linked table in SharePoint Backs up MDB file Tables replaced with linked tables As a table copy of data As a linked table Scenario Simple sharing of dataoriginal database remains intact Synchronize client and SharePoint list Upsize and backup entire database for thin access to more people. Enables rich client forms, reports, queries Enables work offline modes Data always linked and lives on SharePoint

20 As a landing pad and collection point for disparate data sources Collect data from multiple SharePoint lists Other data Excel Spreadsheets ODBC connections (e.g. SQL) Even Create reports and republish back to SharePoint Move your desktop based application onto SharePoint Visible by IT Audit and backup.

21 Set up templates for other users to access and update information and publish back reports in lists. A method to deploy approved applications. Manage user access/permissions Use Access client as a reporting front end.

22 Over 5,000 rows/records, performance may slow At this point, it s probably time to migrate.

23 SharePoint & Access as a B2B platform, not intranet 18,000 vehicles in 28 countries. SharePoint holds data from a management/strategic perspective- feeds MIS on SQL backend Access Client updates the SharePoint with the management data Conducting tenders- 10 OEMs quoting terms and conditions for a fleet in all 28 countries

24 Database driven environment connected to a server/portal and great place to bring in your LOB applications. Access and SharePoint helps empower end users: Bring together different data sources, in a rich client Manage that data Share and collaborate.

25

26 Microsoft Access Homepage The Microsoft Office Access blog

27 Post Event DVD brought to you courtesy of:

28

29 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

30