Some Base relationships not saved

I am new to LO environment, and notice that after some relationships between tables are created, additional links are not saved thereafter. There is no error message when this happens, it is just that the link is not displayed the next time the relationship window is opened. I have three 1:n links installed successfully now, but no more can be installed after that. Is this a Base constraint, or more likely a bug?

I installed the latest version of LO [v5.3.5.2 (x64)] and using Base with integrated Access2Base (v1.6) for an application.

Below are two screenshots: one post install of three 1:1 links, and then after save & reopen relationships window.


There is no limit on links. You can see some examples in the docs - Chapter 3 Tables (especially page #7) found here.

Have not experienced that since starting LO with v4.2.x.

Are the links visible when you save the Relationships?

Yes, links seem to be installed correctly, and save operation appears to complete successfully. But reopen window and they are absent. Can reinstall, but they are lost when relationships window closed.

Can you post a sample? Please no personal/confidential information. Have raised your Karma to permit edit of question & append file.

I added a couple screenshots to the original post.

The problem is that your relation is actually never established. Your first screenshot shows this. At either end of the link there is no 1 or n. This is because neither field is unique. Initials in the Employee table can be duplicated as well as in Camping table. It would be better to change the Employee table so the Primary key is only the ID & use that to link to the other tables.

I would imagine SMSGateway or Network is also not set as unique so again no relation established. If looking for many-to-many relations you need to set up intermediary table (found in Chapter 3 of the referred to documentation).

As far as generating some type of error, you can file a Bug report here.

Thank you for the comments! I was able to fix the SMSGateway link by deleting the ID column, and making the Network column the primary key. Now the 1:n relation shows up and is saved as expected. I need to work on the other link, but it is a similar issue I believe.
I consider this question closed.

You don’t always need to change a key. You can always make a field ‘unique’ and use that.

See this post to set unique.

Why not try deleting the three links that work then create the links that did not work when those three links were there. Do these links hold? If they don’t it suggests there is something wrong in these links. If they hold add the original links.

Good suggestion. I deleted all links, and then tried to install one of the problematic 1:1 links. The save operation seemed fine but on reopen, link was gone. So same bad behavior, and no error message. Even if there is something wrong with the link (which is not apparent to me), there should be an indication of this to the user.