0

Look up query

Screenshot 2026-04-01 at 16.22.08

Hi,

I do have a question to find a solution in Ninox.

In one table I have a dataset. Each dataset has a Main ID#. Thats easy and works well.

In a different table I have a date, price and Main ID# from first table, multiply times. In Libre office I inserted a subtable and displayed those info.

If I scroll to the next main ID the subtable scrolls also to the next data set. Info I pull from a query which is linked to the 2 tables.

Is these scenario also in Ninox possible ?

3 replies

null
    • Fred
    • 7 hrs ago
    • Reported - view

    Short answer, Yes. Ninox, like any relational databases, can do anything a spreadsheet can do, but faster.

    How familiar are you with relational databases? 

    What is your workflow for this database?

    Currently, how is data added to each table?

    In the future, how do you want data to be added to the database?

      • horst_droege
      • 6 hrs ago
      • Reported - view

       tnx for the reply.

      I used years back MS access. Was ok to use. 

      Last year I used Libre office for it. Got it working. Both I just use to occupy myself. I still consider myself as newcomer.

      Main table has about 50 entries and per year my come 5 new one and 5 falling out.

      Payment table 2 may has 20 entries for one main record. Table 2 I would import from a csv file. It's easy to do on Excel but I just want to try Ninox. In one way nice to handle. The sample files and tutorials I found not pointing my so much in the right direction.

    • Fred
    • 4 hrs ago
    • Reported - view

    Ok, it seems that the Payment table is a child of the Main table (or whatever the actual name is). Go to Payments then Edit Fields. Now on the right side, select Relationship fields then select Main and drag it into the Fields section in the middle. Now click on the Main relationship field and set Composition to Yes. This is where we tell that Payment is a child to Main.

    Click OK to save the changes. You have created a 1:M or one to many relationship between Main and Payments. One Main record can have many Payment records linked. With Composition set to Yes, it means that when a record is deleted in Main all child records in Payment are also deleted.

    Now you will see the new field in Payments called Main. If you go back to Main, you will now see a new table view called Payments.

    The next step is to link the Payment records to the Main record. You can manually do it from either end of the relationship. In Payments, you click on the empty field and select the appropriate Main record. In Main, you click on Add exiting record then select the appropriate Payment record.

    But how do you link over 100 Payment records? Well through scripting. Let me know if you are interested in learning that as well.

Login to reply

Content aside

  • 4 hrs agoLast active
  • 3Replies
  • 12Views
  • 2 Following