Relations

From 4dd442010398f4d280ebaa1de3d066185da00daf Mon Sep 17 00:00:00 2001 From: Ivo Hinkelmann Date: Fri, 12 Jun 2009 18:19:30 +0000 Subject: CWS-TOOLING: integrate CWS hcshared21 2009-05-13 09:49:59 +0200 ufi r271841 : CWS-TOOLING: rebase CWS hcshared21 to trunk@271427 (milestone: DEV300:m47) 2009-04-16 11:01:43 +0200 ufi r270873 : again 2009-03-17 10:19:50 +0100 ufi r269575 : before builds 2009-02-13 16:03:59 +0100 ufi r267726 : CWS-TOOLING: rebase CWS hcshared21 to trunk@267171 (milestone: DEV300:m41) 2009-02-10 10:30:11 +0100 ufi r267539 : vor neuem rebase Versuch 2009-02-03 15:55:58 +0100 ufi r267334 : before rebase 2009-01-06 10:38:41 +0100 ufi r265901 : i97718 --- .../text/shared/explorer/database/02010101.xhp | 92 ++++++++++++---------- .../text/shared/explorer/database/makefile.mk | 5 +- .../shared/explorer/database/migrate_macros.xhp | 71 +++++++++++++++++ 3 files changed, 125 insertions(+), 43 deletions(-) create mode 100755 helpcontent2/source/text/shared/explorer/database/migrate_macros.xhp (limited to 'helpcontent2/source/text/shared/explorer/database') diff --git a/helpcontent2/source/text/shared/explorer/database/02010101.xhp b/helpcontent2/source/text/shared/explorer/database/02010101.xhp index 35352548a5..bc2a0c1f3c 100755 --- a/helpcontent2/source/text/shared/explorer/database/02010101.xhp +++ b/helpcontent2/source/text/shared/explorer/database/02010101.xhp @@ -1,9 +1,8 @@ - - - + + - - - + + - -Relations -/text/shared/explorer/database/02010101.xhp - - - + + Join Properties + /text/shared/explorer/database/02010101.xhp + + + links;relational databases (Base) -inner joins (Base) -joins in databases (Base) -left joins (Base) -right joins (Base) -full joins (Base) -mw deleted "join properties" and changed "link properties..." to "links;"Relations -If you double-click a connection between two linked fields in the query design, or if you choose Insert - New Relation, the Relations dialog appears. These properties will be used in all queries created in the future. -

+ inner joins (Base) + joins in databases (Base) + left joins (Base) + right joins (Base) + full joins (Base) +mw deleted "join properties" and changed "link properties..." to "links;" +Join Properties + If you double-click a connection between two linked fields in the query design, or if you choose Insert - New Relation, the Join Properties dialog appears. These properties will be used in all queries created in the future. +

