Access JumpStart
  • Homepage
  • Blog
Select Page
  • Homepage
  • Blog

Implementing an Access architecture for the credit card payoff app

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...

Test Driven Development and Tables in Access

by Jonathan Halder | Nov 19, 2024 | Blogging, MS Access, MS Access Tables, MS Access VBA Coding, TDD

As I think about and discuss an architecture for an Access application I was considering the data persistence layer again and thinking about why one might want to test it. For example, what if your application is meant to track historic events throughout the history...

Considering the various user interface functions of a form

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....

Why, Jon, Why??? For the love of VBA, Why?????

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...

Separating business logic, user interface, and data persistence in a real world Access app

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...
« Older Entries
Next Entries »

Get a Daily Email

An email loaded with my tips and musings.

    We won't send you spam. Unsubscribe at any time.

    Recent Posts

    • Preparing to use AI for programming
    • Microsoft Access customer form logging strategy
    • The HCI Way™ – A Dive into Agile Project Management and Sales!
    • Why I think hourly billing is nuts
    • A day in the life

    Recent Comments

    1. RichardRost on Why I think hourly billing is nuts
    2. Using combo boxes to select an entry and update form fields | Access JumpStart on Hiding duplicate records using running totals over a group
    3. | Access JumpStart on Super Simple Code Kata
    4. Mike Wolfe on Running parallel SQL server databases for testing
    5. Custom Tags For Custom tags for form controls – reimagined code | Access JumpStart on Custom tags for form controls – the case to use them for

    Archives

    • May 2025
    • April 2025
    • March 2025
    • February 2025
    • January 2025
    • December 2024
    • November 2024
    • October 2024
    • September 2024
    • August 2024
    • July 2024
    • June 2024
    • May 2024
    • April 2024
    • March 2024
    • February 2024
    • January 2024
    • December 2023
    • November 2023
    • December 2022
    • March 2022
    • January 2022
    • June 2021
    • November 2020
    • October 2020
    • September 2020
    • August 2020
    • July 2020
    • June 2020

    Categories

    • Blogging
    • MS Access
    • MS Access Features
    • MS Access Forms
    • MS Access Queries
    • MS Access Reports
    • MS Access Tables
    • MS Access VBA Coding
    • TDD
    • Uncategorized
    • Versioning
    Copyright © Halder Consulting Inc.