MS Access
This is a MS Access application.
Form hould have no logic, UI only.
Each app has a controller module, that has all functions used by the app.
The controller accesses the data via class objects that perform the actual CRUD operations.
Access Form Hierarchy
Section titled “Access Form Hierarchy”💡 Access loads sub forms first, so to set programmatically, sub forms must be unbound, then set from the parent.
The app structure uses form that get loaded into subform controls. This was the only way to dynamically size all the forms base on the parent form “Shell”.
Shell (form)
-
ShellNavigation (control) Loads Navigation
-
ShellSub (control) Apps get loaded here *EventApp”, “SongApp”
-
AppFacet (control) Loads the facet forms (tab like control)
Each ‘app’ has a function that is called to populate it with a record by id.
For lists, the facet can be a container with header, and a control for the list subform
- AppSub (control) The list form
-
AppNavigation (control) loads navigation form that controls the loading the facet forms
-
AppSelector (control) Loads the apps selector, which selects the apps record source
-
SubDetail (control) loads the main information detail form
-
Theme module to hold current user theme properties for global access
User module to store current user properties for global access (to avoid initializing the user class on all procedures)