diff options
Diffstat (limited to 'helpcontent2/source/text/shared/02/12100200.xhp')
| -rw-r--r-- | helpcontent2/source/text/shared/02/12100200.xhp | 297 |
1 files changed, 297 insertions, 0 deletions
diff --git a/helpcontent2/source/text/shared/02/12100200.xhp b/helpcontent2/source/text/shared/02/12100200.xhp new file mode 100644 index 000000000..250f0a538 --- /dev/null +++ b/helpcontent2/source/text/shared/02/12100200.xhp @@ -0,0 +1,297 @@ +<?xml version="1.0" encoding="UTF-8"?> +<helpdocument version="1.0"> +<!-- + * This file is part of the LibreOffice project. + * + * This Source Code Form is subject to the terms of the Mozilla Public + * License, v. 2.0. If a copy of the MPL was not distributed with this + * file, You can obtain one at http://mozilla.org/MPL/2.0/. + * + * This file incorporates work covered by the following license notice: + * + * Licensed to the Apache Software Foundation (ASF) under one or more + * contributor license agreements. See the NOTICE file distributed + * with this work for additional information regarding copyright + * ownership. The ASF licenses this file to you under the Apache + * License, Version 2.0 (the "License"); you may not use this file + * except in compliance with the License. You may obtain a copy of + * the License at http://www.apache.org/licenses/LICENSE-2.0 . + --> + +<meta> + <topic id="textshared0212100200xml" indexer="include"> + <title xml-lang="en-US" id="tit">Find Record</title> + <filename>/text/shared/02/12100200.xhp</filename> + </topic> +</meta> +<body> +<bookmark xml-lang="en-US" branch="index" id="bm_id3146936"> +<bookmark_value>tables in databases; searching</bookmark_value> +<bookmark_value>forms; browsing</bookmark_value> +<bookmark_value>records; searching in databases</bookmark_value> +<bookmark_value>searching; databases</bookmark_value> +<bookmark_value>databases; searching records</bookmark_value> +</bookmark><comment>mw changed" database tables;" to "tables in databases;"</comment> +<bookmark xml-lang="en-US" branch="hid/.uno:RecSearch" id="bm_id9750501" localize="false"/> +<bookmark xml-lang="en-US" branch="hid/cui/ui/fmsearchdialog/RecordSearchDialog" id="bm_id3154812" localize="false"/> +<section id="findrecord"> +<h1 id="hd_id3146936"><variable id="datensatzsuche"><link href="text/shared/02/12100200.xhp" name="Find Record">Find Record</link></variable></h1> +<paragraph xml-lang="en-US" id="par_id3147588" role="paragraph"><variable id="suchentext"><ahelp hid=".uno:RecSearch" visibility="hidden">Searches database tables and forms.</ahelp> In forms or database tables, you can search through data fields, list boxes, and check boxes for specific values.</variable></paragraph> +</section> +<section id="howtoget"> + <embed href="text/shared/00/00000450.xhp#find_record"/> +</section> +<paragraph xml-lang="en-US" id="par_id3149355" role="paragraph">When searching a table, the data fields of the current table are searched. When searching in a form, the data fields of the table linked with the form are searched.</paragraph> +<tip id="par_id3153394">The search described here is carried out by <item type="productname">%PRODUCTNAME</item>. If you want to use the SQL server to search in a database, then you should use the <link href="text/shared/02/12110000.xhp" name="Form-based Filters"><emph>Form-based Filters</emph></link> icon on the <link href="text/shared/main0213.xhp" name="Form Bar"><emph>Form</emph> bar</link>.</tip> +<paragraph xml-lang="en-US" id="par_id3149095" role="paragraph">The search function is also available for table controls. When calling the search function from a table control, you can search each column of the table control corresponding to the database columns of the linked database table.</paragraph> +<h2 id="hd_id3143267">Search for</h2> +<paragraph xml-lang="en-US" id="par_id3153527" role="paragraph">Specifies the type of search.</paragraph> +<bookmark xml-lang="en-US" branch="hid/cui/ui/fmsearchdialog/cmbSearchText" id="bm_id3154317" localize="false"/> +<bookmark xml-lang="en-US" branch="hid/cui/ui/fmsearchdialog/rbSearchForText" id="bm_id3147577" localize="false"/> +<h2 id="hd_id3153683">Text:</h2> +<paragraph xml-lang="en-US" id="par_id3154823" role="paragraph"><ahelp hid="cui/ui/fmsearchdialog/rbSearchForText">Enter the search term in the box or select it from the list.</ahelp> The text under the cursor is already copied into the <emph>Text</emph> combo box. Note that while running a search in a form, tabs and line breaks cannot be processed.</paragraph> +<paragraph xml-lang="en-US" id="par_id3148539" role="paragraph">Your search terms will be saved as long as the table or the form document is open. If you are running more than one search and you would like to repeat the search term, you can select a previously used search term from the combo box.</paragraph> +<bookmark xml-lang="en-US" branch="hid/cui/ui/fmsearchdialog/rbSearchForNull" id="bm_id3145316" localize="false"/> +<h2 id="hd_id3153662">Field content is NULL</h2> +<paragraph xml-lang="en-US" id="par_id3153543" role="paragraph"><ahelp hid="cui/ui/fmsearchdialog/rbSearchForNull">Specifies that fields will be found that contain no data.</ahelp></paragraph> +<bookmark xml-lang="en-US" branch="hid/cui/ui/fmsearchdialog/rbSearchForNotNull" id="bm_id3155388" localize="false"/> +<h2 id="hd_id3153717">Field content is not NULL</h2> +<paragraph xml-lang="en-US" id="par_id3143270" role="paragraph"><ahelp hid="cui/ui/fmsearchdialog/rbSearchForNotNull">Specifies that fields will be found that contain data.</ahelp></paragraph> +<h2 id="hd_id3156153">Where to search</h2> +<paragraph xml-lang="en-US" id="par_id3149164" role="paragraph">Specifies the fields for the search.</paragraph> +<bookmark xml-lang="en-US" branch="hid/cui/ui/fmsearchdialog/lbForm" id="bm_id3150670" localize="false"/> +<h2 id="hd_id3154564">Form</h2> +<paragraph xml-lang="en-US" id="par_id3159176" role="paragraph"><ahelp hid="cui/ui/fmsearchdialog/lbForm">Specifies the logical form in which you want the search to take place.</ahelp></paragraph> +<note id="par_id3155434">The<emph> Form </emph>combo box is only visible if the current document is a form document with more than one logical form. It does not appear during a search in tables or queries.</note> +<paragraph xml-lang="en-US" id="par_id3151384" role="paragraph">Form documents may contain multiple logical forms. These are individual form components, which are each linked to a table.</paragraph> +<paragraph xml-lang="en-US" id="par_id3145086" role="paragraph">The <emph>Form</emph> combo box contains the names of all logical forms for which controls exist.</paragraph> +<bookmark xml-lang="en-US" branch="hid/cui/ui/fmsearchdialog/rbAllFields" id="bm_id3149047" localize="false"/> +<h2 id="hd_id3159414">All Fields</h2> +<paragraph xml-lang="en-US" id="par_id3153896" role="paragraph"><ahelp hid="cui/ui/fmsearchdialog/rbAllFields">Searches through all fields.</ahelp> If you are running a search in a table, all fields in the table will be searched. If you are running a search in a form, all fields of the logical form (entered under <emph>Form</emph>) will be searched. If you are running a search in a table control field, all columns that are linked to a valid database table field will be searched.</paragraph> +<paragraph xml-lang="en-US" id="par_id3151054" role="paragraph">Note that the fields of the current logical form do not have to be identical to the fields of the form document. If the form document contains fields that point to multiple data sources (that is, multiple logical forms), the <emph>All Fields</emph> option will only search for the fields linked to data sources in the form document.</paragraph> +<bookmark xml-lang="en-US" branch="hid/cui/ui/fmsearchdialog/lbField" id="bm_id3153524" localize="false"/> +<bookmark xml-lang="en-US" branch="hid/cui/ui/fmsearchdialog/rbSingleField" id="bm_id3150400" localize="false"/> +<h2 id="hd_id3150865">Single field</h2> +<paragraph xml-lang="en-US" id="par_id3153360" role="paragraph"><ahelp hid="cui/ui/fmsearchdialog/rbSingleField">Searches through a specified data field.</ahelp></paragraph> +<h2 id="hd_id3154365">Settings</h2> +<paragraph xml-lang="en-US" id="par_id3158408" role="paragraph">Defines settings to control the search.</paragraph> +<bookmark xml-lang="en-US" branch="hid/cui/ui/fmsearchdialog/lbPosition" id="bm_id3143233" localize="false"/> +<h2 id="hd_id3149809">Position</h2> +<paragraph xml-lang="en-US" id="par_id3148673" role="paragraph"><ahelp hid="cui/ui/fmsearchdialog/lbPosition">Specifies the relationship of the search term and the field contents.</ahelp> The following options are available:</paragraph> +<table id="tbl_id3155994"> + <tablerow> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3156280" role="tablecontent">anywhere in the field</paragraph> + </tablecell> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3145744" role="tablecontent">Returns all fields containing the search pattern anywhere in the field.</paragraph> + </tablecell> + </tablerow> + <tablerow> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3148451" role="tablecontent">beginning of field</paragraph> + </tablecell> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3155429" role="tablecontent">Returns all fields containing the search pattern at the beginning of the field.</paragraph> + </tablecell> + </tablerow> + <tablerow> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3155131" role="tablecontent">end of field</paragraph> + </tablecell> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3153726" role="tablecontent">Returns all fields containing the search pattern at the end of the field.</paragraph> + </tablecell> + </tablerow> + <tablerow> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3147317" role="tablecontent">entire field</paragraph> + </tablecell> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3154127" role="tablecontent">Returns all fields containing the search pattern as an exact match to the contents of the field.</paragraph> + </tablecell> + </tablerow> +</table> +<note id="par_id3152886">If the <emph>Wildcard expression</emph> check box is marked, this function is not available.</note> +<bookmark xml-lang="en-US" branch="hid/cui/ui/fmsearchdialog/cbUseFormat" id="bm_id3154147" localize="false"/> +<h2 id="hd_id3149664">Apply field format</h2> +<paragraph xml-lang="en-US" id="par_id3146975" role="paragraph"><ahelp hid="cui/ui/fmsearchdialog/cbUseFormat">Specifies that all field formats are considered when searching in the current document.</ahelp> Field formats are all visible formats that are created using the following possibilities:</paragraph> +<list type="ordered"> + <listitem> + <paragraph xml-lang="en-US" id="par_id3150103" role="listitem">in table design mode for field properties,</paragraph> + </listitem> + <listitem> + <paragraph xml-lang="en-US" id="par_id3150488" role="listitem">in data source view on column formatting,</paragraph> + </listitem> + <listitem> + <paragraph xml-lang="en-US" id="par_id3152941" role="listitem">in forms on control properties.</paragraph> + </listitem> +</list> +<paragraph xml-lang="en-US" id="par_id3156736" role="paragraph">If the <emph>Apply field format</emph> box is marked, the data source view of the table or form is searched using the formatting set there. If the box is not marked, the database is searched using the formatting saved in the database.</paragraph> +<paragraph xml-lang="en-US" id="par_id3151280" role="paragraph">Example:</paragraph> +<paragraph xml-lang="en-US" id="par_id3149959" role="paragraph">You have a date field, which is saved in "<emph>DD.MM.YY</emph>" format in the database (for example, <emph>17.02.65</emph>). The format of the entry is changed in the data source view to "<emph>DD MMM YYYY</emph>" (<emph>17 Feb 1965</emph>). Following this example, a record containing February 17 is only found when the <emph>Apply field format</emph> option is on:</paragraph> +<table id="tbl_id3151076"> + <tablerow> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3150593" role="tablehead">Apply field format</paragraph> + </tablecell> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3145253" role="tablehead">Search pattern</paragraph> + </tablecell> + </tablerow> + <tablerow> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3083279" role="tablecontent">on</paragraph> + </tablecell> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3155850" role="tablecontent">"Feb" is returned, but not "2".</paragraph> + </tablecell> + </tablerow> + <tablerow> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3148590" role="tablecontent">off</paragraph> + </tablecell> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3153418" role="tablecontent">"2" is returned, but not "Feb".</paragraph> + </tablecell> + </tablerow> +</table> +<paragraph xml-lang="en-US" id="par_id3151321" role="paragraph">It is recommended that you always search using field formatting.</paragraph> +<paragraph xml-lang="en-US" id="par_id3149401" role="paragraph">The following examples show possible issues when searching without field formatting. These issues depend on the database used and only occur for certain internal default formatting:</paragraph> +<table id="tbl_id3156320"> + <tablerow> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3152971" role="tablehead">Search results</paragraph> + </tablecell> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3154273" role="tablehead">Cause</paragraph> + </tablecell> + </tablerow> + <tablerow> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3153836" role="tablecontent">"5" returns "14:00:00" as a time.</paragraph> + </tablecell> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3156332" role="tablecontent">Time fields are not defined for <emph>dBASE</emph> databases and must be simulated. To internally display the time "<emph>14:00:00</emph>", a "<emph>5</emph>" is necessary.</paragraph> + </tablecell> + </tablerow> + <tablerow> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3157965" role="tablecontent">"00:00:00" returns all records of a standard date field.</paragraph> + </tablecell> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3146081" role="tablecontent">The database stores a date value internally using a combined date/time field.</paragraph> + </tablecell> + </tablerow> + <tablerow> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3155764" role="tablecontent">"45.79" does not return "45.79" although the <emph>entire field</emph> option is selected under <emph>Position</emph>.</paragraph> + </tablecell> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3155518" role="tablecontent">The view shown does not match what is stored internally. For example, if value "<emph>45.789</emph>" is stored in the database as a field of type "<emph>Number/Double</emph>" and the shown formatting is set to display only two decimals, "<emph>45.79</emph>" is only returned in searches with field formatting.</paragraph> + </tablecell> + </tablerow> +</table> +<paragraph xml-lang="en-US" id="par_id3148481" role="paragraph">In this case, standard formatting is formatting that refers to the internally stored data. It is not always visible to the user, especially if it is used for simulating data types (for example, time fields in dBASE databases). This depends on the database used and the individual data type. Searching with field formatting is appropriate if you only want to find what is actually shown. This includes fields of type Date, Time, Date/Time and Number/Double.</paragraph> +<paragraph xml-lang="en-US" id="par_id3154507" role="paragraph">However, searching without <emph>Apply field format</emph> is appropriate for larger databases with no formatting issues, because it is faster.</paragraph> +<paragraph xml-lang="en-US" id="par_id3153355" role="paragraph">If you are searching the values of check boxes, and <emph>Apply field format</emph> is on, then you will receive a "1" for marked check boxes, a "0" for unmarked check boxes, and an empty string for undefined (tristate) check boxes. If the search has been carried out with <emph>Apply field format</emph> set to off, you will see the language-dependent default values "TRUE" or "FALSE".</paragraph> +<paragraph xml-lang="en-US" id="par_id3150995" role="paragraph">If you use <emph>Apply field format</emph> when searching in list boxes, you find the text displayed in list boxes. If you do not use <emph>Apply field format,</emph> you will find the contents corresponding to the standard field format.</paragraph> +<bookmark xml-lang="en-US" branch="hid/cui/ui/fmsearchdialog/cbCase" id="bm_id3156717" localize="false"/> +<h2 id="hd_id3150387">Match case</h2> +<paragraph xml-lang="en-US" id="par_id3159267" role="paragraph"><ahelp hid="cui/ui/fmsearchdialog/cbCase">Specifies that upper and lower case are taken into consideration during the search.</ahelp></paragraph> +<bookmark xml-lang="en-US" branch="hid/cui/ui/fmsearchdialog/cbBackwards" id="bm_id3151101" localize="false"/> +<h2 id="hd_id3145297">Search backwards</h2> +<paragraph xml-lang="en-US" id="par_id3151249" role="paragraph"><ahelp hid="cui/ui/fmsearchdialog/cbBackwards">Specifies that the search process will run in reverse direction, from the last to the first record.</ahelp></paragraph> +<bookmark xml-lang="en-US" branch="hid/cui/ui/fmsearchdialog/cbStartOver" id="bm_id3166447" localize="false"/> +<h2 id="hd_id3152484">From top / From bottom</h2> +<paragraph xml-lang="en-US" id="par_id3156316" role="paragraph"><ahelp hid="cui/ui/fmsearchdialog/cbStartOver">Restarts the search. A forward search restarts with the first record. A backwards search restarts with the last record.</ahelp></paragraph> +<bookmark xml-lang="en-US" branch="hid/cui/ui/fmsearchdialog/cbWildCard" id="bm_id3156713" localize="false"/> +<h2 id="hd_id3163724">Wildcard expression</h2> +<paragraph xml-lang="en-US" id="par_id3149255" role="paragraph"><ahelp hid="cui/ui/fmsearchdialog/cbWildCard" visibility="hidden">Allows a search with a <emph>*</emph> or <emph>?</emph> wildcard.</ahelp> You can use the following wildcards:</paragraph> +<table id="tbl_id3151187"> + <tablerow> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3146317" role="tablehead">Wildcards</paragraph> + </tablecell> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3150298" role="tablehead">Meaning</paragraph> + </tablecell> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3153919" role="tablehead">Example</paragraph> + </tablecell> + </tablerow> + <tablerow> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3158411" role="tablecontent">?</paragraph> + </tablecell> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3148874" role="tablecontent">for exactly one arbitrary character</paragraph> + </tablecell> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3150365" role="tablecontent">"?loppy" returns "Floppy"</paragraph> + <paragraph xml-lang="en-US" id="par_id3166426" role="tablecontent">"M?ller" returns, for example, Miller and Moller</paragraph> + </tablecell> + </tablerow> + <tablerow> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3148803" role="tablecontent">*</paragraph> + </tablecell> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3156138" role="tablecontent">for 0 or more arbitrary characters</paragraph> + </tablecell> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3146135" role="tablecontent">"*-*" returns "ZIP-Drive" and "CD-ROM"</paragraph> + <paragraph xml-lang="en-US" id="par_id3155582" role="tablecontent">"M*er" returns all entries starting with an "M" and ending in "er" (for example, Miller, Moller, Mather)</paragraph> + </tablecell> + </tablerow> +</table> +<paragraph xml-lang="en-US" id="par_id3145762" role="paragraph">If you want to search for the actual characters <emph>?</emph> or <emph>*</emph>, precede them with a backslash: "<emph>\?</emph>" or "<emph>\*</emph>". However, this is only necessary when <emph>Wildcard expression</emph> is enabled. When the option is not enabled, the wildcard characters are processed like normal characters.</paragraph> +<bookmark xml-lang="en-US" branch="hid/cui/ui/fmsearchdialog/cbRegular" id="bm_id3150663" localize="false"/> +<h2 id="hd_id3147130">Regular expression</h2> +<paragraph xml-lang="en-US" id="par_id3150982" role="paragraph"><ahelp hid="cui/ui/fmsearchdialog/cbRegular">Searches with regular expressions.</ahelp> The same regular expressions that are supported here are also supported in the <item type="productname">%PRODUCTNAME</item> <link href="text/shared/01/02100000.xhp" name="Find & Replace dialog"><emph>Find & Replace</emph> dialog</link>.</paragraph> +<paragraph xml-lang="en-US" id="par_id3154718" role="paragraph">Searching with regular expressions offers more options than searching with wildcard expressions. If you search with regular expressions, the following characters correspond to those used in searches with wildcards:</paragraph> +<table id="tbl_id3148682"> + <tablerow> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3153705" role="tablehead">Search with wildcard expression</paragraph> + </tablecell> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3149209" role="tablehead">Search with regular expressions</paragraph> + </tablecell> + </tablerow> + <tablerow> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3151045" role="tablecontent">?</paragraph> + </tablecell> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3150384" role="tablecontent">.</paragraph> + </tablecell> + </tablerow> + <tablerow> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3153793" role="tablecontent">*</paragraph> + </tablecell> + <tablecell> + <paragraph xml-lang="en-US" id="par_id3150428" role="tablecontent">.*</paragraph> + </tablecell> + </tablerow> +</table> + <embed href="text/shared/01/02100100.xhp#similarity_search"/> + <embed href="text/shared/01/02100000.xhp#halbnormaltitel"/> + <embed href="text/shared/01/02100000.xhp#halbnormaltext"/> + <embed href="text/shared/01/02100000.xhp#aehnlichtitel"/> + <embed href="text/shared/01/02100000.xhp#aehnlichtext"/> + <embed href="text/shared/01/02100000.xhp#aehnlichbutton"/> + <embed href="text/shared/optionen/01150200.xhp#asia"/> +<h2 id="hd_id3150861">State</h2> +<paragraph xml-lang="en-US" id="par_id3154477" role="paragraph">The <emph>State</emph> line shows the records returned by the search. If the search reaches the end (or the beginning) of a table, the search is automatically continued at the other end.</paragraph> +<paragraph xml-lang="en-US" id="par_id3163720" role="paragraph">In very large databases, finding the record in reverse search order can take some time. In this case, the <emph>status bar</emph> informs you that the records are still being counted.</paragraph> +<bookmark xml-lang="en-US" branch="hid/cui/ui/fmsearchdialog/pbSearchAgain" id="bm_id3149494" localize="false"/> +<h2 id="hd_id3147389">Search/Cancel</h2> +<paragraph xml-lang="en-US" id="par_id3154368" role="paragraph"><ahelp hid="cui/ui/fmsearchdialog/pbSearchAgain" visibility="hidden">Starts or cancels the search.</ahelp> If the search is successfully completed, the corresponding field in the table is highlighted. You can continue the search by clicking the <emph>Search</emph> button again. You can cancel a search process by clicking the <emph>Cancel</emph> button.</paragraph> +<bookmark xml-lang="en-US" branch="hid/cui/ui/fmsearchdialog/close" id="bm_id3152453" localize="false"/> +<h2 id="hd_id3145080">Close</h2> +<paragraph xml-lang="en-US" id="par_id3156166" role="paragraph"><ahelp hid="cui/ui/fmsearchdialog/close">Closes the dialog. The settings of the last search will be saved until you quit <item type="productname">%PRODUCTNAME</item>.</ahelp></paragraph> +<paragraph xml-lang="en-US" id="par_id3151183" role="paragraph">If several tables or forms are open, you can set different search options for each document. When you close the documents only the search options of the document last closed are saved.</paragraph> +</body> +</helpdocument> |