-Tables involved -Specifies two different tables that you want to join.UFI: removed a help idFields involved -Specifies two data fields that will be joined by a relation. -Options -Type -Specifies the link type of the selected link. Some databases support only a subset of the possible types. -Inner Join -With the internal join, the results table contains only the records for which the content of the linked fields is the same. In $[officename] SQL this type of link is created by a corresponding WHERE clause. -Left Join -With the left join, the results table contains all fields of the left table and only those fields of the right table for which the content of the linked fields is the same. In $[officename] SQL this type of link corresponds to the LEFT OUTER JOIN command. -Right Join -With the right join, the results table contains all fields of the right table and only those fields of the left table for which the content of the linked fields is the same. In $[officename] SQL this type of link corresponds to the RIGHT OUTER JOIN command. -Full Join -For a full join, the results table contains all fields of the left and right tables. In the SQL of $[officename] this type of link corresponds to the FULL OUTER JOIN command. - - + +Tables involved + Specifies two different tables that you want to join. + Fields involved + Specifies two data fields that will be joined by a relation. + Options + +Type + Specifies the link type of the selected link. Some databases support only a subset of the possible types. + Inner Join + With the internal join, the results table contains only the records for which the content of the linked fields is the same. In $[officename] SQL this type of link is created by a corresponding WHERE clause. + Left Join + With the left join, the results table contains all fields of the left table and only those fields of the right table for which the content of the linked fields is the same. In $[officename] SQL this type of link corresponds to the LEFT OUTER JOIN command. + Right Join + With the right join, the results table contains all fields of the right table and only those fields of the left table for which the content of the linked fields is the same. In $[officename] SQL this type of link corresponds to the RIGHT OUTER JOIN command. + Full Join + For a full join, the results table contains all fields of the left and right tables. In the SQL of $[officename] this type of link corresponds to the FULL OUTER JOIN command. + +Natural + Inserts the keyword NATURAL into the SQL statement that defines the relation. The relation joins all columns that have the same column name in both tables. The resulting joined table contains only one column for each pair of equally named columns. + + \ No newline at end of file diff --git a/helpcontent2/source/text/shared/explorer/database/makefile.mk b/helpcontent2/source/text/shared/explorer/database/makefile.mk index 3492dd4323..f2d85e7594 100644 --- a/helpcontent2/source/text/shared/explorer/database/makefile.mk +++ b/helpcontent2/source/text/shared/explorer/database/makefile.mk @@ -6,9 +6,9 @@ # # OpenOffice.org - a multi-platform office productivity suite # -# $RCSfile: makefile.mk,v $ +# $RCSfile: makefile.template,v $ # -# $Revision: 1.13.4.4 $ +# $Revision: 1.5 $ # # This file is part of OpenOffice.org. # @@ -112,6 +112,7 @@ XHPFILES = \ menuinsert.xhp \ menutools.xhp \ menuview.xhp \ + migrate_macros.xhp \ password.xhp \ querywizard00.xhp \ querywizard01.xhp \ diff --git a/helpcontent2/source/text/shared/explorer/database/migrate_macros.xhp b/helpcontent2/source/text/shared/explorer/database/migrate_macros.xhp new file mode 100755 index 0000000000..b90fc54ea4 --- /dev/null +++ b/helpcontent2/source/text/shared/explorer/database/migrate_macros.xhp @@ -0,0 +1,71 @@ + + + + + + + + + Migrate Macros + /text/shared/explorer/database/migrate_macros.xhp + + + +

+wizards;macros (Base) + Macro Wizard (Base) + macros;attaching new (Base) + migrating macros (Base) +MW added 2 index entries +Migrate Macros + +The Database Document Macro Migration Wizard moves existing macros from sub-documents of an old Base file into the new Base file's macro storage area. +

+ +Choose a location and file name to save the new database file. By default, the new file gets the same name as the old file, while the old file gets renamed with the string "backup" in the name. + +The list shows all changes that were applied to the database file. + Previously, macros have been allowed to reside only in the text sub-documents of forms and reports. Starting with OpenOffice.org 3.1 or StarOffice 9.1, macros can also be stored in the Base file itself. This means that macros in Base files can be called now from any of its sub-components: forms, reports, table design, query design, relation design, table data view. + However, it is technically not possible to store macros both in a Base file and in its sub-documents at the same time. So, if you want to attach some new macros to the Base file, while retaining any existing old macros that were stored in the sub-documents, you must move the existing old macros up to the Base file's macro storage area. + The Database Document Macro Migration Wizard can move the macros up into the Base file's storage area. You can then examine the macros and edit them as needed. + For example, it is possible that macros from the sub-documents had the same module names and macro names. After you moved the macros into one common macro storage area, you must edit the macros to make the names unique. The wizard cannot do this. + The wizard can backup the Base file to another folder of your choice. The wizard changes the original Base file. The backup remains unchanged. +

+ An in depth explanation by the developers (Wiki). +

+ + \ No newline at end of file -- cgit