by Jonathan Halder | Nov 26, 2024 | Blogging, MS Access, MS Access Forms, MS Access VBA Coding
Some things you do when designing forms inherently reset the VBA environment. This takes all your existing object variables in that form and resets them. That’s why I often use a function to refer to an object to check to make sure it exists before I use it so I...
by Jonathan Halder | Nov 21, 2024 | Blogging, MS Access, MS Access Forms, MS Access Tables, MS Access VBA Coding
Now I have some code. Here’s what my form looks like so far: That contains the following module: ‘Form_frmAccounts Option Compare Database Option Explicit Private InternalAccount As AccountInterface Private Function Acct() As AccountInterface If...
by Jonathan Halder | Nov 20, 2024 | Blogging, MS Access, MS Access Forms, MS Access Tables, MS Access VBA Coding, TDD
I am currently discussing a credit card payoff application I’m working on in terms of Model-View-Control architecture in a series of messages. In this message, moving back to forms, I have built a form (user interface) which I am going to think of as the user...
by Jonathan Halder | Nov 18, 2024 | Blogging, MS Access, MS Access Forms, MS Access Tables, MS Access VBA Coding
Given a table as the persistence layer, we will use that table to save data for re-use. If there is a form bound to this table, what user interface functions does this perform? Controls bound to fields in the table are saved automatically based on various behaviors....
by Jonathan Halder | Nov 15, 2024 | Blogging, MS Access, MS Access Forms, MS Access Tables, MS Access VBA Coding
From my message yesterday:Separating business logic, user interface, and data persistence in a real world Access app | Access JumpStartI laid out a potential structure which included a Table which would be a data persistence layer a Form which represents a user...
by Jonathan Halder | Nov 14, 2024 | Blogging, MS Access, MS Access Forms, MS Access Tables, MS Access VBA Coding
Considering a simple app to calculate the number of payments it would take to payoff a credit card, how might I architect this in Access to optimize for separation of database, user interface, and business logic layers? Let’s consider a simple app with a table...
