Share this Page URL

Chapter 15. Integration with Office 2003... > Working with Access Data in InfoPath - Pg. 545

Integration with Office 2003 and SharePoint Services 16. 17. 545 Click the Refresh Data button at the top of the SharePoint list. If you're asked about pending changes, click Yes to proceed. Switch back to your Access database. If the table Access List 1 is still open, close it and reopen the Access List 1 table. You should now see the MyField1 field in the linked table and a new record with ID equal to 1. The Title and MyField1 fields are filled in with the values you entered earlier. As with any linked table, you can also add data to the linked table (either in Table view or via forms or another Web page), and that data will appear in the SharePoint list. With this level of integration, SharePoint can serve as your "one-stop shop" for data and information. Changing views The default view for a linked Access table is Datasheet view. SharePoint, however, allows you to modify the way the data is presented. You can choose to display the data in the standard List format, or you can customize the view using the Modify Settings And Columns command on the Actions menu. You can add columns and reorder them, change the title of the list, and set permissions. You can make an Access linked list look as much or as little like the rest of your SharePoint site as you want! Working with Access Data in InfoPath InfoPath (formerly known as XDocs), a new product introduced with Office 2003, is a powerful forms creation and entry program. Although earlier versions of Office supported forms in Word and Access, InfoPath introduces a new level of extensibility and design features that makes forms management and creation easy and very powerful. You've already learned how forms can be used in conjunction with a database to capture and display data. Access forms are a powerful tool for many scenarios. InfoPath takes the thinking behind Access forms to the next level. InfoPath is a complete, XML- based, form designing and publishing tool. As with Access forms, InfoPath forms are data driven, and so there is a tight synergy between Access and InfoPath. InfoPath forms can be linked to Access tables and used to populate those tables as well as display the data in them. In this section, we'll explore how Access can be used to extend InfoPath and broaden the use of the data it captures. See Also For more information about working with forms in Access, seeChapter 7, "Designing Basic Forms," and Chapter 8, "Adding Features and Function to Forms." Some knowledge of InfoPath and forms development will be helpful as you dig into this section, as we won't be able to give a full introduction to the application. You can find more information about InfoPath on the CD that accompanies this book. Exploring Info on InfoPath To demonstrate how Access can work with InfoPath, let's take a brief look at how InfoPath works and explore its architecture a bit. At its core, InfoPath is a standards-conformant XML file creator and editor. InfoPath is XML-based throughout and uses XML transforms, DTDs, manifests, and data files to accomplish its tasks. The designers of InfoPath built it from the ground up to conform to most of the relevant World Wide Web Consortium (W3C) standards, including DOM 1.0, XSLT 1.0, and XHTML 1.0. (These are just three of the many standards--a complete list is available on the InfoPath site on Office Online. For information about W3C standards, seeChapter 16.) Like the Access forms designer, the InfoPath editor is a graphical user interface that hides a lot of the underlying XML syntax and code and allows you to create forms in a friendly, intuitive environment. Because InfoPath is XML-based, forms created in InfoPath can be published as standalone forms to a location on the file system, to a Web site, or to a SharePoint team site.