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...
by Jonathan Halder | Nov 13, 2024 | MS Access, MS Access Forms, MS Access Tables, MS Access VBA Coding, TDD
What would your strategy for splitting a form between logic and database record management? I’m honestly asking, because that’s what I’m thinking about today. I’m thinking in terms of creating tests a la TDD style work. Having business logic...
by Jonathan Halder | Oct 25, 2024 | Blogging, MS Access, MS Access Tables
SQL Server Express is a version of SQL server you can install on a computer available to all your Access Front End users that will provide a more robust back end than using Access accdb files. How much does it cost? It’s free! So what’s the catch?...
by Jonathan Halder | Oct 7, 2024 | Blogging, MS Access, MS Access Queries, MS Access Tables
This morning I was working on a query for a customer report that took me longer than I expected and produced more problems than I expected. I actually had 3 tables named customers, orders, and payments. Customers can have multiple orders, and have a one to many...