Portals, Commit, Primary Key

[bdam]

I've attached a sample file to show in general what I'm up against.

So let's say you have two tables, the parent table is books and the child table contains all the proposed titles.

So you have a layout showing records from the parent/books table with a portal showing all the related records in the child/titles table.

Now, what I need to do is have the ability to select which title is current so we can retain the list of all proposed titles but track which one we are currently going with.

So that boils down to a primary key of sorts in order to make sure only one title is selected as current.

So that's what I have in the sample file. The only problem I have (and it is slight) is that you can add a title, change the current "current" title to No and set the new title to "Yes" without having to click out of the portal for force validation for the individual changes.

It's tough to explain hense the example file. Try changing the current description to no and another to yes.

It's not the end of the world, just something my users can't seem to get.

Thanks,

Bryan

portal_commit_test.zip

[comment]

I would do it this way.

SelectChild.fp7.zip

[bdam]

Thanks Comment that's a pretty nice idea you have there.

Bryan