My company is a brewpub, and so all these different files are things I've come up with to help us manage the information. For example, 'banquets' holds the information for all the banquets people will have with us. 'Schedule' is the employee schedule for all the different departments (I can't believe it crashes your application!! I made it in FMP8A!! EEK!!). I have a bunch of others, as well: entertainment, for a schedule of people who will be playing at the brewery, recipes, for... recipes, purchase orders, etc, etc, etc. I suppose the reason I have them all in seperate files is because it seems like it would easier to fix when something goes horribly wrong. Likewise, if someone manages to crash one file, they don't all crash. Obviously I was wrong with this assumption, and will get to work putting them all into one huge database.
I do, however, think it would be worthwhile to create a Banquet record and have a calendar record be created because of that, instead of the other way round. Although I suppose that if I were in the calendar and made a new record with the tag of banquet, I could then go to the banquet layout and fill details from there. Which is exactly what you said. hmmm.... I have much to think about on this.
I ought to add that before this job, my experience with database work was to the extent of... arrays in c++. I know that doesn't count, but I think you see what I mean. I thought I was getting it down pretty good, but apparently I've missed a huge point!!!