<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - EDITING: Query input in foreignkey-field impossible, when two tables in the query." href="https://bugs.documentfoundation.org/show_bug.cgi?id=68153#c19">Comment # 19</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - EDITING: Query input in foreignkey-field impossible, when two tables in the query." href="https://bugs.documentfoundation.org/show_bug.cgi?id=68153">bug 68153</a> from <a class="email" href="mailto:lionel@mamane.lu" title="Lionel Elie Mamane <lionel@mamane.lu>"> Lionel Elie Mamane</a> <pre>(In reply to Howard Johnson from <a href="show_bug.cgi?id=68153#c17">comment #17</a>) >>> What were talking about here is the ability to edit many-to-one relations in >>> queries, and in forms based on those queries. > As I pointed out before, forms/subforms deal with "has" relationships (main > table has children; where FKs are in the children and point to the main > table), not "is" relationships (where FKs are in the parents and points to > enumerations). I fail to see why subforms wouldn't work in both directions. > As I said before: MySQL can do this, and I can prove it because Access, > when connected to MySQL, to the very same database and tables, can do this. In my experience, Access doesn't do it. I attach an Access database. In it, Access refuses to change the value of the foreign key field. Oh, I see now. Access accepts to do it when you change ONLY the FK field AND NO OTHER FIELD on the "many" side in a one-to-many join. It then immediately refreshes all fields that come from the "many" side, to avoid the ambiguity I described. OK, I understand now what you mean. Basically, Access does this through its Jet database engine, not through MySQL. So we are back to "Base is not its own database engine". I understand the cool feature you are used to on the Access side. It might be doable within the Base design. Valid feature request. P.S.: other consequences of "Access has its own database engine" (which is able to "connect" to other engines through ODBC): * you write your queries in the SQL dialect understood by Access (Jet), *not* the one understood by e.g. MySQL (unless you do an "SQL direct" query but then you cannot edit data). * you can do a join between tables that come from *different* DBMS. Whereas Base just sends the SQL whatever DBMS you are using. However, note that in a writer document having forms and subforms (alas not in a Base form document, that's a feature request of mine...) the different (sub)forms can pull data from different DBMS.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>