The problem described is not the only one, and consider when the application gets bigger, I am afraid I will get stuck somewhere and I will need to rethink everything. I also thought at keeping different match records for each user (one for userAway, one for userHome) but this looks even more wrong to me.

I gather from the terminology, that this isn't American Rules Football...

Which makes some of your terminology unfamiliar to me. So I have a few questions about your design and the purpose of this database.

What is a "user"? It's not a team, so I don't get what a record in this table represents. Perhaps a "fantasy" system?

And how do you record which team wins a given match? Using the fields for the number of away and home goals as match fields in your relationships between User_AllMatch and the two "...wins" table occurrences puzzles me. I don't see how that is intended to function.

In a typical team sporting event, a game or "match" table links to two occurrences of a Team table, one link for the away team and one for the home team. Two score fields record the score for the away and home teams. Comparing the scores--which can be done in more than one way in FileMaker determines which team gets the "win" for that match.

So this is a Fantasy system of sorts. It would seem that each "user" simulates being the "owner" of one or more soccer teams and thus "Their" team will play another gamer's team in a match. Is that a correct analysis?

If so, it would seem that you need to link each user record to one or more team records rather than directly linking them to a match record. The teams selected for the match would be linked to the match record rather than the users.

But since this is a database to support a game system, maybe you pick and choose your teams each time that you play and thus each user is not directly linked to a team that they "own"?

Well, I had two different designs in mind and how users linked to teams is the key difference here. This does require linking users directly to matches rather than linking them to teams that then link to matches.

But the whole "away vs. Home" designation complicates this as a user might select a team and play as the "Away" team in one match and select a different team and play as the "Home" team in another match.

And I assume that you want the total wins/losses statistics for each user?

Since you have indicated that you've changed your design, I don't know exactly what your current design is and I don't know what results you need out of it. That's why I asked some questions yesterday about the results that you want to see.

What I see here suggests that you may need two sets of table occurrences (called table occurrence groups), one for data entry--setting up a match and recording the score for each team/user pair. and one for reporting the win loss statistics that you want. (And my questions were to verify exactly what statistics you want to see here.)