Applying MVC to Microsoft Access

[RyanP]

Not a technical how-to question... just learning here / trying to wrap my head around this...

Have been researching the MVC architecture as an ongoing plan to upgrade into Web or Rich Client (.NET) apps in lieu of Access...

Is it too simplified (or outright wrong) to say that in Microsoft Access itself, the MVC architecture is essentially as follows;

Model - Queries & Tables

View - Forms & Reports (100% managed by the Access GUI itself, no coding)

Controller - Essentially all the VB Project behind the forms or in modules (or macros)

• Calling on the model (data manipulation, running queries, setting record sources etc)
  
• Creating/defining the views based on a mix of application & business logic
  
• Coordinating between the View & the Model

As far as commenting in code or naming of modules goes, good practice to identify what is associated with the Views & what is associated with the Model?

[June7]

Never encountered the term before (not formally trained in db concepts) but sounds reasonable.

Comments in code adequate to explain the code purpose and logic.