Sentence view
Universal Dependencies - English - LinES
| Language | English |
|---|
| Project | LinES |
|---|
| Corpus Part | train |
|---|
| Annotation | Ahrenberg, Lars |
|---|
showing 101 - 200 of 357 • previous • next
For example, when you move a Product field to the filter area, you can display data for one product at a time.
s-101
en_lines-ud-train-doc1-101
For example, when you move a Product field to the filter area, you can display data for one product at a time.
Moving row or column fields to a higher or lower level
s-102
en_lines-ud-train-doc1-102
Moving row or column fields to a higher or lower level
When a view has multiple row and column fields, the fields that are closest to the detail data are referred to as inner fields.
s-103
en_lines-ud-train-doc1-103
When a view has multiple row and column fields, the fields that are closest to the detail data are referred to as inner fields.
The other fields are outer fields.
s-104
en_lines-ud-train-doc1-104
The other fields are outer fields.
You can switch the inner and outer fields.
s-105
en_lines-ud-train-doc1-105
You can switch the inner and outer fields.
Example of inner and outer row fields
s-106
en_lines-ud-train-doc1-106
Example of inner and outer row fields
2 Outer row field
s-107
en_lines-ud-train-doc1-107
2 Outer row field
2 Inner row field
s-108
en_lines-ud-train-doc1-108
2 Inner row field
3 Outer field items
s-109
en_lines-ud-train-doc1-109
3 Outer field items
4 Items for the inner field are repeated for each item in the outer field.
s-110
en_lines-ud-train-doc1-110
4 Items for the inner field are repeated for each item in the outer field.
Adding and removing fields
s-111
en_lines-ud-train-doc1-111
Adding and removing fields
The layout of a PivotTable view does not have to include all of the fields that are available from the underlying record source.
s-112
en_lines-ud-train-doc1-112
The layout of a PivotTable view does not have to include all of the fields that are available from the underlying record source.
You can also remove fields that you no longer want to see from the PivotTable view layout.
s-113
en_lines-ud-train-doc1-113
You can also remove fields that you no longer want to see from the PivotTable view layout.
Customizing the layout of a PivotChart view
s-114
en_lines-ud-train-doc1-114
Customizing the layout of a PivotChart view
You change the layout of a chart by moving the fields to predefined drop areas within the chart workspace.
s-115
en_lines-ud-train-doc1-115
You change the layout of a chart by moving the fields to predefined drop areas within the chart workspace.
To do this, drop areas must be shown in the chart.
s-116
en_lines-ud-train-doc1-116
To do this, drop areas must be shown in the chart.
Drop areas are displayed differently depending on the chart type.
s-117
en_lines-ud-train-doc1-117
Drop areas are displayed differently depending on the chart type.
For example, a series drop area is not displayed for a pie chart because pie charts consist of only one series.
s-118
en_lines-ud-train-doc1-118
For example, a series drop area is not displayed for a pie chart because pie charts consist of only one series.
Additionally, it is written in a style similar to an XML document using a combination of XML-like tags and HTML to create a template for a specific style of output.
s-119
en_lines-ud-train-doc1-119
Additionally, it is written in a style similar to an XML document using a combination of XML-like tags and HTML to create a template for a specific style of output.
Note that you are not required to link either a CSS file or an XSL style sheet to an XML document in order for Internet Explorer 5 (and later versions) to display the document.
s-120
en_lines-ud-train-doc1-120
Note that you are not required to link either a CSS file or an XSL style sheet to an XML document in order for Internet Explorer 5 (and later versions) to display the document.
Internet Explorer has a default, built-in style sheet that displays the XML source as a (collapsible|expandable) tree.
s-121
en_lines-ud-train-doc1-121
Internet Explorer has a default, built-in style sheet that displays the XML source as a (collapsible|expandable) tree.
You can use style sheets to insure that the XML-based Web pages on your intranet or Website are consistent and present a uniform appearance without having to add HTML to each page.
s-122
en_lines-ud-train-doc1-122
You can use style sheets to insure that the XML-based Web pages on your intranet or Website are consistent and present a uniform appearance without having to add HTML to each page.
About Extensible Stylesheet Language Transformation (XSLT)
s-123
en_lines-ud-train-doc1-123
About Extensible Stylesheet Language Transformation (XSLT)
XSL for Transformation (XSLT) is a specification that is currently under development by the World Wide Web Consortium (W3C), and supported by Access.
s-124
en_lines-ud-train-doc1-124
XSL for Transformation (XSLT) is a specification that is currently under development by the World Wide Web Consortium (W3C), and supported by Access.
XSLT is an XML-based language that allows one XML document to be mapped, or transformed, into another XML document.
s-125
en_lines-ud-train-doc1-125
XSLT is an XML-based language that allows one XML document to be mapped, or transformed, into another XML document.
This provides a way of transforming an XML document's presentation information from a source format to a target format and back again.
s-126
en_lines-ud-train-doc1-126
This provides a way of transforming an XML document's presentation information from a source format to a target format and back again.
Typically, a developer creates an XSL transformation file that, when applied to an XML document during export, interprets or transforms the XML data into a presentation format that can be recognized by another application, such as Service Advertising Protocol (SAP) or a custom purchase order format.
s-127
en_lines-ud-train-doc1-127
Typically, a developer creates an XSL transformation file that, when applied to an XML document during export, interprets or transforms the XML data into a presentation format that can be recognized by another application, such as Service Advertising Protocol (SAP) or a custom purchase order format.
XSLT has many of the constructs (structures and commands) found in other programming languages which allow the developer to use variables, loops and iterations, and conditional statements.
s-128
en_lines-ud-train-doc1-128
XSLT has many of the constructs (structures and commands) found in other programming languages which allow the developer to use variables, loops and iterations, and conditional statements.
This gives the developer considerable control over the output of the XML data.
s-129
en_lines-ud-train-doc1-129
This gives the developer considerable control over the output of the XML data.
About exporting to XML files
s-130
en_lines-ud-train-doc1-130
About exporting to XML files
Exporting data and database objects to an XML file is a convenient way to move and store your information in a format that can readily be used across the Web.
s-131
en_lines-ud-train-doc1-131
Exporting data and database objects to an XML file is a convenient way to move and store your information in a format that can readily be used across the Web.
In Access, you can export the data, the schema (data structure), or both, to XML files.
s-132
en_lines-ud-train-doc1-132
In Access, you can export the data, the schema (data structure), or both, to XML files.
Export data to an XML file and, optionally, use an XSLT to transform the data to another format.
s-133
en_lines-ud-train-doc1-133
Export data to an XML file and, optionally, use an XSLT to transform the data to another format.
Export the data schema using XML Schema standard (XSD).
s-134
en_lines-ud-train-doc1-134
Export the data schema using XML Schema standard (XSD).
Export the data behind forms and reports to an XML file.
s-135
en_lines-ud-train-doc1-135
Export the data behind forms and reports to an XML file.
You can also transform the data to another presentation format using an Extensible Style Language (XSL) file during the export process.
s-136
en_lines-ud-train-doc1-136
You can also transform the data to another presentation format using an Extensible Style Language (XSL) file during the export process.
You can export tables, queries, and the data behind forms or reports from a Microsoft Access database (.mdb) as well as tables, views, stored produces, functions, and the data behind forms and reports from a Microsoft Access project (.adp).
s-137
en_lines-ud-train-doc1-137
You can export tables, queries, and the data behind forms or reports from a Microsoft Access database (.mdb) as well as tables, views, stored produces, functions, and the data behind forms and reports from a Microsoft Access project (.adp).
Exporting tables, queries, views, datasheets, forms or reports
s-138
en_lines-ud-train-doc1-138
Exporting tables, queries, views, datasheets, forms or reports
You can export a database object as an XML document in several ways:
s-139
en_lines-ud-train-doc1-139
You can export a database object as an XML document in several ways:
You can export just the data from a table, query, datasheet, form, or report into an XML file.
s-140
en_lines-ud-train-doc1-140
You can export just the data from a table, query, datasheet, form, or report into an XML file.
This data is saved to a file named .xml.
s-141
en_lines-ud-train-doc1-141
This data is saved to a file named .xml.
You can export just the schema (data structure) of a table, query, datasheet, form, or report to an XML schema file.
s-142
en_lines-ud-train-doc1-142
You can export just the schema (data structure) of a table, query, datasheet, form, or report to an XML schema file.
An XML schema file is a formal specification of the rules for an XML document, providing a series of element names, as well as which elements are allowed in the document and in what combinations.
s-143
en_lines-ud-train-doc1-143
An XML schema file is a formal specification of the rules for an XML document, providing a series of element names, as well as which elements are allowed in the document and in what combinations.
If you select to save the schema as XSD, the file is saved as .xsd.
s-144
en_lines-ud-train-doc1-144
If you select to save the schema as XSD, the file is saved as .xsd.
[45]
Note
s-145
en_lines-ud-train-doc1-145
Note
When you export a table to an XML document, you can also export related tables.
s-146
en_lines-ud-train-doc1-146
When you export a table to an XML document, you can also export related tables.
For example, if you export a table of Customers Orders, you can also choose to export a related Orders Details table and Customers table into the same file.
s-147
en_lines-ud-train-doc1-147
For example, if you export a table of Customers Orders, you can also choose to export a related Orders Details table and Customers table into the same file.
If selected, you can also save the structure of a table, query, datasheet, form, or report into a file that describes the presentation and connection information.
s-148
en_lines-ud-train-doc1-148
If selected, you can also save the structure of a table, query, datasheet, form, or report into a file that describes the presentation and connection information.
For forms and reports, this file is saved in an XML-based language called ReportML which provides presentation data as well as a data model for creating a data access page.
s-149
en_lines-ud-train-doc1-149
For forms and reports, this file is saved in an XML-based language called ReportML which provides presentation data as well as a data model for creating a data access page.
For tables, queries-views, and datasheets, the presentation file is a spreadsheet-like template.
s-150
en_lines-ud-train-doc1-150
For tables, queries-views, and datasheets, the presentation file is a spreadsheet-like template.
This file is saved as _report.xml.
s-151
en_lines-ud-train-doc1-151
This file is saved as _report.xml.
In addition, when you choose to save the data as XML, you can specify that the data be transformed to a custom display format by using an existing .xsl file.
s-152
en_lines-ud-train-doc1-152
In addition, when you choose to save the data as XML, you can specify that the data be transformed to a custom display format by using an existing .xsl file.
If no .xsl file is specified, the data is saved in standard XML format.
s-153
en_lines-ud-train-doc1-153
If no .xsl file is specified, the data is saved in standard XML format.
Note that if no data is selected for export then a presentation format is also unavailable.
s-154
en_lines-ud-train-doc1-154
Note that if no data is selected for export then a presentation format is also unavailable.
What is ReportML?
s-155
en_lines-ud-train-doc1-155
What is ReportML?
ReportML is a 'language' developed by Microsoft and specific to Access which can be used to describe Access database objects in XML.
s-156
en_lines-ud-train-doc1-156
ReportML is a 'language' developed by Microsoft and specific to Access which can be used to describe Access database objects in XML.
The ReportML language is made up of a set of tags that describe a form, report or data access page's properties, events, and attributes.
s-157
en_lines-ud-train-doc1-157
The ReportML language is made up of a set of tags that describe a form, report or data access page's properties, events, and attributes.
When you export data from Access to an XML file, you choose to save the structure of a form or report into a ReportML format.
s-158
en_lines-ud-train-doc1-158
When you export data from Access to an XML file, you choose to save the structure of a form or report into a ReportML format.
The ReportML file can be used to convert the saved data into a data access page.
s-159
en_lines-ud-train-doc1-159
The ReportML file can be used to convert the saved data into a data access page.
Well-formed documents
s-160
en_lines-ud-train-doc1-160
Well-formed documents
Any XML document produced by Access is well-formed, which means that it conforms to the basic rules of XML.
s-161
en_lines-ud-train-doc1-161
Any XML document produced by Access is well-formed, which means that it conforms to the basic rules of XML.
That is:
s-162
en_lines-ud-train-doc1-162
That is:
Each XML document must have a unique root element (an element encompassing the entire document).
s-163
en_lines-ud-train-doc1-163
Each XML document must have a unique root element (an element encompassing the entire document).
All start and end tags match.
s-164
en_lines-ud-train-doc1-164
All start and end tags match.
XML tags are case-sensitive.
s-165
en_lines-ud-train-doc1-165
XML tags are case-sensitive.
For each start tag, there is a corresponding end tag.
s-166
en_lines-ud-train-doc1-166
For each start tag, there is a corresponding end tag.
Empty elements can be denoted by a special shorthand tag.
s-167
en_lines-ud-train-doc1-167
Empty elements can be denoted by a special shorthand tag.
Again, XML tags are case-sensitive.
s-168
en_lines-ud-train-doc1-168
Again, XML tags are case-sensitive.
Access ReportML will not write out any empty tags.
s-169
en_lines-ud-train-doc1-169
Access ReportML will not write out any empty tags.
Elements do not overlap.
s-170
en_lines-ud-train-doc1-170
Elements do not overlap.
In other words, start and end tag must be properly nested within other elements.
s-171
en_lines-ud-train-doc1-171
In other words, start and end tag must be properly nested within other elements.
Certain reserve characters are part of the XML syntax and will not be interpreted as themselves if used in the data portion of an element.
s-172
en_lines-ud-train-doc1-172
Certain reserve characters are part of the XML syntax and will not be interpreted as themselves if used in the data portion of an element.
You need to substitute a special character sequence (called an 'entity' by XML) as follows:
s-173
en_lines-ud-train-doc1-173
You need to substitute a special character sequence (called an 'entity' by XML) as follows:
[74]
Character
s-174
en_lines-ud-train-doc1-174
Character
[75]
Entity
s-175
en_lines-ud-train-doc1-175
Entity
The following is an example of a well-formed XML document:
s-176
en_lines-ud-train-doc1-176
The following is an example of a well-formed XML document:
where:
s-177
en_lines-ud-train-doc1-177
where:
is a declaration that states that this is an XML document and gives the version number.
s-178
en_lines-ud-train-doc1-178
is a declaration that states that this is an XML document and gives the version number.
The declaration is optional but is recommended in any XML document.
s-179
en_lines-ud-train-doc1-179
The declaration is optional but is recommended in any XML document.
is the root element which encompasses the entire document.
s-180
en_lines-ud-train-doc1-180
is the root element which encompasses the entire document.
is a start tag and is an end tag which together describe an element of data, in this case, the customer's name.
s-181
en_lines-ud-train-doc1-181
is a start tag and is an end tag which together describe an element of data, in this case, the customer's name.
Notice that each tag set has both start and end tags and is case sensitive, and that the tag sets are properly nested within each other.
s-182
en_lines-ud-train-doc1-182
Notice that each tag set has both start and end tags and is case sensitive, and that the tag sets are properly nested within each other.
Also notice the entity ' which will be transformed to an apostrophe when the data is imported by the receiving application.
s-183
en_lines-ud-train-doc1-183
Also notice the entity ' which will be transformed to an apostrophe when the data is imported by the receiving application.
The apostrophe has a special purpose in an XML document and can be misinterpreted if used directly in the text.
s-184
en_lines-ud-train-doc1-184
The apostrophe has a special purpose in an XML document and can be misinterpreted if used directly in the text.
The converted data will be displayed as Mom's Boston Crab Meat.
s-185
en_lines-ud-train-doc1-185
The converted data will be displayed as Mom's Boston Crab Meat.
White space can be used throughout the document to enhance readability.
s-186
en_lines-ud-train-doc1-186
White space can be used throughout the document to enhance readability.
If a schema is specified while exporting from Access, then the XML documents created are considered to be valid XML documents.
s-187
en_lines-ud-train-doc1-187
If a schema is specified while exporting from Access, then the XML documents created are considered to be valid XML documents.
This means that in addition to being well-formed, the documents conform to a defined schema.
s-188
en_lines-ud-train-doc1-188
This means that in addition to being well-formed, the documents conform to a defined schema.
About exporting or copying a PivotTable view to Excel or other applications
s-189
en_lines-ud-train-doc1-189
About exporting or copying a PivotTable view to Excel or other applications
If you are familiar with Microsoft Excel PivotTable reports and want to work with the data in Excel, there are two ways to accomplish this.
s-190
en_lines-ud-train-doc1-190
If you are familiar with Microsoft Excel PivotTable reports and want to work with the data in Excel, there are two ways to accomplish this.
Exporting data to an interactive Excel PivotTable report
s-191
en_lines-ud-train-doc1-191
Exporting data to an interactive Excel PivotTable report
To view and modify the contents of a PivotTable view by using Excel, you can export the PivotTable view to Excel.
s-192
en_lines-ud-train-doc1-192
To view and modify the contents of a PivotTable view by using Excel, you can export the PivotTable view to Excel.
Preparing for export to Excel
s-193
en_lines-ud-train-doc1-193
Preparing for export to Excel
Excel PivotTable reports can not display detail fields.
s-194
en_lines-ud-train-doc1-194
Excel PivotTable reports can not display detail fields.
When you export to Excel, detail fields will be available on the PivotTable toolbar in Excel, but the fields won't be displayed in the report.
s-195
en_lines-ud-train-doc1-195
When you export to Excel, detail fields will be available on the PivotTable toolbar in Excel, but the fields won't be displayed in the report.
If you want the Excel PivotTable report to reflect the appearance of the PivotTable view, before you export to an Excel PivotTable report, either move all the fields out of the detail area, or hide detail data for items and cells so that the detail area is not displayed.
s-196
en_lines-ud-train-doc1-196
If you want the Excel PivotTable report to reflect the appearance of the PivotTable view, before you export to an Excel PivotTable report, either move all the fields out of the detail area, or hide detail data for items and cells so that the detail area is not displayed.
After you export
s-197
en_lines-ud-train-doc1-197
After you export
You might notice some differences in your PivotTable view after you export it to Excel.
s-198
en_lines-ud-train-doc1-198
You might notice some differences in your PivotTable view after you export it to Excel.
This is because PivotTable views use the Microsoft Office PivotTable Component, and Excel PivotTable reports either do not support certain PivotTable list features, or they implement some features differently.
s-199
en_lines-ud-train-doc1-199
This is because PivotTable views use the Microsoft Office PivotTable Component, and Excel PivotTable reports either do not support certain PivotTable list features, or they implement some features differently.
For information about differences between PivotTable lists and Excel PivotTable reports, see Excel Help.
s-200
en_lines-ud-train-doc1-200
For information about differences between PivotTable lists and Excel PivotTable reports, see Excel Help.
Edit as list • Text view • Dependency trees