Well, I'm looking for this in the forum with no success.
My question is to know what is the best practice to build a form with a header-detail structure. I come from Windows (specifically from Delphi) and in there we have grids and the clientdataset. Here doesn't exist, so I'm bit lost.
I made many basic tutorials, but in none gave this info. All I have found is saving records from a simple table, with no relationship with others.
I don't know what's the best, no only to build, also to the final user:
1 - two activities with two different forms (one for head and one for detail)?
2 - make a form to introduce new records, or use the same form for all, saving changes when the user change, or edit something?
3 - save a record when a data change (for examples when a record lost focus)?
Don't know. Many questions, and many doubts, and no answer...
So tell me, what are best practices for this? Or what are most used in Android community?
Thanks.
My question is to know what is the best practice to build a form with a header-detail structure. I come from Windows (specifically from Delphi) and in there we have grids and the clientdataset. Here doesn't exist, so I'm bit lost.
I made many basic tutorials, but in none gave this info. All I have found is saving records from a simple table, with no relationship with others.
I don't know what's the best, no only to build, also to the final user:
1 - two activities with two different forms (one for head and one for detail)?
2 - make a form to introduce new records, or use the same form for all, saving changes when the user change, or edit something?
3 - save a record when a data change (for examples when a record lost focus)?
Don't know. Many questions, and many doubts, and no answer...
So tell me, what are best practices for this? Or what are most used in Android community?
Thanks.