Wow, what a great site this is! i cannot believe all of the knowledge here.

Right off the bat I have a question. Of course, that is why I joined. Maybe one day I will be able to provide an answer or 2.

I am attempting to create a database to track my workouts. Although there are other things I am tracking, the main 2 are cardio and weights. The question I have applies to both weights and cardio, but for simplicity's sake, I will use cardio.

I have a " MAIN" file (Unique key, date, Journal), a CARDIOMAIN file (Unique Key -from Main, activity, location, time of day, notes), and a CARDIODETAIL file (Unique Key -from Main, rep #, duration, distance, and several calc fields, and summary fields). For each entry, there will be one record in the Main, one in the CARDIOMAIN, and at least 1, but likely many in the cardio detail.

So I have a layout that contains date (from main), activity , notes, etc (from CARDIOMAIN), and a portal to CARDIODETAIL, with several fields.

Ok, finally to my question: I need to know how to set the field in the portal CARDIODETAIL (Unique key) to its related records in MAIN and CARDIOMAIN. I thought it was working when I entered the first record in the Cardiodetail portal, but when I add a second record, the calcs did not work. Then when I looked, I saw that the related unique key had no data.

Do I need a script on entering a new record in the portal to set the key field to its related value? I really wish I could just tab to the next field and keep entering data (reps)

Any clues for the clueless appreciated.

Al in Nebraska

If your main record has a unique key, and your related file does not use a calculated key for the relationship, and the relationship is set to allow creation of related records... there should be no problem. Are the fields in the portal from the related file? That's one common mistake.

Hi Al,

As Tom indicated, it should work if your relationship is correct (allow creation of related). Do you have an auto-enter option set for your IDs?

Something else to consider ... your RelatedID key doesn't need to be in the portal. If it's set up correctly, you would click into any field in the portal except the ID field, and a new related record will be created if it doesn't exist. FM will insert the related ID automatically

LaRetta