Ask Your Question

Mail Merge does not find the source data when I go back into the document.

asked 2019-03-21 15:14:23 +0200

VKW gravatar image

updated 2019-03-21 15:35:21 +0200

I have created a Mal Merge Document with a data source of an *.ods spreadsheet. When I go back into the document after saving it I am unable to scroll through my mail merge documents to see each individual and then when I go to the Data Sources I get an error that says "the connection to the data sources XXXX cannot be established". Then I tried to go back through the Mail Wizard to link to the Data Source but it will then create a new data source with the same name as above but with a 1 behind it. I now have 3 data sources for this mail merge none of which work.

I have tried a variety of solutions that I have read in your documentation but the error still returns. I would like to have my mail merge document link to a spreadsheet and then save it and have it be there when I open it again. Thanks

edit retag flag offensive close merge delete

2 Answers

Sort by » oldest newest most voted

answered 2019-05-03 15:39:14 +0200

brucef gravatar image

I confirm the frustration expressed by Dioxaz with mail merge documents not able to retain the Database link. In our case, I am always looking to the same query each month, with the resulting data filtered differently by current date range. But now, with LibreOffice Mac v the Exchange Database must be re-located each time the .odt is opened. As noted OO Writer worked fine. However LibreOffice provides better support for .xlsx and .docx conversions, so made the switch. Lets hope someone takes this defect seriously.

edit flag offensive delete link more

answered 2019-04-12 14:42:01 +0200

Dioxaz gravatar image

updated 2019-04-12 14:52:15 +0200

To OP: when re-importing your database with another method (the mailing assistant for instance), you must reinsert all your fields one by one from the newly imported database. As your ODT will still look for the older database name when referencing its fields if you don't do so (hoover your mouse over your fields and the complete field path will pop up). As a workaround, you can also use the database manager (Tools > Options > Libre Office Base) in order to rename your newly imported database to the same name as the older one (don't rename the ODB file, you have to open the database manager and change the display name only).

I'm adding in my feedback as we currently experience the same issue at the organization I work for. The typical scenario is any machine running Libre Office 6 (Windows or Linux, it doesn't matter) will lose its connection to a database imported from an ODS file at some point:

  • either during adding the fields into an ODT document (you can see the database vanish live right in front of your powerless eyes)
  • or after inserting a custom field (unrelated to the database), right after closing the custom field dialog
  • or while attempting to delete some text
  • or after restarting Writer or any Libre Office application

The database is simply not there anymore, whether from the "data sources" window (Ctrl+Shift+F4) or the database manager (Tools > Options > Libre Office Base), without any manual intervention. I noticed this behaviour started to appear from version alpha onwards and still persists with latest evolution build (6.2.2 as I'm writing this), according to my tests.

On the other hand, Libre Office 5.4.7 works perfectly and doesn't disconnect an imported-from-ODS database (using the "Exchange database" function) at random.

One workaround I've found is going into the database manager and renaming the freshly imported database to something other than its original name. It did work multiple times in my own case but I had reports that even the renaming trick failed at times.

I'm quite puzzled to see nobody else using Libre Office 6 reported that problem before us. This is extremely penalizing and made us ditch Libre Office completely (at least version 6, but at the IT desk I work for, we decided to install Open Office instead, to prevent any further problem we might have missed).

Edit: I even filed a bug describing the issue:

edit flag offensive delete link more
Login/Signup to Answer

Question Tools

1 follower


Asked: 2019-03-21 15:14:23 +0200

Seen: 98 times

Last updated: May 03