Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index

Alternatively, to save copying data into a common .ods file, you can keep one .odb file (e.g. mergesource.odb) but change which .ods file it points to. Open mergesource.odb, then Edit > Database > Properties, and change the path to spreadsheet document.

Saves a bit of copying data around, but I can see that might not be so easy as an instruction if there are non-technical users of your merge document. Whatever works for you and your users is best ;o)


Steve Edmonds wrote:
And thanks to the discussion I think I have a much better understanding
and can iron out the problems our users are having with the merge.
We keep getting new lists to merge, all the same format. The secret to
simplification is, once set up, to have an ods named mergesource.ods or
something and then copy the new data in each time or save the new data
as mergesource.ods. Then a new .odb file is not created each merge, and
it is not necessary to exchange the database or re-link the fields.

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.