| s-2
| SQL Server verifies that the account name and password were validated when the user logged on to the system and grants access to the database, without requiring a separate logon name or password. |
| s-3
| With the default installation of the Microsoft SQL Server 2000 Desktop Engine with integrated security, the user must be a member of the administrator group for the machine on which the Access project resides. |
| s-4
| This makes it difficult to allow other users to gain access to the Access project. |
| s-5
| There is currently no simple way for the system administrator to create new logon accounts to the locally installed SQL Server database except by using SQL Tools or Transact-SQL (TSQL) commands. |
| s-6
| See the http://officeupdate.microsoft.com/, Microsoft Developer Network Web site for more information on TSQL. |
| s-7
| You can change the security mode for accessing the SQL Server database on a computer running Windows NT. |
| s-8
| By setting properties from the View menu, you can enable mixed mode security. |
| s-9
| Using the default SA account, users can access the SQL Server database through the Access project without any additional security requirements. |
| s-10
| The administrator of the SQL Server can also add additional security by changing the default SA account password. |
| s-11
| In order for the Enable system administrator (SA) user name check box to be enabled, the following must be true. |
| s-12
| The Access project must be connected to a SQL Server 7.0 (or later) database or a Microsoft SQL Server 2000 Desktop Engine. |
| s-13
| The SQL Server database must be running on a Windows NT platform. |
| s-14
| The SQL Server must be running on the same computer as the Access project. |
| s-15
| The current Windows NT user must be an Administrator for the computer. |
| s-16
| The current SQL Server user must be a member of the System Administrator role. |
| s-17
| After changing the security mode, it is strongly recommended that the SA password be changed by using the Set Login Password command (on the Tools menu, point to Security). |
| s-18
| Some of the hyperlinks in this topic go to the Web. |
| s-19
| About XML data and Access |
| s-20
| Extensible Markup Language (XML) is the standard language for describing and delivering data on the Web, just as Hypertext Markup Language (HTML) is the standard language for creating and displaying Web pages. |
| s-21
| Microsoft Access provides ways to both import and export XML data as well as transform the data to and from other formats using XML related files. |
| s-22
| About XML |
| s-23
| Moving information across the Internet and between software applications has always been difficult due to differences in data formats and proprietary structures. |
| s-24
| HTML, while well suited for providing text and image display information for Web browsers, is limited in its ability to define data and data structures. |
| s-25
| HTML describes how a Web page should look, whereas XML defines the data and describes how the data should be structured. |
| s-26
| XML is a data interchange format in that it allows you to exchange data between dissimilar systems or applications. |
| s-27
| XML separates the data from the presentation so that the same XML data can be presented in multiple ways by using different presentation files. |
| s-28
| XML is a standards-based protocol that is governed by the World Wide Web Consortium (W3C). |
| s-29
| The XML protocol is a set of rules, guidelines, and conventions for designing data formats and structures, in a way that produces files that are easy to generate and easily read by different computers and applications. |
| s-30
| In addition, XML defined structures are unambiguous; that is, they are self-describing and platform-independent. |
| s-31
| Like HTML, XML makes use of tags and attributes, but while HTML specifies what each tag and attribute means (and thus how the data between them will look in a browser), XML uses the tags only to delimit pieces of data, and leaves the interpretation of the data completely to the application that reads it. |
| s-32
| Additional information about XML can be found on the web site. |
| s-33
| About importing XML data |
| s-34
| Access provides choices for using data from many external sources. |
| s-35
| XML makes it easier to transform the data from almost any external application for use by Access. |
| s-36
| You can: |
| s-37
| Use an Extensible Stylesheet Language Transformation (XSLT) file to transform the data into an Access data format. |
| s-38
| You can use the Import command (point to Get External Data on the File menu) to import XML data files into Access. |
| s-39
| This command displays the Import dialog box so that you can select an XML document as well as a schema, which describes the structure of the data. |
| s-40
| You can only import a single document at a time into Access. |
| s-41
| The data must be in a format that Access recognizes, either in a native format or through the use of a schema. |
| s-42
| Note that when importing XML data, you can not choose a subset of the XML document; the entire file has to be imported. |
| s-43
| You can transform the native XML data into a specific Access format by choosing from the options in the Import XML dialog box. |
| s-44
| You can also specify whether to overwrite any existing tables or append to existing data. |
| s-45
| What are XML schemas |
| s-46
| You use XML schemas to describe the structure of data in a common format that customers, other Web browsers, and any number of XML-enabled software programs can recognize. |
| s-47
| Specifically, schemas define the rules of an XML data document, including element names and data types, which elements can appear in combination, and which attributes are available for each element. |
| s-48
| Schemas provide a model for an XML data document which defines the arrangement of tags and text within all documents referencing the schema. |
| s-49
| Access supports the XML Schema standard (XSD). |
| s-50
| XSD is a proposed World Wide Web Consortium (W3C) standard designed as a basic infrastructure for describing the type and structure of XML documents. |
| s-51
| By using a schema, you can ensure that any XML document that is used to import data into Access or export from Access to another format contains specific data and conforms to a defined structure. |
| s-52
| You can also provide the schema to other businesses and applications so that they know how they should structure any data they provide to you and they, in turn, can provide their schema to you. |
| s-53
| Displaying XML data |
| s-54
| XML syntax (the tags and their placement in a document) defines and describes the data in an XML document but doesn't indicate how the data should be displayed. |
| s-55
| In earlier applications and in some current uses, Cascading Style Sheets (CSS) were used to tell the browser how to display the XML data. |
| s-56
| However, a CSS isn't always a good choice because they are written in a specialized language which means that the developer has to use another language in order to write, modify, or understand the structure of the style sheet. |
| s-57
| A CSS merely allows you to specify the formatting of each XML element without much control over the output. |
| s-58
| On the other hand, an Extensible Stylesheet Language (XSL) style sheet is considerably more flexible than a CSS file. |
| s-59
| It allows you to precisely select the data that will be displayed, to specify the order or arrangement of the data, and to modify or add information. |
| s-60
| You can apply a filter to a row or column field to show the top or bottom n items based on a total. |
| s-61
| For example, you can filter for the top or bottom 25 % of salespeople based on the number of orders handled. |
| s-62
| Combining multiple filters |
| s-63
| Filters are additive. |
| s-64
| Each filter you apply is added to the ones you already have in effect. |
| s-65
| However, when you apply a filter by selection, the conditional filter already applied on the field is removed before the filter by selection is applied. |
| s-66
| Conditional filters are independent of each other. |
| s-67
| The result of one conditional filter does not affect the result of another. |
| s-68
| An autofilter is always applied before a conditional filter, regardless of the order in which you applied them. |
| s-69
| For example, if you set a conditional filter to show the top two cities based on sales, followed by an autofilter on the ShippedCity field to include only five cities, the PivotTable view will show the top two of the five cities you selected. |
| s-70
| Removing and reapplying a filter |
| s-71
| However, the filter settings are retained, so that when you turn autofiltering back on, the data that was previously displayed or hidden is again displayed or hidden. |
| s-72
| Filter settings are retained when you move fields to change the layout. |
| s-73
| Also, if you remove a field and later add the field back to the layout, the same items are again hidden. |
| s-74
| If you don't want to retain your filter selections, make sure the AutoFilter button is not selected before you start selecting items to filter. |
| s-75
| If the button is not selected, selecting new items to filter automatically turns filtering on and removes your former filter settings. |
| s-76
| Identifying filters that are currently in effect |
| s-77
| When items in a field are hidden by autofiltering or filter by selection, the drop-down arrow Field arrow in the field label is blue. |
| s-78
| Click the blue arrow to see the filter that is in effect. |
| s-79
| When items in a field are hidden by conditional filtering, a funnel appears to the left of the drop-down arrow Field arrow. |
| s-80
| You can get more information about the current filter in the Properties dialog box. |
| s-81
| Effects of filtering on calculations |
| s-82
| Totals can include only the displayed data, or both visible and hidden data. |
| s-83
| About customizing a control |
| s-84
| In Design view of a form, report, or data access page, you can format a control in the following ways: |
| s-85
| Size. |
| s-86
| You can resize a control by using the sizing handles, or you can resize a control to the height or width of another control. |
| s-87
| When you are in Design view of a form or report, you can use the ruler to help you resize controls. |
| s-88
| The width of the ruler's unit of measure is based on the regional settings in Microsoft Windows Control Panel. |
| s-89
| Color, transparency, and special effects. |
| s-90
| You can change the color of a control or make it transparent. |
| s-91
| You can also emphasize the appearance of a control by using special effects. |
| s-92
| For example, you can specify that a control is raised, sunken, or etched. |
| s-93
| On a form or report, you can also specify that a control is shadowed or chiseled. |
| s-94
| Borders. |
| s-95
| You can set the color and width of borders of controls. |
| s-96
| Also, you can set the line style of borders. For example, you can specify that a border consists of dashes or dots. |
| s-97
| Appearance of text. |
| s-98
| You can specify the font and font size for text in a control. |
| s-99
| Also, you can make the text in a control bold, italic, or underlined. |
| s-100
| Position. |
| s-101
| You can move a control or align it relative to another control. |