uuYou need to make sure your tables are correctly linked.
In the relationships graph, you should see this:
MAIN TABLE --------------- RELATED TABLE
Likewise, your layout should match this:
YOUR LAYOUT SHOULD BE FOR THE MAIN TABLE ---- PORTAL SET TO RELATED TABLE
All the fields in the portal should belong to the related table.
Hope this helps.
That suggestion gets me so close to what I want it hurts. Now everything seems to work right EXCEPT: When I add a sample to the current event it shows up correctly. Then I go to a different event and add a sample, but it shows up in the event I previously added to. It seems like it is not updating the Event ID when I change events, but is still holding the initial value.
Make sure your two tables are related by a unique identifier.
For instance -
(In this example, contactsA is a list of contacts, eventB is a list of events for each contact)
If you have contactA with a serial number field, then in the eventB table, create a field called foreign_key or such. In the relationship view, double click the table for eventB (or whatever your related table is) and make sure contactA serial_field is linked to EventB_foreignKey (a number field, with NO serial defined.).
(In case you don't know about serial fields, make a number field, double click it and check on the serial number function. this will make a unique id number for each record.)
Depending on your set up, you might need to check the box that says allow creation of records through this relationship in the related table.
Then, on your layout, you can create related records in the portal for that main table record. Also, when you go to a new record, you shouldn't see the previous records created earlier unless you go back to that main record.
Thank you for the help. It took me a while (I'm a slow learner) but it works well now.