Bug 62520 - Crash when opening Tools => Relationships with MS SQL Server 2008 over ODBC
Summary: Crash when opening Tools => Relationships with MS SQL Server 2008 over ODBC
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
(earliest affected) release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
Whiteboard: BSA
Depends on:
Reported: 2013-03-19 12:28 UTC by Björn Schließmann
Modified: 2020-04-19 12:44 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Björn Schließmann 2013-03-19 12:28:02 UTC
Problem description: In a freshly created Base file using an ODBC MS SQL Server connection, clicking Tools => Relationships crashed LibreOffice.

Steps to reproduce:

1. Start Base
2. Connect to an existing database, select ODBC, Next
3. Click Browse, select database, Next
4. Leave user name empty (NTLM authentication), Click "Test Connection", "The Connection was established successfully", click ok and Next
5. leave defaults, click "Finish"
6. Click "Save"
7. Click Tools => Relationships ... Crash!

Current behavior: Crash

Expected behavior: Show the Relationships dialogue

Additional comments:
- Happens using versions 4.0.1 and 3.6.5. Creating and editing tables, designing and executing queries, ... everything works. Except Relationships.
- Sometimes, directly after rebooting, opening the relationships window works one or two times. After that, the behaviour is as stated above. It may be subjective, but it seems to work more often if I delete one or both of the XML files und LibreOffice 4.0\share\config\soffice.cfg\modules\dbrelation.

I'll be happy to provide more details as needed.
Operating System: Windows XP
Version: release
Comment 1 Joel Madero 2014-05-28 02:54:02 UTC
Sorry for the horribly long delay on this one. Can you confirm that this is still a problem with a fresh profile and - if so I'm going to get it confirmed so we can figure out what's going on. Again - sorry for the delay
Comment 2 Björn Schließmann 2014-06-02 17:21:37 UTC
Thanks for your reply! I'm going to look into it again soon, this problem is related to a project at work that is on hold for now, but I still need to finish it.

My temporary solution was to use Microsoft's administration tool for configuring relationships.
Comment 3 Buovjaga 2014-10-24 14:46:18 UTC
Can you test on
Comment 4 Alex Thurgood 2015-01-03 17:40:57 UTC
Adding self to CC if not already on
Comment 5 Joel Madero 2015-01-09 17:04:50 UTC
Lionel - this one has been around in UNCONFIRMED land for a long time. Do you have a setup that could test it with 4.3 or newer?
Comment 6 Lionel Elie Mamane 2015-01-09 17:25:28 UTC
(In reply to Joel Madero from comment #5)
> Lionel - this one has been around in UNCONFIRMED land for a long time. Do
> you have a setup that could test it?

Not really. A backtrace from a debug build would be nice, as usual...
Comment 7 Joel Madero 2015-01-09 17:30:44 UTC
Putting this in NEEDINFO.

Björn: We'll need a backtrace of this one. They are relatively straight forward to do. If you can still confirm the problem you can find instructions for a backtrace here: https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg

Once you get a backtrace you can put the bug back into UNCONFIRMED and I'll try to poke a developer to take a look at it. Thanks again for your patience.
Comment 8 QA Administrators 2015-07-18 17:35:31 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

This NEEDINFO message was generated on: 2015-07-18
Comment 9 QA Administrators 2015-09-04 03:00:51 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO
Message generated on: 2015-09-03
Comment 10 b. 2020-04-19 12:44:28 UTC
this bug benefits from the fix of @LEM in #63695, but the '"uno: copy" via the dispatcher does not work when a button has focus' problem (described in #70883) becomes active again ...