I'm having trouble determining how to design my fmp9 db. I had a solution that worked but was not user-friendly, and my attempt to make it user-friendly has resulted in a mess.

Each day I need to specify

--which Projects I worked on

--which Tasks I performed for each project that day

--and what set of Resources I used for each of those tasks.

I have separate tables for possible tasks and resources, and then I have these additional 3 tables: Projects, TaskEvents (where the Date gets involved), and Resourceevents.

Its very user-unfriendly to make a new record on a separate screen for each project/task/resource combo that occurs in one day, and so I need to do this in a sort of table layout, so I'm trying to ENTER all of the project/task/resource combos for ONE day on the same screen, by entering them into a portal that is self-joining.

these are my questions:

1. Am I correct to be doing this using a self-join?

2. do the portal fields all have to be from the same table?

3. why is my resourceeventID field not auto-entering values (as specified to) as i enter data into the portal that points to the resourceevent table? Because of self-join? I've checked 'create records' in either direction in the relationship so I don't know why its not creating those portal records?

4. should i even have a taskevent table?

Attached is my db with user/pass mark/mark. The layout i'm working on is the Event Copy at the bottom.

sustainabledesign2.fp7.zip

Readers have noted that the file is pass protected. As I state in my first post, user/pass = mark/mark