Thank you Erel, I am now on the right track.
As a rule, is it good practice to put separate app functionality in different activities/module, with their associated pages and panels, or as some posters seem to put all logic in a single activity and load their pages and panels as required?
My current App currently has over 6500 lines of code spread over 10 Activities/Services, including all of the required #if b4a/b4i logic and has 6 somewhat distinct Activities, so through my "Activity.AddMenuItem" menu on each page, I can go directly to the root of any of those activities, closing the current activity with an "Activity.Finish" in the "Activity_Pause" sub on all but the first Activity. Each Panel that gets loaded within an Activity has Save/Close/Cancel buttons that work like a back button.
How can I capture the back button in both B4i and B4A and popup a modal dialog to ask if a Save/Close/Cancel event needs to be performed?
I guess my approach is more like a web developer rather than a pure App developer, but I recognise that step 1 seems to become aware of the differences in approach, so I seem to be slowly getting there. Much compliments on your product, I will be a B4X lifer...