Date: prev next · Thread: first prev next last
2021 Archives by date, by thread · List index

Hi Moebius,

here the simple solution:

Put away the table "codes".
Edit table "Personnens"
→ add the field "Villes_ID" to "Personnes" (should be INTEGER;
foreignkey from table "Villes")
→ delete the fields "Codepost" and "Ville" from this table. You will get
this information from "Villes".

You will search for "Villes" or "PostCode" later?
Create a table filter for only one row.
Fields are like  the fields in "Villes". The field "ID" could be boolean.

Together with thgis table you could search for every "PostCode" or "Ville".

Here a complicated solution:
Rows of table "codes" will appear many times in "Villes".
Rows of table "Villes" will also appear many times in "codes".
You have to delete the "postalcode" für "Villes".
You have to create a combination of the two elements together in table
Change the fields "Codepost" and "Ville" from this table to INTEGER
fileds. They will contain the foreignkey from the tables "Villes" and

I would prefer the simple method. You have to edit only one table to
cretae the mostly used combinations of "Code" and "Ville". Then you
could choose the values from this table in a listbox to put the
foreignkey to "Personnes".

Lets see whot you need for per private mail. Thins ist is too special
for other people in this mailinglist.



To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
Privacy Policy:


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.