Hi pirxx, I am also interested to see forthcoming responses from more knowledgeable people on this forum than me, but I have a thought for you first. I sometimes look past the solutions needed and see practical uses and suggestions. My question here concerns why the tasks are deleted, I suspect, when completed. If I were your boss and depending on unknown operational details of which I do not know, I could sometime want an opportunity to review past tasks and related completion details. Instead of deleting each task, you could retain them by removing or changing their relationship and keep them in the related table assuming they would have enough identifiable details to find if needed. Sometimes we look back for information and when it's gone, it's gone.
Just a thought.
Thank you Tec man. In this case it is fully disposable information as it's proposed work and once it's approved it gets tracked in a different way. But I do appreciate the thought.
is there a calculation that would allow me to harvest both task lists and display in a single field?
You could use the List() function for this, e.g.
"Tasks:¶" & List ( VFX::SomeField ) & "¶¶Animations:¶" & List ( Animations::AnotherField )
There is a related table that breaks down the work into VFX-related tasks (related to the main table by the "SHOT NAME."
This is not a good way. You should have a ShotID field in the Shots table, with auto-entered serial number, and use that as the matchfield to the child tables.
As an alternative to using a portal in table view, which won't work as far as I know, try setting up a list view layout with your portals. This approach allows portals and you can get most of the features of a table view in your list view layout.
be able to resize columns in browse mode
be able to move columns to different positions
Be able to use modify to add/remove columns
You can still
See a list of all records in your found set in column format.
Sort on different fields by clicking the column names IF you write a sort script and set up the column label as a button to run that script.
In the end I'm using both suggested solutions on different layouts. Everyone is happy. Thank you heaps.