I have a list where I have a lot of fields that are used only depending what kind of activity (choosen also via a dropdown). So I the result is in most cases that need a resulting field that holds the value from one field or another field (or fields) depending the value of another field. For expample: Activities can be 'in house' => choosen from a list of or own locations ( another list with the data via dbjoin-dropdown), or somewhere else where we enter the address in another field.
I see 2 possible workmethods:
- The use of many calc-fields to get the resulting data nice in the listviews with the other fields in the edit-form.
- the use of a SQL-view where I concatenate/calculate the right data for the list.
Wich way is the better way?
What is better in preformance (speed)?
Are the calculations also done if I use the list in a dropdown for another list?
When I use a SQL-view to show the list. Can I easily open the edit-form with the raw data when I click the edit button in that list?
I hope my questions are clear and understandable as my english is not that good,
Greetings,
Filip
I see 2 possible workmethods:
- The use of many calc-fields to get the resulting data nice in the listviews with the other fields in the edit-form.
- the use of a SQL-view where I concatenate/calculate the right data for the list.
Wich way is the better way?
What is better in preformance (speed)?
Are the calculations also done if I use the list in a dropdown for another list?
When I use a SQL-view to show the list. Can I easily open the edit-form with the raw data when I click the edit button in that list?
I hope my questions are clear and understandable as my english is not that good,
Greetings,
Filip