If you are not going to use a portal. Why do you need a table occurrence? Why not just perform a find to control what records appear in the layout's found set?
I suppose. Maybe I'm making it harder than it needs to be, But here's my logic.
For candidates that are not assigned to a requisition, there are certain fields that do not apply to them, so I have one layout that displays only certain fields associated with that candidate. Once that candidate is assigned a requisition, there is a whole other set that applies to them, so I have them displayed on a different layout. I didn't want to have to go through the step of finding records each time I go to a specific layout. Do you think it would be just better to assign a script trigger when loading that layout to find the records that I want visible in that layout.
I think I'm stuck on using the list view too, experiementing with a really cool layout that I purchased from ISO. Maybe I need to get over that in this case.
If both layouts are based on the same table occurrence, they'll have the same found set, current record and sort order. Thus you can find and sort records on the first layout and just switch layouts when the user clicks a row in the list view. If the second layout is set to form view, the record they see will be the record for the listed record they clickec and no find was required past the original one to pull up the list.
Thanks Phil for the insight!!!! Not quite the answer I was seeking, but I love that you always help me look at it a bit differently. I know my experience shows, but I'll get there.
I am currious as to how you can keep on the posts out here.
Thank you again.