You can only run an import into one table at a time. You could script multiple imports into multiple tables. Filemaker will create the new tables, and you can delete the fields you don't want.
You would have to create any relationships manually.
I'm not sure you have the optimal structure setup. Does each competitor gets a score in each "round", or do they skip rounds?
Are they playing each other as well? What is the sport we're talking about? What are you actually collecting and what do you hope to track/report on?
It my be that you need tables like this:
Competitor - CompetitorID, name etc ( this may be a small table with few records,or thousands as for the olympics)
event - eventID, date, ground, eventcompetitor1, eventcompetitor2, score1, score2 ( for two teams home & away) or
event - eventID, date, eventname, ground etc
score - ID, eventID, eventcompetitorID, score
Then you would create relationships between the event, competitor and score tables as required.
Then you can run reports by sorting the games by year, quarter or ground or competitor etc
You could do this kind of on the fly by creating global fields as well, and crating relationships you could populate via lists, which would work well for a small project for a single user.
It's hard to give you much more help without knowing more about your project.
Main Topics
Browse All Topics





by: lesouefPosted on 2009-09-07 at 03:15:50ID: 25273955
you can import twice the same file in 2 separate record and pickup only the required records for each table