[OBP]

Not really, as long as the way that you have it WORKS, it is OK, it might not be ideal, but having it working is the important part.
But you might run in to problems later with any analysis that you might want to do.

[hqnet]

Hi OBP
Ok, my original problem with relations is 'solved' in the sense that I learned to propagate the relations.
But know, if I try to go by your example and use a single table for repairs I find another problem: due to the large amount of fields, I need to split them into forms, and when I fill two forms each one uses a different RepairID, thus creating one record for each form (in the table). This means that I get up to 5 rows stored, where only the values of one form is stored in each row.

I realize this is not happening in your example, where you used sheets style for the input, but I have a lot of fields and I need to have them grouped in a more visual manner, which is why I am using a design-form.

I am attaching a mod to your example where I try to illustrate what I just described. You will see that the RepairID is different in the two tabs.

TIA

[OBP]

I thought you were going to continue using the 5 Table method, have you abondoned that idea?
I have looked at your example and the RepairID is the same in both Tabs for each Car Visit record, so I am not sure what you mean.

[hqnet]

Hey, thank you for still being there!

I didn't abandond the idea, but as you said it could be safer to use a single one in the long run, I decided to take the advice.

To elaborate on the example:
- create a new visit for an existing car
- enter the date, wich gives it a VisitID
- move to tab1, enter a Repair Category and description, you get a RepairID
- move to tab2, enter a Repair Category and you get a different RepairID

If I were to store this, it would create two rows in the table, each one with only half the fields used.
Also, I would be entering one set of values in two forms but when reviewing the data it would be shown as two separate sets which becomes too confusing IMHO....

[OBP]

Ok the Tabs should be on a Visit & Repair form, so that the RepairID gets generated and used to link to the Tabs, thus using the same ID

[hqnet]

I had tried that but as the object would not hide when changing tabs I thought it couldn´t be done... Based on your comment I insisted until I got it right, so now I have to reproduce it in my original project but I think it will finally take off!

Thanks a Ton!!

[OBP]

My pleasure.

[hqnet]

Ok, I backported the new knowledge ( ) to my project and so far it is working as expected, so I am marking the thread solved. Thanks again!