When creating a form and a subform you have to define the relations between form and subform. There is a possibility to link from one form to another. When you youse the litte wizard for it and press the button, that it should suggest the right values, it only works with the fist field of the subform with the right fieldtype. Relationships, which are created in the database, are not consulted. When creating whole forms with the wizard it works right. Wizard reads the relationships right from the database.
Hi Robert, 1) Please add the LO-version in which the bug occurs. 2) I don´t unterstand the procedure. Can you create a screenshot
Created attachment 66239 [details] Database with 3 tables, one table with two foreign-keys. Try to change the relation between form and subform in the form "Leser_subformtest" with the suggestion of the dialog. It suggests wrong values. The form itsel is created with the form-wizard. This wizard suggests the rigtht values.
Created attachment 66240 [details] Detailed description how to choose the dialog with wring suggestion In this description is declared how to find the wrong dialog. The suggestion of this dialog works in the right way, when I copied two tables, switched the position of the foreign-keys in one of the tables and declared the relationship new. Without declaring the relationship the dialog didn't suggest anything - the button is disabled. But the function behind the button doesn't read the relationship at all.
@ Robert, thx for attach 66240. But I can´t reproduce some steps. Please list more details in your document. You wrote: When you start the form-wizard with the table „Leser“ you could choose the table „Ausleihe“ as subform. The relation between both tables is choosen automatically. Asks from me: 1) What means "start the form-wizard with the table „Leser“". Please describe exactly the procedure. E.g. do you choose table "Table: Leser"? And which "available fields" have you chosen? 2) I created a form with the "Wizard to Create Form". I have chosen as subform "Table: Ausleihe". Also here: Please describe exactly the procedure. E.g. have you chosen the automatic selection or the "manual selection"? And which "available fields" have you chosen? 3) The next steps? You wrote: Picture 2: ... When you haven't used the form-wizard you could chosse the entries for Link fields in a dialog. See the cursor over the three point, which start this dialog. Asks from me: 1) Please describe exactly the procedure ("you could chosse the entries for Link fields in a dialog") 2) What do you mean with "See the cursor over the three point"? You wrote: Picture 3: This dialog has a button „Suggest“. ... 1) This dialog has a button „Suggest“. What dialog? How do open this dialog? 2) I will test the rest if I know the procedure.
Created attachment 66367 [details] Description how to get the right connection with form-wizard and the wrong with suggestion in the dialog The way to get the right connection between two forms: Use the form-wizard, add the subform, base on an existing relation. This relation is the relation choosen in Tools → Relationships. After creating such a form (with subform) open the form for editing. Open the form-navigator and there, with a click of the right button of the mouse, open the properties of the subform. You could see the linked fields (as linked by the form-wizards). There are buttons between the fields, for example Link master fields... "ID" [...]. A click on one of this buttons opens a dialog. Choose in this dialog "Suggest". The wrong connection is suggested.
@ Robert Now I understand what you mean. I can reconstruct your observation. But I want to discuss your conclusion. You believe there is a bug. IMHO it is possible that there is a normal behavior. Click on "Sugggest" shows all (!) fields of the table "Ausleihe" and this is IMHO correct. I understand you so that your argues "The table "Medien" doesn't exist in this form" is the cause of the malfunction. I can´t comprehend this argument. "Medien_ID" isn´t a field of the table "Medien" but of the table "Ausleihe. We need another base-specialist to confirm your suspicion. Perhaps someone reading this bugreport can help. I set Lionl to CC.
@Jochen: Difference between the suggestion of the form-wizard and the dialog, where you can link the forms, is: The form-wizard works right with the defined relationships of the database. The dialog works wrong (or didn't have a look) at the relationsships. When I press "Suggest" I expect, that the dialog would have a look at the defined relationship - but I don't know, whre the dialog gets it's information from, not only from the relationship, also from the position of a field in the table and other tables in the database ...
Hi Rainer, please have a look at comment 6 and comment 7. Which procedure do you suggest?
The content of this report seems to be clear: Formwizard reads the relationship of the table from the database. If you will create a form without the wizard and will link a subform to a mainform, you could chose the fields, which should be linked. You could also press the button "Suggest" - but this "Suggestion" doesn't have a look at the relationship of the table like the formwizard. It suggests only the first field, which has the same fieldtype as the chosen fieldtype of the mainform. I will change the status to "New". Base works well without fixing this bug. So I change the importance also to "low" and "minor".
Adding self to CC if not already on
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT: - Update the version field - Reply via email (please reply directly on the bug tracker) - Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-01-17
Bug still exists with LO 5.1.0.2, OpenSUSE 42.1 Leap, 64bit rpm Linux.
Bug appears also in the first available LO-version (LO 3.3.0.4, OpenSUSE 42.1 64bit rpm Linux). So I set this bug as "Inherited From OOo".
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.2.7 or 5.3.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170522
Bug still exists with LO 5.4.0.0.beta1, OpenSUSE 42.1 Leap, 64bit rpm Linux.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Bug still exists with LO 6.0.5.1, OpenSUSE 42.3 Leap, 64bit rpm Linux.
Dear robert, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Buggy behaviour is still the same in LO 6.2.4.2 on OpenSUSE 15 64bit rpm Linux
Dear Robert Großkopf, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Bug is still the same in LO 7.1.4.2 on OpenSUSE 15.2 64bit rpm Linux. Here a very short description: Open the database. Open the form for editing, not for input data. Click on the second tablecontrol (MedienID and others). Right mouseclick and open form properties. See relation between the forms: "ID" to "Leser_ID" as it is described in relationship of the database. Click on the button with the three points on the right. Let suggest which fields should be choosen. It will choose "Medien_ID", which is the wrong field an not connected in the relationship of the database to "Leser".