summaryrefslogtreecommitdiffstats
path: root/helpcontent2/source/text/shared/explorer/database/migrate_macros.xhp
diff options
context:
space:
mode:
Diffstat (limited to 'helpcontent2/source/text/shared/explorer/database/migrate_macros.xhp')
-rw-r--r--helpcontent2/source/text/shared/explorer/database/migrate_macros.xhp4
1 files changed, 2 insertions, 2 deletions
diff --git a/helpcontent2/source/text/shared/explorer/database/migrate_macros.xhp b/helpcontent2/source/text/shared/explorer/database/migrate_macros.xhp
index 99a8adc119..11b48dd44f 100644
--- a/helpcontent2/source/text/shared/explorer/database/migrate_macros.xhp
+++ b/helpcontent2/source/text/shared/explorer/database/migrate_macros.xhp
@@ -48,9 +48,9 @@
<bookmark xml-lang="en-US" branch="hid/.uno:DBMigrateScripts" id="bm_id0224200911384751" localize="false"/>
<paragraph xml-lang="en-US" id="par_id0112200902353466" role="paragraph" l10n="NEW"><ahelp hid=".">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.</ahelp></paragraph>
</section>
-<bookmark xml-lang="en-US" branch="hid/dbaccess_PushButton_TP_SAVE_DBDOC_AS_PB_BROWSE_SAVE_AS_LOCATION" id="bm_id022420091141368" localize="false"/>
+<bookmark xml-lang="en-US" branch="hid/dbaccess:PushButton:TP_SAVE_DBDOC_AS:PB_BROWSE_SAVE_AS_LOCATION" id="bm_id022420091141368" localize="false"/>
<paragraph xml-lang="en-US" id="par_id0224200911454780" role="paragraph" l10n="NEW"><ahelp hid="." visibility="hidden">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.</ahelp></paragraph>
-<bookmark xml-lang="en-US" branch="hid/dbaccess_MultiLineEdit_TP_SUMMARY_ED_CHANGES" id="bm_id0224200911450172" localize="false"/>
+<bookmark xml-lang="en-US" branch="hid/dbaccess:MultiLineEdit:TP_SUMMARY:ED_CHANGES" id="bm_id0224200911450172" localize="false"/>
<paragraph xml-lang="en-US" id="par_id022420091145472" role="paragraph" l10n="NEW"><ahelp hid="." visibility="hidden">The list shows all changes that were applied to the database file.</ahelp></paragraph>
<paragraph xml-lang="en-US" id="par_id0112200902353542" role="paragraph" l10n="NEW">Previously, macros have been allowed to reside only in the text sub-documents of forms and reports. Now 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.</paragraph>
<paragraph xml-lang="en-US" id="par_id0112200903075865" role="paragraph" l10n="NEW">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. </paragraph>