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?

1. Controls bound to fields in the table are saved automatically based on various behaviors.
2. Controls can have different ways to format the data to display to the user (like using $ with currency and making negative numbers red)
3. The form provides it’s own controls for navigation from record to record, and has the ability to display the records one at a time or in a growing list in continuous view
4. Access forms also allow filtering and sorting of the records with built in controls.
5. There are validation rules that can be put in each control – but should we prefer using business rules for this, or utilize the built in Access validation? In addition, validation rules can be placed in the data persistence layer, the table has rules that can be defined for the validity of the data.
6. The form and controls trigger different events as the user interface is being used. These events can trigger code or macros to run that are embedded in the form AND we can listen for these events by registering them in class objects.
7. In order to calculate a display something like a payoff date, we could embed this code into the form itself, or create a calculated field in the table, or again separate the calculations out into a class module.
8. There is a combo box in the form that stores an Account Type ID while displaying an Account Type Name.

I want to separate the user interface functionality from the business logic here.

So far, I’ve identified that I want to have business logic for validating a record and calculating a payoff date. Perhaps we can blend those easily into the form using a class. I’ll look at how I might do that in the next message.

Previous messages leading up to this one.

You can split a db, but can you split a form? | Access JumpStart
Separating business logic, user interface, and data persistence in a real world Access app | Access JumpStart
Why, Jon, Why??? For the love of VBA, Why????? | Access JumpStart