AllLangHelp_sdatabase.mk | 1
AllLangHelp_shared.mk | 1
source/text/sdatabase/02000000.xhp | 8 -
source/text/sdatabase/02000002.xhp | 4
source/text/sdatabase/02010100.xhp | 100 +++++++++++-----------
source/text/shared/02/01170203.xhp | 2
source/text/shared/02/14030000.xhp | 2
source/text/shared/02/14040000.xhp | 2
source/text/shared/02/14050000.xhp | 2
source/text/shared/02/14060000.xhp | 2
source/text/shared/02/14070000.xhp | 2
source/text/shared/02/limit.xhp | 2
source/text/shared/explorer/database/05020000.xhp | 2
source/text/shared/explorer/database/11080000.xhp | 2
source/text/shared/guide/data_enter_sql.xhp | 2
source/text/shared/guide/data_queries.xhp | 2
source/text/shared/guide/data_search2.xhp | 2
source/text/shared/guide/data_tables.xhp | 2
18 files changed, 70 insertions(+), 70 deletions(-)
New commits:
commit 49af25239f655a8d87dbe28bf5ed75040ca6bc11
Author: Olivier Hallot <olivier.hal...@libreoffice.org>
AuthorDate: Wed Aug 12 17:15:17 2020 -0300
Commit: Olivier Hallot <olivier.hal...@libreoffice.org>
CommitDate: Wed Aug 12 22:32:17 2020 +0200
Reposition query design help page
Change-Id: I5bf19c20cbac1b764aec972fa756586438279cc0
Reviewed-on: https://gerrit.libreoffice.org/c/help/+/100629
Tested-by: Jenkins
Reviewed-by: Olivier Hallot <olivier.hal...@libreoffice.org>
diff --git a/AllLangHelp_sdatabase.mk b/AllLangHelp_sdatabase.mk
index 4065e5c30..bca681984 100644
--- a/AllLangHelp_sdatabase.mk
+++ b/AllLangHelp_sdatabase.mk
@@ -19,6 +19,7 @@ $(eval $(call gb_AllLangHelp_add_helpfiles,sdatabase,\
helpcontent2/source/text/sdatabase/main \
helpcontent2/source/text/sdatabase/02000000 \
helpcontent2/source/text/sdatabase/02000002 \
+ helpcontent2/source/text/sdatabase/02010100 \
helpcontent2/source/text/sdatabase/toolbars \
))
diff --git a/AllLangHelp_shared.mk b/AllLangHelp_shared.mk
index b3e7f75f8..92c720da5 100644
--- a/AllLangHelp_shared.mk
+++ b/AllLangHelp_shared.mk
@@ -856,7 +856,6 @@ $(eval $(call gb_AllLangHelp_add_helpfiles,shared,\
))
$(eval $(call gb_AllLangHelp_add_helpfiles,shared,\
- helpcontent2/source/text/shared/explorer/database/02010100 \
helpcontent2/source/text/shared/explorer/database/02010101 \
helpcontent2/source/text/shared/explorer/database/04000000 \
helpcontent2/source/text/shared/explorer/database/04030000 \
diff --git a/source/text/sdatabase/02000000.xhp
b/source/text/sdatabase/02000000.xhp
index e3fa83b2e..265121e3b 100644
--- a/source/text/sdatabase/02000000.xhp
+++ b/source/text/sdatabase/02000000.xhp
@@ -59,14 +59,14 @@
<tip id="par_id3153146">You can also open the data source view
(Ctrl+Shift+F4), select the entire database table in the data source view
(click on the top left corner of the table), and then drag the selection to a
text document or spreadsheet.</tip>
<h2 id="hd_id3148946"><link href="text/shared/main0212.xhp" name="Sorting and
Filtering Data">Sorting and Filtering Data</link></h2>
<paragraph role="paragraph" id="par_id3149655" xml-lang="en-US">Allows you to
sort and filter the data in a query table.</paragraph>
-<h2 id="hd_id3153379"><link href="text/shared/explorer/database/02010100.xhp"
name="Query Design">Query Design</link></h2>
+<h2 id="hd_id3153379"><link href="text/sdatabase/020010100.xhp" name="Query
Design">Query Design</link></h2>
<paragraph role="paragraph" id="par_id3151211" xml-lang="en-US">With the
<emph>Query Design</emph>, you can create and edit a query or view.</paragraph>
<embed href="text/shared/main0214.xhp#sql"/>
-<h2 id="hd_id3153968"><link href="text/shared/explorer/database/02010100.xhp"
name="Query Through Several Tables">Query Through Several Tables</link></h2>
+<h2 id="hd_id3153968"><link href="text/sdatabase/020010100.xhp" name="Query
Through Several Tables">Query Through Several Tables</link></h2>
<paragraph role="paragraph" id="par_id3151043" xml-lang="en-US">The query
result can contain data from several tables if these are linked to each other
by suitable data fields.</paragraph>
-<h2 id="hd_id3159149"><link href="text/shared/explorer/database/02010100.xhp"
name="Formulating Query Criteria">Formulating Query Criteria</link></h2>
+<h2 id="hd_id3159149"><link href="text/sdatabase/020010100.xhp"
name="Formulating Query Criteria">Formulating Query Criteria</link></h2>
<paragraph role="paragraph" id="par_id3154910" xml-lang="en-US">You can find
out which operators and commands can be used to formulate the filter conditions
for a query.</paragraph>
-<h2 id="hd_id3156212"><link href="text/shared/explorer/database/02010100.xhp"
name="Executing Functions">Executing Functions</link></h2>
+<h2 id="hd_id3156212"><link href="text/sdatabase/020010100.xhp"
name="Executing Functions">Executing Functions</link></h2>
<paragraph role="paragraph" id="par_id3144762" xml-lang="en-US">You can
perform calculations with the data of a table and store the results as a query
result.</paragraph>
</body>
</helpdocument>
diff --git a/source/text/sdatabase/02000002.xhp
b/source/text/sdatabase/02000002.xhp
index 5181290fb..99024ab9a 100644
--- a/source/text/sdatabase/02000002.xhp
+++ b/source/text/sdatabase/02000002.xhp
@@ -33,10 +33,10 @@
<h2 id="hd_id3145072">How to continue?</h2>
<paragraph role="paragraph" id="par_id3149177" xml-lang="en-US">There are
three options available for answering this question:</paragraph>
<h3 id="hd_id3147576">Do you really want to open the query in the graphic
view?</h3>
-<paragraph role="paragraph" id="par_id3166461" xml-lang="en-US"><ahelp
hid=".">Allows you to open the query in the <link
href="text/shared/explorer/database/02010100.xhp" name="Design View">Design
View</link> in spite of missing elements.</ahelp> This option also allows you
to specify if other errors need to be ignored.</paragraph>
+<paragraph role="paragraph" id="par_id3166461" xml-lang="en-US"><ahelp
hid=".">Allows you to open the query in the <link
href="text/sdatabase/02010100.xhp" name="Design View">Design View</link> in
spite of missing elements.</ahelp> This option also allows you to specify if
other errors need to be ignored.</paragraph>
<paragraph role="paragraph" id="par_id3153031" xml-lang="en-US">The query is
opened in the Design View (the graphical interface). Missing tables appear
blank and invalid fields appear with their (invalid) names in the list of
fields. This lets you work with exactly those fields that caused the
error.</paragraph>
<h3 id="hd_id3149578">Open the query in the SQL View</h3>
-<paragraph role="paragraph" id="par_id3159157" xml-lang="en-US"><ahelp
hid=".">Allows you to open the query design in the <link
href="text/shared/explorer/database/02010100.xhp" name="SQL Mode">SQL
Mode</link> and to interpret the query as a <link
href="text/shared/02/14030000.xhp" name="Native SQL">Native SQL</link>.</ahelp>
You can only quit the native SQL mode when the $[officename] statement is
completely interpreted (only possible if the used tables or fields in the query
really exist).</paragraph>
+<paragraph role="paragraph" id="par_id3159157" xml-lang="en-US"><ahelp
hid=".">Allows you to open the query design in the <link
href="text/sdatabase/02010100.xhp" name="SQL Mode">SQL Mode</link> and to
interpret the query as a <link href="text/shared/02/14030000.xhp" name="Native
SQL">Native SQL</link>.</ahelp> You can only quit the native SQL mode when the
$[officename] statement is completely interpreted (only possible if the used
tables or fields in the query really exist).</paragraph>
<h3 id="hd_id3150984">Do not open the query</h3>
<paragraph role="paragraph" id="par_id3156329" xml-lang="en-US"><ahelp
hid=".">Allows you to cancel the procedure and specify that the query should
not be opened.</ahelp> This option corresponds to the function of the
<emph>Cancel</emph> dialog button.</paragraph>
<h3 id="hd_id3148492">Also ignore similar errors</h3>
diff --git a/source/text/shared/explorer/database/02010100.xhp
b/source/text/sdatabase/02010100.xhp
similarity index 87%
rename from source/text/shared/explorer/database/02010100.xhp
rename to source/text/sdatabase/02010100.xhp
index 74aff76d0..b3e64a4b4 100644
--- a/source/text/shared/explorer/database/02010100.xhp
+++ b/source/text/sdatabase/02010100.xhp
@@ -21,7 +21,7 @@
<meta>
<topic id="textsharedexplorerdatabase02010100xml" indexer="include"
status="PUBLISH">
<title id="tit" xml-lang="en-US">Query Design</title>
- <filename>/text/shared/explorer/database/02010100.xhp</filename>
+ <filename>/text/sdatabase/020010100.xhp</filename>
</topic>
</meta>
@@ -49,24 +49,24 @@
<comment>mw added "(Base)" to all entries</comment>
<paragraph id="par_id3153323" role="paragraph" localize="false"
xml-lang="en-US"/>
-<paragraph id="hd_id3153394" role="heading" level="1" xml-lang="en-US"><link
href="text/shared/explorer/database/02010100.xhp" name="Query Design">Query
Design</link></paragraph>
+<h1 id="hd_id3153394"><link href="text/sdatabase/020010100.xhp" name="Query
Design">Query Design</link></h1>
<paragraph id="par_id3156411" role="paragraph" xml-lang="en-US"><ahelp
hid=".">The <emph>Query Design View </emph>allows you to create and edit a
database query.</ahelp></paragraph>
<section id="howtoget">
<embed href="text/shared/00/00000450.xhp#entwab"/>
</section>
-<paragraph id="par_id7024140" role="note" xml-lang="en-US">Most databases use
queries to filter or to sort database tables to display records on your
computer. Views offer the same functionality as queries, but on the server
side. If your database is on a server that supports views, you can use views to
filter the records on the server to speed up the display time.</paragraph>
-<paragraph id="par_id3159176" role="note" xml-lang="en-US">Selecting the
<emph>Create View</emph> command from the <emph>Tables</emph> tab page of a
database document, you see the <emph>View Design</emph> window that resembles
the <emph>Query Design</emph> window described here.</paragraph>
+<note id="par_id7024140">Most databases use queries to filter or to sort
database tables to display records on your computer. Views offer the same
functionality as queries, but on the server side. If your database is on a
server that supports views, you can use views to filter the records on the
server to speed up the display time.</note>
+<note id="par_id3159176">Selecting the <emph>Create View</emph> command from
the <emph>Tables</emph> tab page of a database document, you see the <emph>View
Design</emph> window that resembles the <emph>Query Design</emph> window
described here.</note>
<paragraph id="par_id8307138" role="paragraph" xml-lang="en-US">The Query
Design window layout is stored with a created query, but cannot be stored with
a created view.</paragraph>
-<paragraph id="hd_id3149233" role="heading" level="2" xml-lang="en-US">The
Design View</paragraph>
+<h2 id="hd_id3149233">The Design View</h2>
<paragraph id="par_id3145673" role="paragraph" xml-lang="en-US">To create a
query, click the <emph>Queries</emph> icon in a database document, then click
<emph>Create Query in Design View</emph>.</paragraph>
-<paragraph id="par_id3150255" role="paragraph" xml-lang="en-US">The lower pane
of the Design View is where you <link
href="text/shared/explorer/database/02010100.xhp" name="define">define</link>
the query. To define a query, specify the database <link
href="text/shared/explorer/database/02010100.xhp" name="field names">field
names</link> to include and the <link
href="text/shared/explorer/database/02010100.xhp"
name="criteria">criteria</link> for displaying the fields. To rearrange the
columns in the lower pane of the Design View, drag a column header to a new
location, or select the column and press <switchinline select="sys"><caseinline
select="MAC">Command
+<paragraph id="par_id3150255" role="paragraph" xml-lang="en-US">The lower pane
of the Design View is where you <link href="text/sdatabase/020010100.xhp"
name="define">define</link> the query. To define a query, specify the database
<link href="text/sdatabase/020010100.xhp" name="field names">field names</link>
to include and the <link href="text/sdatabase/020010100.xhp"
name="criteria">criteria</link> for displaying the fields. To rearrange the
columns in the lower pane of the Design View, drag a column header to a new
location, or select the column and press <switchinline select="sys"><caseinline
select="MAC">Command
</caseinline><defaultinline>Ctrl</defaultinline></switchinline>+arrow
key.</paragraph>
<paragraph id="par_id3152474" role="paragraph" xml-lang="en-US">In the top of
the query Design View window, the <link href="text/shared/main0214.xhp"
name="icons">icons</link> of the <emph>Query Design</emph> Bar and the
<emph>Design</emph> bar are displayed.</paragraph>
<paragraph id="par_id3147559" role="paragraph" xml-lang="en-US">If you want to
test a query, double-click the query name in the database document. The query
result is displayed in a table similar to the Data Source View. Note: the table
displayed is only temporary.</paragraph>
-<paragraph id="hd_id8226264" role="heading" level="3" xml-lang="en-US">Keys in
Query Design View</paragraph>
+<h3 id="hd_id8226264">Keys in Query Design View</h3>
<table id="tbl_id1880855">
<tablerow>
@@ -104,67 +104,67 @@
</table>
-<paragraph id="hd_id3154939" role="heading" level="2"
xml-lang="en-US">Browse</paragraph>
+<h2 id="hd_id3154939">Browse</h2>
<paragraph id="par_id3148799" role="paragraph" xml-lang="en-US">When you open
the query design for the first time, you see a dialog in which you must first
select the table or query that will be the basis for your new query.</paragraph>
<bookmark xml-lang="en-US" branch="hid/DBACCESS_HID_CTL_QRYDGNTAB"
id="bm_id3150767" localize="false"/>
<paragraph id="par_id3144762" role="paragraph" xml-lang="en-US"><ahelp
hid="HID_CTL_QRYDGNTAB">Double-click fields to add them to the query.
Drag-and-drop to define relations.</ahelp></paragraph>
-<paragraph id="par_id3157894" role="note" xml-lang="en-US">While designing a
query, you cannot modify the selected tables.</paragraph>
+<note id="par_id3157894">While designing a query, you cannot modify the
selected tables.</note>
-<paragraph id="hd_id3149562" role="heading" level="3" xml-lang="en-US">Remove
tables</paragraph>
+<h3 id="hd_id3149562">Remove tables</h3>
<paragraph id="par_id3150685" role="paragraph" xml-lang="en-US">To remove the
table from Design View, click the upper border of the table window and display
the context menu. You can use the <emph>Delete</emph> command to remove the
table from the Design View. Another option is to press the Delete
key.</paragraph>
<section id="darstellungaendern">
-<paragraph id="hd_id3150012" role="heading" level="3" xml-lang="en-US">Move
table and modify table size</paragraph>
+<h3 id="hd_id3150012">Move table and modify table size</h3>
<paragraph id="par_id3146922" role="paragraph" xml-lang="en-US">You can resize
and arrange the tables according to your preferences. To move tables, drag the
upper border to the desired position. Enlarge or reduce the size in which the
table is displayed by positioning the mouse cursor on a border or on a corner
and dragging the table until it is the desired size.</paragraph>
</section>
-<paragraph id="hd_id3145365" role="heading" level="2" xml-lang="en-US">Table
Relations</paragraph>
+<h2 id="hd_id3145365">Table Relations</h2>
<paragraph id="par_id3154145" role="paragraph" xml-lang="en-US">If there are
data relations between a field name in one table and a field name in another
table, you can use these relations for your query.</paragraph>
<paragraph id="par_id3152577" role="paragraph" xml-lang="en-US">If, for
example, you have a spreadsheet for articles identified by an article number,
and a spreadsheet for customers in which you record all articles that a
customer orders using the corresponding article numbers, then there is a
relationship between the two "article number" data fields. If you now want to
create a query that returns all articles that a customer has ordered, you must
retrieve data from two spreadsheets. To do this, you must inform $[officename]
about the relationship which exists between the data in the two
spreadsheets.</paragraph>
<paragraph id="par_id3155302" role="paragraph" xml-lang="en-US">To do this,
click a field name in a table (for example, the field name "Item-Number" from
the Customer table), hold down the mouse button and then drag the field name to
the field name of the other table ("Item-Number" from the Item table). When you
release the mouse button, a line connecting the two fields between the two
table windows appears. The corresponding condition that the content of the two
field names must be identical is entered in the resulting SQL query.</paragraph>
<paragraph id="par_id3153876" role="paragraph" xml-lang="en-US">The creation
of a query that is based on several related sheets is only possible if you use
$[officename] as the interface for a relational database.</paragraph>
-<paragraph id="par_id3145646" role="note" xml-lang="en-US">You cannot access
tables from different databases in a query. Queries involving multiple tables
can only be created within one database.</paragraph>
+<note id="par_id3145646">You cannot access tables from different databases in
a query. Queries involving multiple tables can only be created within one
database.</note>
-<paragraph id="hd_id3153279" role="heading" level="3"
xml-lang="en-US">Specifying the relation type</paragraph>
+<h3 id="hd_id3153279">Specifying the relation type</h3>
<paragraph id="par_id3154791" role="paragraph" xml-lang="en-US">If you
double-click on the line connecting two linked fields or call the menu command
<emph>Insert - New Relation</emph>, you can specify the type of relation in the
<link href="text/shared/explorer/database/02010101.xhp"
name="Relations"><emph>Relations</emph></link> dialog.</paragraph>
<bookmark xml-lang="en-US" branch="hid/DBACCESS_HID_QUERY_EDIT_JOINCONNECTION"
id="bm_id3145253" localize="false"/>
<paragraph id="par_id3150094" role="paragraph" xml-lang="en-US"><ahelp
hid="HID_QUERY_EDIT_JOINCONNECTION" visibility="hidden">Edit Join
Properties.</ahelp> Alternatively, press Tab until the line is selected, then
press Shift+F10 to display the context menu and there choose the command
<emph>Edit</emph>. Some databases support only a subset of the possible join
types.</paragraph>
-<paragraph id="hd_id3155851" role="heading" level="3"
xml-lang="en-US">Deleting relations</paragraph>
+<h3 id="hd_id3155851">Deleting relations</h3>
<paragraph id="par_id3156178" role="paragraph" xml-lang="en-US">To delete a
relation between two tables, click the connection line and then press the
Delete key.</paragraph>
<paragraph id="par_id3150715" role="paragraph" xml-lang="en-US">Alternatively,
delete the respective entries in <emph>Fields involved </emph>in the
<emph>Relations</emph> dialog. Or press Tab until the connecting vector is
displayed highlighted, then press Shift+F10 to open the context menu and select
<emph>Delete </emph>command.</paragraph>
<bookmark xml-lang="en-US" branch="hid/DBACCESS_HID_CTL_QRYDGNCRIT"
id="bm_id3152972" localize="false"/>
-<paragraph id="hd_id3151208" role="heading" level="2"
xml-lang="en-US">Defining the query</paragraph>
+<h2 id="hd_id3151208">Defining the query</h2>
<paragraph id="par_id3158416" role="paragraph" xml-lang="en-US"><ahelp
hid="HID_CTL_QRYDGNCRIT">Select conditions to define the query.</ahelp> Each
column of the design table accepts a data field for the query. The conditions
in one row are linked with a Boolean AND.</paragraph>
-<paragraph id="hd_id3154161" role="heading" level="3"
xml-lang="en-US">Specifying field names</paragraph>
+<h3 id="hd_id3154161">Specifying field names</h3>
<paragraph id="par_id3146791" role="paragraph" xml-lang="en-US">First, select
all field names from the tables that you want to add to the query. You can do
this either by drag-and-drop or by double-clicking a field name in the table
window. With the drag-and-drop method, use the mouse to drag a field name from
the table window into the lower area of the query design window. As you do
this, you can decide which column in the query design window will receive the
selected field. A field name can also be selected by double-clicking. It will
then be added to the next free column in the query design window.</paragraph>
-<paragraph id="hd_id3150750" role="heading" level="3"
xml-lang="en-US">Deleting field names</paragraph>
+<h3 id="hd_id3150750">Deleting field names</h3>
<paragraph id="par_id3154479" role="paragraph" xml-lang="en-US">To remove a
field name from the query, click the column header of the field and choose the
<emph>Delete</emph> command on the context menu for the column.</paragraph>
-<paragraph id="hd_id3155764" role="heading" level="3" xml-lang="en-US">Saving
the query</paragraph>
+<h3 id="hd_id3155764">Saving the query</h3>
<paragraph id="par_id3148481" role="paragraph" xml-lang="en-US">Use the
<emph>Save</emph> icon on the Standard toolbar to save the query. You will see
a dialog that asks you to enter a name for the query. If the database supports
schemas, you can also enter a schema name.</paragraph>
<bookmark xml-lang="en-US" branch="hid/dbaccess/ui/savedialog/schema"
id="bm_id3156378" localize="false"/>
-<paragraph id="hd_id3154362" role="heading" level="4"
xml-lang="en-US">Schema</paragraph>
+<h4 id="hd_id3154362">Schema</h4>
<paragraph id="par_id3154754" role="paragraph" xml-lang="en-US"><ahelp
hid="dbaccess/ui/savedialog/schema">Enter the name of the schema that is
assigned to the query or table view.</ahelp></paragraph>
<bookmark xml-lang="en-US" branch="hid/dbaccess/ui/savedialog/title"
id="bm_id3147340" localize="false"/>
-<paragraph id="hd_id3156717" role="heading" level="4" xml-lang="en-US">Query
name or table view name</paragraph>
+<h4 id="hd_id3156717">Query name or table view name</h4>
<paragraph id="par_id3154253" role="paragraph" xml-lang="en-US"><ahelp
hid="dbaccess/ui/savedialog/title">Enter the name of the query or table
view.</ahelp></paragraph>
-<paragraph id="hd_id3163805" role="heading" level="3"
xml-lang="en-US">Filtering data</paragraph>
+<h3 id="hd_id3163805">Filtering data</h3>
<paragraph id="par_id3154964" role="paragraph" xml-lang="en-US">To filter data
for the query, set the desired criteria in the lower area of the query design
window. The following options are available:</paragraph>
<bookmark xml-lang="en-US" branch="hid/DBACCESS_HID_QRYDGN_ROW_FIELD"
id="bm_id3148536" localize="false"/>
-<paragraph id="hd_id3146916" role="heading" level="4"
xml-lang="en-US">Field</paragraph>
+<h4 id="hd_id3146916">Field</h4>
<paragraph id="par_id3156372" role="paragraph" xml-lang="en-US"><ahelp
hid="HID_QRYDGN_ROW_FIELD">Enter the name of the data field that is referred to
in the Query. All settings made in the filter option rows refer to this
field.</ahelp> If you activate a cell here with a mouse click you'll see an
arrow button, which enables you to select a field. The "Table name.*" option
selects all data fields with the effect that the specified criteria will be
applied to all table fields.</paragraph>
<bookmark xml-lang="en-US" branch="hid/DBACCESS_HID_QRYDGN_ROW_ALIAS"
id="bm_id3154702" localize="false"/>
-<paragraph id="hd_id3145150" role="heading" level="4"
xml-lang="en-US">Alias</paragraph>
+<h4 id="hd_id3145150">Alias</h4>
<paragraph id="par_id3146315" role="paragraph" xml-lang="en-US"><ahelp
hid="HID_QRYDGN_ROW_ALIAS">Specifies an alias. This alias will be listed in the
query instead of the field name. This makes it possible to use user-defined
column labels.</ahelp> For example, if the data field is named PtNo and,
instead of that name, you would like to have PartNum appear in the query, enter
PartNum as the alias.</paragraph>
<paragraph id="par_id3155959" role="paragraph" xml-lang="en-US">In a SQL
statement, aliases are defined as follows:</paragraph>
<paragraph id="par_id3149922" role="paragraph" xml-lang="en-US">SELECT column
AS alias FROM table.</paragraph>
@@ -172,27 +172,27 @@
<paragraph id="par_id3148478" role="paragraph" xml-lang="en-US">SELECT "PtNo"
AS "PartNum" FROM "Parts"</paragraph>
<bookmark xml-lang="en-US" branch="hid/DBACCESS_HID_QRYDGN_ROW_TABLE"
id="bm_id3154665" localize="false"/>
-<paragraph id="hd_id3148485" role="heading" level="4"
xml-lang="en-US">Table</paragraph>
+<h4 id="hd_id3148485">Table</h4>
<paragraph id="par_id3163665" role="paragraph" xml-lang="en-US"><ahelp
hid="HID_QRYDGN_ROW_TABLE">The corresponding database table of the selected
data field is listed here.</ahelp> If you activate this cell with a mouse
click, an arrow will appear which enables you to select a different table for
the current query.</paragraph>
<bookmark xml-lang="en-US" branch="hid/DBACCESS_HID_QRYDGN_ROW_ORDER"
id="bm_id3154202" localize="false"/>
-<paragraph id="hd_id3154207" role="heading" level="4"
xml-lang="en-US">Sort</paragraph>
+<h4 id="hd_id3154207">Sort</h4>
<paragraph id="par_id3150979" role="paragraph" xml-lang="en-US"><ahelp
hid="HID_QRYDGN_ROW_ORDER">If you click on this cell, you can choose a sort
option: ascending, descending and unsorted.</ahelp> Text fields will be sorted
alphabetically and numerical fields numerically. For most databases,
administrators can set the sorting options at the database level.</paragraph>
<bookmark xml-lang="en-US" branch="hid/DBACCESS_HID_QRYDGN_ROW_VISIBLE"
id="bm_id3149334" localize="false"/>
-<paragraph id="hd_id3150384" role="heading" level="4"
xml-lang="en-US">Visible</paragraph>
+<h4 id="hd_id3150384">Visible</h4>
<paragraph id="par_id3146133" role="paragraph" xml-lang="en-US"><ahelp
hid="HID_QRYDGN_ROW_VISIBLE">If you mark the <emph>Visible</emph> property for
a data field, that field will be visibly displayed in the resulting
query</ahelp>. If you are only using a data field to formulate a condition or
make a calculation, you do not necessarily need to display it.</paragraph>
<bookmark xml-lang="en-US" branch="hid/DBACCESS_HID_QRYDGN_ROW_CRIT"
id="bm_id3147130" localize="false"/>
-<paragraph id="hd_id3154714" role="heading" level="4"
xml-lang="en-US">Criteria</paragraph>
-<paragraph id="par_id3145134" role="paragraph" xml-lang="en-US"><ahelp
hid="HID_QRYDGN_ROW_CRIT">Specifies a first <link
href="text/shared/explorer/database/02010100.xhp" name="criteria ">criteria
</link>by which the content of the data field is to be
filtered.</ahelp></paragraph>
+<h4 id="hd_id3154714">Criteria</h4>
+<paragraph id="par_id3145134" role="paragraph" xml-lang="en-US"><ahelp
hid="HID_QRYDGN_ROW_CRIT">Specifies a first <link
href="text/sdatabase/020010100.xhp" name="criteria ">criteria </link>by which
the content of the data field is to be filtered.</ahelp></paragraph>
-<paragraph id="hd_id3152477" role="heading" level="4"
xml-lang="en-US">or</paragraph>
+<h4 id="hd_id3152477">or</h4>
<paragraph id="par_id3154585" role="paragraph" xml-lang="en-US">Here you can
enter one additional filter criterion for each line. Multiple criteria in a
single column will be interpreted as boolean OR.</paragraph>
<paragraph id="par_id3148800" role="paragraph" xml-lang="en-US">You can also
use the context menu of the line headers in the lower area of the query design
window to insert a filter based on a function:</paragraph>
<bookmark xml-lang="en-US" branch="hid/DBACCESS_HID_QRYDGN_ROW_FUNCTION"
id="bm_id3153275" localize="false"/>
-<paragraph id="hd_id3148419" role="heading" level="3"
xml-lang="en-US">Functions</paragraph>
+<h3 id="hd_id3148419">Functions</h3>
<paragraph id="par_id3153233" role="paragraph" xml-lang="en-US"><ahelp
hid="HID_QRYDGN_ROW_FUNCTION" visibility="hidden">Select a function to run in
the query.</ahelp> The functions which are available here depend on those
provided by the database engine. </paragraph>
<paragraph id="par_id8760818" role="paragraph" xml-lang="en-US">If you are
working with the embedded HSQL database, the list box in the
<emph>Function</emph> row offers you the following options:</paragraph>
@@ -299,7 +299,7 @@
<paragraph id="par_id3149425" role="paragraph" xml-lang="en-US">SELECT
FUNCTION() AS alias FROM table</paragraph>
<paragraph id="par_id3144431" role="paragraph"
xml-lang="en-US">Example:</paragraph>
<paragraph id="par_id3154614" role="paragraph" xml-lang="en-US">SELECT
COUNT(*) AS count FROM "Item"</paragraph>
-<paragraph id="par_id3154610" role="note" xml-lang="en-US">If you run such a
function, you cannot insert any additional columns for the query other than as
an argument in a "Group" function.</paragraph>
+<note id="par_id3154610">If you run such a function, you cannot insert any
additional columns for the query other than as an argument in a "Group"
function.</note>
<paragraph id="par_id3154644" role="paragraph" xml-lang="en-US">
<emph>Examples</emph> </paragraph>
<paragraph id="par_id3151120" role="paragraph" xml-lang="en-US">In the
following example, a query is run through two tables: an "Item" table with the
"Item_No" field and a "Suppliers" table with the "Supplier_Name" field. In
addition, both tables have a common field name "Supplier_No."</paragraph>
<paragraph id="par_id3155144" role="paragraph" xml-lang="en-US">The following
steps are required to create a query containing all suppliers who deliver more
than three items.</paragraph>
@@ -348,26 +348,26 @@
</list>
<paragraph id="par_id3147549" role="paragraph" xml-lang="en-US">The following
context menu commands and symbols are available:</paragraph>
-<paragraph id="hd_id3154172" role="heading" level="3"
xml-lang="en-US">Functions</paragraph>
+<h3 id="hd_id3154172">Functions</h3>
<paragraph id="par_id3150414" role="paragraph" xml-lang="en-US"><ahelp
hid="HID_QRYDGN_ROW_FUNCTION">Shows or hides a row for the selection of
functions.</ahelp></paragraph>
-<paragraph id="hd_id3149872" role="heading" level="3" xml-lang="en-US">Table
Name</paragraph>
+<h3 id="hd_id3149872">Table Name</h3>
<paragraph id="par_id3147246" role="paragraph" xml-lang="en-US"><ahelp
hid="HID_QRYDGN_ROW_FUNCTION">Shows or hides the row for the table
name.</ahelp></paragraph>
-<paragraph id="hd_id3145117" role="heading" level="3" xml-lang="en-US">Alias
Name</paragraph>
+<h3 id="hd_id3145117">Alias Name</h3>
<paragraph id="par_id3155754" role="paragraph" xml-lang="en-US"><ahelp
hid="HID_QRYDGN_ROW_FUNCTION">Shows or hides the row for the alias
name.</ahelp></paragraph>
-<paragraph id="hd_id3153298" role="heading" level="3"
xml-lang="en-US">Distinct Values</paragraph>
+<h3 id="hd_id3153298">Distinct Values</h3>
<paragraph id="par_id3147500" role="paragraph" xml-lang="en-US"><ahelp
hid="HID_QRYDGN_ROW_FUNCTION">Retrieves only distinct values from the
query.</ahelp> This applies to multiple records that might contain several
repeating occurrences of data in the selected fields. If the <emph>Distinct
Values</emph> command is active, you should only see one record in the query
(DISTINCT). Otherwise, you will see all records corresponding to the query
criteria (ALL).</paragraph>
<paragraph id="par_id3150436" role="paragraph" xml-lang="en-US">For example,
if the name "Smith" occurs several times in your address database, you can
choose the<emph> Distinct Values</emph> command to specify in the query that
the name "Smith" will occur only once.</paragraph>
<paragraph id="par_id3152352" role="paragraph" xml-lang="en-US">For a query
involving several fields, the combination of values from all fields must be
unique so that the result can be formed from a specific record. For example,
you have "Smith in Chicago" once in your address book and "Smith in London"
twice. With the<emph> Distinct Values</emph> command, the query will use the
two fields "last name" and "city" and return the query result "Smith in
Chicago" once and "Smith in London" once.</paragraph>
<paragraph id="par_id3149825" role="paragraph" xml-lang="en-US">In SQL, this
command corresponds to the DISTINCT predicate.</paragraph>
-<paragraph id="hd_id3153290" role="heading" level="3"
xml-lang="en-US">Limit</paragraph>
+<h3 id="hd_id3153290">Limit</h3>
<paragraph id="par_id3147501" role="paragraph" xml-lang="en-US"><ahelp
hid="HID_QRYDGN_ROW_FUNCTION">Allows you to limit the maximum number of records
returned by a query.</ahelp></paragraph>
<paragraph id="par_id3152350" role="paragraph" xml-lang="en-US">If a
<emph>Limit</emph> construction is added, you will get at most as many rows as
the number you specify. Otherwise, you will see all records corresponding to
the query criteria.</paragraph>
-<paragraph id="hd_id3148926" role="heading" level="3"
xml-lang="en-US">Formulating filter conditions</paragraph>
+<h3 id="hd_id3148926">Formulating filter conditions</h3>
<section id="abfragekriterien">
<paragraph id="par_id3153162" role="paragraph" xml-lang="en-US">When
formulating filter conditions, various operators and commands are available to
you. Apart from the relational operators, there are SQL-specific commands that
query the content of database fields. If you use these commands in the
$[officename] syntax, $[officename] automatically converts these into the
corresponding SQL syntax via an internal parser. You can also enter the SQL
command directly and bypass the internal parser. The following tables give an
overview of the operators and commands:</paragraph>
@@ -622,7 +622,7 @@
</table>
-<paragraph id="hd_id3155954" role="heading" level="3"
xml-lang="en-US">Examples</paragraph>
+<h3 id="hd_id3155954">Examples</h3>
<table id="tbl_id3083279">
<tablerow>
@@ -690,10 +690,10 @@
<paragraph id="par_id3150572" role="paragraph" xml-lang="en-US"> <emph>Outer
Join</emph> Escape Sequence: {oj outer-join}</paragraph>
<paragraph id="par_id3156052" role="paragraph" xml-lang="en-US">Example:
select Article.* from {oj item LEFT OUTER JOIN orders ON
item.no=orders.ANR}</paragraph>
-<paragraph id="hd_id3153674" role="heading" level="3"
xml-lang="en-US">Querying text fields</paragraph>
+<h3 id="hd_id3153674">Querying text fields</h3>
<paragraph id="par_id3149134" role="paragraph" xml-lang="en-US">To query the
content of a text field, you must put the expression between single quotes. The
distinction between uppercase and lowercase letters depends on the database in
use. LIKE, by definition, is case-sensitive (though some databases don't
interpret this strictly).</paragraph>
-<paragraph id="hd_id3149302" role="heading" level="3"
xml-lang="en-US">Querying date fields</paragraph>
+<h3 id="hd_id3149302">Querying date fields</h3>
<paragraph id="par_id3157998" role="paragraph" xml-lang="en-US"> <emph>Date
fields</emph> are represented as #Date# to clearly identify them as dates.
Date, time and date/time constants (literals) used in conditions can be of
either the SQL Escape Syntax type, or default SQL2 syntax.</paragraph>
<table id="tbl_id3156186">
@@ -759,7 +759,7 @@
<paragraph id="par_id3149540" role="paragraph" xml-lang="en-US">Example:
select * from mytable where years='1999-12-31' </paragraph>
<paragraph id="par_id3150510" role="paragraph" xml-lang="en-US">All date
expressions (date literals) must be enclosed with single quotation marks.
(Consult the reference for the particular database and connector you are using
for more details.)</paragraph>
-<paragraph id="hd_id3150427" role="heading" level="3"
xml-lang="en-US">Querying Yes/No fields</paragraph>
+<h3 id="hd_id3150427">Querying Yes/No fields</h3>
<paragraph id="par_id3149523" role="paragraph" xml-lang="en-US">To query
Yes/No fields, use the following syntax for dBASE tables:</paragraph>
<table id="tbl_id3150146">
@@ -809,23 +809,23 @@
</tablerow>
</table>
-<paragraph id="par_id3157888" role="note" xml-lang="en-US">The syntax depends
on the database system used. You should also note that Yes/No fields can be
defined differently (only 2 states instead of 3).</paragraph>
+<note id="par_id3157888">The syntax depends on the database system used. You
should also note that Yes/No fields can be defined differently (only 2 states
instead of 3).</note>
-<paragraph id="hd_id3145772" role="heading" level="3"
xml-lang="en-US">Parameter queries</paragraph>
+<h3 id="hd_id3145772">Parameter queries</h3>
<paragraph id="par_id191120151905346795" role="paragraph"
xml-lang="en-US">Parameter queries allow the user to input values at run-time.
These values are used within the criteria for selecting the records to be
displayed. Each such value has a parameter name associated with it, which is
used to prompt the user when the query is run. </paragraph>
<paragraph id="par_id191120151905439551" role="paragraph"
xml-lang="en-US">Parameter names are preceded by a colon in both the Design and
SQL views of a query. This can be used wherever a value can appear. If the same
value is to appear more than once in the query, the same parameter name is
used.</paragraph>
-<paragraph id="par_id191120151905518123" role="paragraph" xml-lang="en-US">In
the simplest case, where the user enters a value which is matched for equality,
the parameter name with its preceding colon is simply entered in the Criterion
row. In <link href="text/shared/explorer/database/02010100.xhp#sqlmode">SQL
mode</link> this should be typed as <item type="input">WHERE "Field" =
:Parameter_name</item></paragraph>
-<paragraph id="par_id191120151905584287" role="warning"
xml-lang="en-US">Parameter names may not contain any of the characters <item
type="input"><space>`!"$%^*()+={}[]@'~#<>?/,</item>. They may not
be the same as field names or SQL reserved words. They may be the same as
aliases.</paragraph>
-<paragraph id="par_id191120151931441881" role="tip" xml-lang="en-US">A useful
construction for selecting records based on parts of a text field's content is
to add a hidden column with <item type="input">"LIKE '%' || :Part_of_field ||
'%'"</item> as the criterion. This will select records with an exact match. If
a case-insensitive test is wanted, one solution is to use <item
type="input">LOWER (Field_Name)</item> as the field and <item type="input">LIKE
LOWER ( '%' || :Part_of_field || '%' )</item> as the criterion. Note that the
spaces in the criterion are important; if they are left out the SQL parser
interprets the entire criterion as a string to be matched. In <link
href="text/shared/explorer/database/02010100.xhp#sqlmode">SQL mode</link> this
should be typed as <item type="input">LOWER ( "Field_Name" ) LIKE LOWER ( '%'
|| :Part_of_field || '%' )</item>.</paragraph>
+<paragraph id="par_id191120151905518123" role="paragraph" xml-lang="en-US">In
the simplest case, where the user enters a value which is matched for equality,
the parameter name with its preceding colon is simply entered in the Criterion
row. In <link href="text/sdatabase/020010100.xhp#sqlmode">SQL mode</link> this
should be typed as <item type="input">WHERE "Field" =
:Parameter_name</item></paragraph>
+<warning id="par_id191120151905584287">Parameter names may not contain any of
the characters <item
type="input"><space>`!"$%^*()+={}[]@'~#<>?/,</item>. They may not
be the same as field names or SQL reserved words. They may be the same as
aliases.</warning>
+<tip id="par_id191120151931441881">A useful construction for selecting records
based on parts of a text field's content is to add a hidden column with <item
type="input">"LIKE '%' || :Part_of_field || '%'"</item> as the criterion. This
will select records with an exact match. If a case-insensitive test is wanted,
one solution is to use <item type="input">LOWER (Field_Name)</item> as the
field and <item type="input">LIKE LOWER ( '%' || :Part_of_field || '%' )</item>
as the criterion. Note that the spaces in the criterion are important; if they
are left out the SQL parser interprets the entire criterion as a string to be
matched. In <link href="text/sdatabase/020010100.xhp#sqlmode">SQL mode</link>
this should be typed as <item type="input">LOWER ( "Field_Name" ) LIKE LOWER (
'%' || :Part_of_field || '%' )</item>.</tip>
<paragraph id="par_id3150585" role="paragraph" xml-lang="en-US">Parameter
queries may be used as the data source for <link
href="text/shared/02/01170203.xhp" name="subforms">subforms</link>, to allow
the user to restrict the displayed records.</paragraph>
-<paragraph id="hd_id3151035" role="heading" level="3"
xml-lang="en-US">Parameter Input</paragraph>
+<h3 id="hd_id3151035">Parameter Input</h3>
<paragraph id="par_id3153596" role="paragraph" xml-lang="en-US"><ahelp
hid="HID_QRYDGN_ROW_FUNCTION">The <emph>Parameter Input</emph> dialog asks the
user to enter the parameter values. Enter a value for each query parameter and
confirm by clicking <emph>OK</emph> or typing
<emph>Enter</emph>.</ahelp></paragraph>
<paragraph id="par_id191120151924165870" role="paragraph" xml-lang="en-US">The
values entered by the user may consist of any characters which are allowable
for the SQL for the relevant criterion; this may depend on the underlying
database system.</paragraph>
-<paragraph id="par_id191120151939594217" role="tip" xml-lang="en-US">The user
can use the SQL wild-card characters "%" (arbitrary string) or "_" (arbitrary
single character) as part of the value to retrieve records with more complex
criteria.</paragraph>
+<tip id="par_id191120151939594217">The user can use the SQL wild-card
characters "%" (arbitrary string) or "_" (arbitrary single character) as part
of the value to retrieve records with more complex criteria.</tip>
<section id="sqlmode">
-<paragraph id="hd_id3145181" role="heading" level="2" xml-lang="en-US">SQL
Mode</paragraph>
+<h2 id="hd_id3145181">SQL Mode</h2>
<paragraph id="par_id3147013" role="paragraph" xml-lang="en-US">SQL stands for
"Structured Query Language" and describes instructions for updating and
administering relational databases.</paragraph>
<paragraph id="par_id3152570" role="paragraph" xml-lang="en-US">In
$[officename] you do not need any knowledge of SQL for most queries, since you
do not have to enter the SQL code. If you create a query in the query designer,
$[officename] automatically converts your instructions into the corresponding
SQL syntax. If, with the help of the <emph>Switch Design View On/Off
</emph>button, you change to the SQL view, you can see the SQL commands for a
query that has already been created.</paragraph>
<paragraph id="par_id3152412" role="paragraph" xml-lang="en-US">You can
formulate your query directly in SQL code. Note, however, that the special
syntax is dependent upon the database system that you use.</paragraph>
diff --git a/source/text/shared/02/01170203.xhp
b/source/text/shared/02/01170203.xhp
index 61dde6522..bb9cc85e6 100644
--- a/source/text/shared/02/01170203.xhp
+++ b/source/text/shared/02/01170203.xhp
@@ -143,7 +143,7 @@
<section id="Section13">
<bookmark xml-lang="en-US" branch="hid/EXTENSIONS_HID_PROP_MASTERFIELDS"
id="bm_id3147097" localize="false"/><paragraph role="heading" id="hd_id3153714"
xml-lang="en-US" level="2">Link master fields</paragraph>
<paragraph role="paragraph" id="par_id3147339" xml-lang="en-US"><ahelp
hid=".">If you create a <link href="text/shared/02/01170203.xhp"
name="subform">subform</link>, enter the data field of the parent form
responsible for the synchronization between parent and subform.</ahelp> To
enter multiple values, press Shift + Enter after each input line.<comment>UFI:
fixes #i22439#</comment></paragraph>
-<paragraph role="paragraph" id="par_id3149568" xml-lang="en-US">The subform is
based on an <link href="text/shared/00/00000005.xhp#sql" name="SQL">SQL</link>
query; more specifically, on a <link
href="text/shared/explorer/database/02010100.xhp" name="Parameter
Query">Parameter Query</link>. If a field name is entered in the <emph>Link
master fields</emph> box, the data contained in that field in the main form is
read to a variable that you must enter in <emph>Link slave fields</emph>. In an
appropriate SQL statement, this variable is compared to the table data that the
subform refers to. Alternatively, you can enter the column name in the
<emph>Link master fields</emph> box.</paragraph>
+<paragraph role="paragraph" id="par_id3149568" xml-lang="en-US">The subform is
based on an <link href="text/shared/00/00000005.xhp#sql" name="SQL">SQL</link>
query; more specifically, on a <link href="text/sdatabase/02010100.xhp"
name="Parameter Query">Parameter Query</link>. If a field name is entered in
the <emph>Link master fields</emph> box, the data contained in that field in
the main form is read to a variable that you must enter in <emph>Link slave
fields</emph>. In an appropriate SQL statement, this variable is compared to
the table data that the subform refers to. Alternatively, you can enter the
column name in the <emph>Link master fields</emph> box.</paragraph>
<paragraph role="paragraph" id="par_id3156089" xml-lang="en-US">Consider the
following example:</paragraph>
<paragraph role="paragraph" id="par_id3151017" xml-lang="en-US">The database
table on which the form is based is, for example, a customer database
("Customer"), where every customer has been given a unique number in a data
field named "Cust_ID". A customer's orders are maintained in another database
table. You now want to see each customer's orders after entering them into the
form. In order to do this you should create a subform. Under <emph>Link master
fields</emph> enter the data field from the customer database which clearly
identifies the customer, that is, Cust_ID. Under <emph>Link slave fields</emph>
enter the name of a variable which is to accept the data of the field Cust_ID,
for example, x.</paragraph>
<paragraph role="paragraph" id="par_id3151248" xml-lang="en-US">The subform
should show the appropriate data from the orders table ("Orders") for each
customer ID (Customer_ID -> x). This is only possible if each order is
uniquely assigned to one customer in the orders table. Alternatively, you can
use another field called Customer_ID; however, to make sure that this field is
not confused with the same field from the main form, the field is called
Customer_Number.</paragraph>
diff --git a/source/text/shared/02/14030000.xhp
b/source/text/shared/02/14030000.xhp
index d011d2eb6..fd15006c2 100644
--- a/source/text/shared/02/14030000.xhp
+++ b/source/text/shared/02/14030000.xhp
@@ -47,6 +47,6 @@
</tablerow>
</table>
</section>
-<paragraph role="paragraph" id="par_id3155535" xml-lang="en-US">Click the icon
again to return to normal mode, in which the changes in the <link
href="text/shared/explorer/database/02010100.xhp" name="New Query
Design"><emph>New Query Design</emph></link> are synchronized with the
permitted changes through SQL.</paragraph>
+<paragraph role="paragraph" id="par_id3155535" xml-lang="en-US">Click the icon
again to return to normal mode, in which the changes in the <link
href="text/sdatabase/02010100.xhp" name="New Query Design"><emph>New Query
Design</emph></link> are synchronized with the permitted changes through
SQL.</paragraph>
</body>
</helpdocument>
diff --git a/source/text/shared/02/14040000.xhp
b/source/text/shared/02/14040000.xhp
index ab4f62f72..6d4e23283 100644
--- a/source/text/shared/02/14040000.xhp
+++ b/source/text/shared/02/14040000.xhp
@@ -31,7 +31,7 @@
<section id="funktionen">
<bookmark branch="hid/.uno:DBViewFunctions" xml-lang="en-US" id="bm_id3154840"
localize="false"/>
<h1 id="hd_id3153514"><link href="text/shared/02/14040000.xhp"
name="Functions">Functions</link></h1>
-<paragraph role="paragraph" id="par_id3159224" xml-lang="en-US"><ahelp
visibility="visible" hid=".uno:DBViewFunctions">Displays the
<emph>Function</emph> row in the lower part of the design view of the <link
href="text/shared/explorer/database/02010100.xhp" name="Query
Design"><emph>Query Design</emph></link> window.</ahelp></paragraph>
+<paragraph role="paragraph" id="par_id3159224" xml-lang="en-US"><ahelp
visibility="visible" hid=".uno:DBViewFunctions">Displays the
<emph>Function</emph> row in the lower part of the design view of the <link
href="text/sdatabase/02010100.xhp" name="Query Design"><emph>Query
Design</emph></link> window.</ahelp></paragraph>
</section>
<section id="syfunktionen">
<table id="tbl_id3149119">
diff --git a/source/text/shared/02/14050000.xhp
b/source/text/shared/02/14050000.xhp
index 999139402..051363474 100644
--- a/source/text/shared/02/14050000.xhp
+++ b/source/text/shared/02/14050000.xhp
@@ -31,7 +31,7 @@
<section id="tabellenname">
<bookmark xml-lang="en-US" branch="hid/.uno:DBViewTableNames"
id="bm_id2447279" localize="false"/>
<paragraph role="heading" id="hd_id3149991" xml-lang="en-US" level="1"><link
href="text/shared/02/14050000.xhp" name="Table Name">Table
Name</link></paragraph>
-<paragraph role="paragraph" id="par_id3154232" xml-lang="en-US"><ahelp
hid=".">Displays the <emph>Table</emph> row in the lower part of the <link
href="text/shared/explorer/database/02010100.xhp" name="Query
Design"><emph>Query Design</emph></link>.</ahelp></paragraph>
+<paragraph role="paragraph" id="par_id3154232" xml-lang="en-US"><ahelp
hid=".">Displays the <emph>Table</emph> row in the lower part of the <link
href="text/sdatabase/02010100.xhp" name="Query Design"><emph>Query
Design</emph></link>.</ahelp></paragraph>
</section>
<section id="sytabellenname">
<table id="tbl_id3147102">
diff --git a/source/text/shared/02/14060000.xhp
b/source/text/shared/02/14060000.xhp
index d518d243a..db7ef69a1 100644
--- a/source/text/shared/02/14060000.xhp
+++ b/source/text/shared/02/14060000.xhp
@@ -31,7 +31,7 @@
<section id="aliasname">
<bookmark branch="hid/.uno:DBViewAliases" xml-lang="en-US" id="bm_id3151299"
localize="false"/>
<h1 id="hd_id3150758"><link href="text/shared/02/14060000.xhp"
name="Alias">Alias</link></h1>
-<paragraph role="paragraph" id="par_id3148731" xml-lang="en-US"><ahelp
visibility="visible" hid=".uno:DBViewAliases">Displays the <emph>Alias</emph>
row in the lower part of the <link
href="text/shared/explorer/database/02010100.xhp" name="Query
Design"><emph>Query Design</emph></link>.</ahelp></paragraph>
+<paragraph role="paragraph" id="par_id3148731" xml-lang="en-US"><ahelp
visibility="visible" hid=".uno:DBViewAliases">Displays the <emph>Alias</emph>
row in the lower part of the <link href="text/sdatabase/02010100.xhp"
name="Query Design"><emph>Query Design</emph></link>.</ahelp></paragraph>
</section>
<section id="syaliasname">
<table id="tbl_id3149716">
diff --git a/source/text/shared/02/14070000.xhp
b/source/text/shared/02/14070000.xhp
index b30a02f69..94a2cb402 100644
--- a/source/text/shared/02/14070000.xhp
+++ b/source/text/shared/02/14070000.xhp
@@ -34,7 +34,7 @@
</bookmark>
<bookmark xml-lang="en-US" branch="hid/.uno:DBDistinctValues"
id="bm_id3147588" localize="false"/>
<h1 id="hd_id3149991"><link href="text/shared/02/14070000.xhp" name="Distinct
Values">Distinct Values</link></h1>
-<paragraph role="paragraph" id="par_id3154894" xml-lang="en-US"><ahelp
hid=".uno:DBDistinctValues">Expands the created select statement of the <link
href="text/shared/explorer/database/02010100.xhp" name="SQL Query"><emph>SQL
Query</emph></link> in the current column by the parameter
<emph>DISTINCT</emph>.</ahelp> The consequence is that identical values
occurring multiple times are listed only once.</paragraph>
+<paragraph role="paragraph" id="par_id3154894" xml-lang="en-US"><ahelp
hid=".uno:DBDistinctValues">Expands the created select statement of the <link
href="text/sdatabase/02010100.xhp" name="SQL Query"><emph>SQL
Query</emph></link> in the current column by the parameter
<emph>DISTINCT</emph>.</ahelp> The consequence is that identical values
occurring multiple times are listed only once.</paragraph>
</section>
<section id="syeindeutige">
<table id="tbl_id3150935">
diff --git a/source/text/shared/02/limit.xhp b/source/text/shared/02/limit.xhp
index 1104855a8..9378df9ae 100644
--- a/source/text/shared/02/limit.xhp
+++ b/source/text/shared/02/limit.xhp
@@ -21,6 +21,6 @@
</bookmark>
<paragraph role="heading" id="hd_id3149991" xml-lang="en-US"
level="1">Limit</paragraph>
<bookmark xml-lang="en-US" branch="hid/.uno:DBLimit" id="bm_id3147588"
localize="false"/>
-<paragraph role="paragraph" id="par_id3154894" xml-lang="en-US"><ahelp
hid=".">Expands the created select statement of the <link
href="text/shared/explorer/database/02010100.xhp" name="SQL Query">SQL
Query</link> by the LIMIT X clause</ahelp>. This can be used to limit your SQL
Query results to those that fall within the first X number of it.</paragraph>
+<paragraph role="paragraph" id="par_id3154894" xml-lang="en-US"><ahelp
hid=".">Expands the created select statement of the <link
href="text/sdatabase/02010100.xhp" name="SQL Query">SQL Query</link> by the
LIMIT X clause</ahelp>. This can be used to limit your SQL Query results to
those that fall within the first X number of it.</paragraph>
</body>
</helpdocument>
diff --git a/source/text/shared/explorer/database/05020000.xhp
b/source/text/shared/explorer/database/05020000.xhp
index 96a89ef00..7f65f5324 100644
--- a/source/text/shared/explorer/database/05020000.xhp
+++ b/source/text/shared/explorer/database/05020000.xhp
@@ -43,7 +43,7 @@
<embed href="text/shared/00/00000450.xhp#sytabelle"/>
<paragraph role="note" id="par_id3152812" xml-lang="en-US">If the
<emph>Relation Design</emph> window is open, the selected tables cannot be
modified, even in Table Design mode. This ensures that tables are not changed
while the relations are being created.</paragraph>
<paragraph role="paragraph" id="par_id3150541" xml-lang="en-US">The selected
tables are shown in the top area of the relation design view. You can close a
table window through the context menu or with the Delete key.</paragraph>
-<embed href="text/shared/explorer/database/02010100.xhp#darstellungaendern"/>
+<embed href="text/sdatabase/02010100.xhp#darstellungaendern"/>
<bookmark xml-lang="en-US" branch="index"
id="bm_id3148922"><bookmark_value>primary keys;inserting (Base)</bookmark_value>
<bookmark_value>keys;primary keys (Base)</bookmark_value>
<bookmark_value>external keys (Base)</bookmark_value>
diff --git a/source/text/shared/explorer/database/11080000.xhp
b/source/text/shared/explorer/database/11080000.xhp
index c8fd3726e..38ac0e0a6 100644
--- a/source/text/shared/explorer/database/11080000.xhp
+++ b/source/text/shared/explorer/database/11080000.xhp
@@ -40,7 +40,7 @@
</section>
<embed href="text/shared/guide/data_enter_sql.xhp#data_enter_sql"/>
<paragraph role="paragraph" id="par_id3147275" xml-lang="en-US">You can only
enter administration commands in this dialog, such as Grant, Create Table, or
Drop Table, and not filter commands. The commands that you can enter depend on
the data source, for example, dBASE can only run some of the SQL commands list
here.</paragraph>
-<paragraph role="note" id="par_id3154860" xml-lang="en-US">To run an SQL query
for filtering data in the database, use the <link
href="text/shared/explorer/database/02010100.xhp" name="Query Design">Query
Design View</link>.</paragraph>
+<paragraph role="note" id="par_id3154860" xml-lang="en-US">To run an SQL query
for filtering data in the database, use the <link
href="text/sdatabase/02010100.xhp" name="Query Design">Query Design
View</link>.</paragraph>
<bookmark xml-lang="en-US" branch="hid/dbaccess/ui/directsqldialog/sql"
id="bm_id3150772" localize="false"/><paragraph role="heading" id="hd_id3149514"
xml-lang="en-US" level="2">Command to execute</paragraph>
<paragraph role="paragraph" id="par_id3147618" xml-lang="en-US"><ahelp
hid="dbaccess/ui/directsqldialog/sql">Enter the SQL administration command that
you want to run.</ahelp></paragraph>
<paragraph role="paragraph" id="par_id3153087" xml-lang="en-US">For example,
for a "Bibliography" data source, you can enter the following SQL
command:</paragraph>
diff --git a/source/text/shared/guide/data_enter_sql.xhp
b/source/text/shared/guide/data_enter_sql.xhp
index 227039c73..c7268b251 100644
--- a/source/text/shared/guide/data_enter_sql.xhp
+++ b/source/text/shared/guide/data_enter_sql.xhp
@@ -67,7 +67,7 @@
</listitem>
</list>
<section id="relatedtopics">
- <paragraph xml-lang="en-US" id="par_id3153223" role="paragraph"><link
href="text/shared/explorer/database/02010100.xhp" name="Query Design">Query
Design</link></paragraph>
+ <paragraph xml-lang="en-US" id="par_id3153223" role="paragraph"><link
href="text/sdatabase/02010100.xhp" name="Query Design">Query
Design</link></paragraph>
<embed href="text/shared/guide/database_main.xhp#database_main"/>
</section>
</body>
diff --git a/source/text/shared/guide/data_queries.xhp
b/source/text/shared/guide/data_queries.xhp
index 96fd55860..b7347fffc 100644
--- a/source/text/shared/guide/data_queries.xhp
+++ b/source/text/shared/guide/data_queries.xhp
@@ -65,7 +65,7 @@
<paragraph role="paragraph" id="par_idN10658" xml-lang="en-US">Click
<emph>Create Query in Design View</emph>.</paragraph>
</listitem>
</list>
-<paragraph role="paragraph" id="par_idN1065F" xml-lang="en-US">You see the
<link href="text/shared/explorer/database/02010100.xhp">Query Design
window</link>.</paragraph>
+<paragraph role="paragraph" id="par_idN1065F" xml-lang="en-US">You see the
<link href="text/sdatabase/02010100.xhp">Query Design window</link>.</paragraph>
<section id="relatedtopics">
<paragraph role="paragraph" id="par_idN1067B" xml-lang="en-US"
localize="false">
<embedvar href="text/sdatabase/main.xhp#base"/>
diff --git a/source/text/shared/guide/data_search2.xhp
b/source/text/shared/guide/data_search2.xhp
index 2cf00dacd..bcfbe5d5c 100644
--- a/source/text/shared/guide/data_search2.xhp
+++ b/source/text/shared/guide/data_search2.xhp
@@ -58,7 +58,7 @@
<paragraph role="paragraph" id="par_id3149666" xml-lang="en-US">Enter the
filter conditions into one or several fields. Note that if you enter filter
conditions into several fields, all of the entered conditions must match
(Boolean AND).</paragraph>
</listitem>
</list>
-<paragraph role="paragraph" id="par_id3149481" xml-lang="en-US">More
information about wildcards and operators can be found in <link
href="text/shared/explorer/database/02010100.xhp" name="Query Design">Query
Design</link>. </paragraph>
+<paragraph role="paragraph" id="par_id3149481" xml-lang="en-US">More
information about wildcards and operators can be found in <link
href="text/sdatabase/02010100.xhp" name="Query Design">Query Design</link>.
</paragraph>
<bookmark xml-lang="en-US" branch="hid/.uno:FormFilterExecute"
id="bm_id9819688" localize="false"/>
<paragraph role="paragraph" id="par_id3152462" xml-lang="en-US"><ahelp
hid=".uno:FormFilterExecute">If you click the <emph>Apply Form-Based
Filter</emph> icon on the <emph>Form Filter</emph> toolbar, the filter will be
applied.</ahelp> You see the <emph>Form Navigation</emph> toolbar and can
browse through the found records.</paragraph>
<bookmark xml-lang="en-US" branch="hid/.uno:FormFilterExit" id="bm_id2865336"
localize="false"/>
diff --git a/source/text/shared/guide/data_tables.xhp
b/source/text/shared/guide/data_tables.xhp
index 3e68c6aa6..8b3ecfcce 100644
--- a/source/text/shared/guide/data_tables.xhp
+++ b/source/text/shared/guide/data_tables.xhp
@@ -76,7 +76,7 @@
<paragraph role="paragraph" id="par_idN1078E" xml-lang="en-US">Click
<emph>Create Table View</emph>.</paragraph>
</listitem>
</list>
-<paragraph role="paragraph" id="par_idN10795" xml-lang="en-US">You see the
View Design window, which is almost the same as the <link
href="text/shared/explorer/database/02010100.xhp">Query Design
window</link>.</paragraph>
+<paragraph role="paragraph" id="par_idN10795" xml-lang="en-US">You see the
View Design window, which is almost the same as the <link
href="text/sdatabase/020010100.xhp">Query Design window</link>.</paragraph>
<section id="relatedtopics">
<paragraph role="paragraph" id="par_idN1067B" xml-lang="en-US"
localize="false">
<embedvar href="text/sdatabase/main.xhp#base"/>
_______________________________________________
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
