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
At my job we currently use Lotus Symphony and we use the Open Document
format exclusively. We're currently in the process of migrating to
LibreOffice 4.2. We have a lot of documents we use with the mail merge
feature. All of the data sources are from spreadsheets. In Symphony, the
spreadsheet
On 2014-03-20 07:12, Jeff Prater wrote:
At my job we currently use Lotus Symphony and we use the Open Document
format exclusively. We're currently in the process of migrating to
LibreOffice 4.2. We have a lot of documents we use with the mail merge
feature. All of the data sources are from
Yeah--I guess I could do that. But I already have all these fields created.
I have probably 50+ documents where I would need to make these manual
changes. Plus, the spreadsheets get updated regularly and I don't want to
have to reimport/reattach the spreadsheet all the time. I guess I'll have
to
Hi,
I did my database in OO about 10 years ago, maybe more. I haven't
fiddled with the fields since then, but they were custom fields. I moved
to LO as soon as it was released. I use mail merge extensively, and had
no problems having custom named fields working to pull the data from. So
there
That's the problem. Whenever I attempt to do the mail merge, it doesn't
list any of the custom fields in my document. It only list canned fields.
I don't see how I can match my existing fields within this interface.
[image: Inline image 2][image: Inline image 1]
-
Jeff Prater
On Wed, Mar
Not sure if I've missed the point here -
Create a spreadsheet .ods file with 3 columns each column headed - col1, col2,
col3
Add two rows populating respective columns my first row contained 1, 2, 3 and
the 2nd row a, b ,c so I had a spreadsheet .ods file that looked like this -
col1col2
Yes--that does work. However, I already have a bunch of .odt documents
mapped with the fields from the .ods spreadsheets. I don't want to have to
delete all of the existing fields and reinsert them. I was hoping this
would just work.
Also, is there any way to not have LO cache (if that's the
Okay--I think I found the problem. When I opened one of my .odt documents
and hovered over one of the fields, LO didn't seem to recognize it as a
field. After going back to Insert Fields Other and manually reinserting
the fields, the mail merge works correctly. I was hoping I wouldn't have to
I have not been following the discussion so I can't comment on anything
that's gone before, but one thing I recently learned is that you can
keep the fields window open while inserting all your fields.
There are arrow buttons/icons that In some cases you can simply click
those and it will
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
11 matches
Mail list logo
