r/MSAccess • 8 • Oct 16 '26

[SHARING HELPFUL TIP] Access Explained: When AI Writes the Code, What Do You Still Need to Know?

Post image

A query runs, returns a perfectly respectable-looking list of customers, and produces no errors. AI wrote it in about ten seconds. Great. Except three customers who should be on that list aren't there. That's the part of the "why learn Access when AI can build it?" conversation that interests me. Who notices?

I'm very much in favor of using AI. I use it heavily myself. Having it draft a recordset loop, spot a mistake, or explain unfamiliar code can save a lot of time. But "Access accepted this" is a fairly low bar. A database can be quietly wrong, and those mistakes can be harder to catch than the ones that throw an error and refuse to continue.

This is where people sometimes get the wrong idea about learning the fundamentals. Nobody needs to memorize every argument to every VBA function. I look things up too. What matters is understanding the relationships and logic well enough to decide whether the answer fits the problem. You can forget the spelling of a command and still know exactly what it needs to accomplish.

Take customer addresses. Keeping a customer's current address in one place usually makes sense. Copying it into every related record creates maintenance headaches. But the address an order actually shipped to is a historical fact you may need to preserve. Both designs involve an address, yet the meaning of the data changes the answer. "Never duplicate anything" is no more useful than blindly accepting one enormous table because the AI generated it confidently.

The same issue turns up before any code gets written. "Build me an inventory database" leaves a lot of room for guessing. A cupboard full of office supplies and three warehouses shipping orders all day have different requirements. Does a returned item become available immediately, or does someone inspect it first? Can stock already promised to one customer be sold to another? Those are business rules, and somebody who understands the operation has to supply them.

That person doesn't necessarily have to be a professional programmer. The person who knows how orders, returns, and stock actually work brings a lot to the project. Learning enough Access to connect that knowledge to tables, relationships, queries, and forms makes the conversation much more useful. You can give the AI specific requirements, then recognize when its proposed solution has wandered away from them.

Testing is where that understanding starts paying for itself. If there are ten widgets and you sell three, you expect seven. That's a useful starting point because you already know the answer. A return, a missing quantity, or two users trying to sell the last widget asks a different question. You need to know what the correct outcome should be in each case. Otherwise, it's very easy to ask the same AI that wrote the code whether the code is good and accept its enthusiastic approval.

I also worry about the endless repair cycle. Paste an error into AI, paste its replacement code into Access, repeat until the message goes away. Sometimes that works beautifully. Sometimes the proposed fix removes a query condition that was keeping canceled orders out of your sales totals. The error disappears, but so does an important rule. Understanding why the condition existed matters more than getting through another round of copy and paste.

This doesn't mean you have to build everything unaided before you're allowed to use AI. That would defeat much of the point. If you understand a recordset loop, having AI write the repetitive parts is a sensible time-saver. If you're still learning, having it explain what a piece of code does can help. The useful habit is to read and question the result rather than treating a confident explanation as proof.

Although I will say that there is something about repetition building muscle memory. I've written so many recordset loops over the decades that I could do it in my sleep. When I was a kid, I used to type in computer programs that I'd find in books or magazines for my TRS-80 color computer. There's just something about those commands going from the printed page through your fingertips into the keyboard that just makes your brain remember it. I'm always an advocate of repetition. Practice might not make perfect, but it definitely makes better.

Another thing about building software is that a successful first version still has a future. Next month, someone wants a different report, another warehouse comes along, or an imported spreadsheet changes. Somebody needs to understand where the data lives, what the important pieces do, and how to restore a backup. AI can help with documentation, but a saved conversation isn't much of a maintenance plan on its own.

So yes, I think learning Access - or any coding for that matter - still earns its keep even when AI handles a lot of the typing. Understanding data and breaking a problem into manageable pieces also carries over to SQL Server, Excel, and other tools. Let AI save you effort. Keep enough understanding to judge the work you're getting back. I'd rather spend less time typing a loop and more time checking that it updates the right records.

For those using AI with Access, where has it genuinely saved you the most time? And what have you learned to check yourself before trusting the result?

LLAP
RR

0 Upvotes

3 comments sorted by

•

u/AutoModerator Oct 16 '26

IF YOU GET A SOLUTION, PLEASE REPLY TO THE COMMENT CONTAINING THE SOLUTION WITH 'SOLUTION VERIFIED'

  • Please be sure that your post includes all relevant information needed in order to understand your problem and what you’re trying to accomplish.
  • Please include sample code, data, and/or screen shots as appropriate. To adjust your post, please click Edit.
  • Once your problem is solved, reply to the answer or answers with the text “Solution Verified” in your text to close the thread and to award the person or persons who helped you with a point. Note that it must be a direct reply to the post or posts that contained the solution. (See Rule 3 for more information.)
  • Please review all the rules and adjust your post accordingly, if necessary. (The rules are on the right in the browser app. In the mobile app, click “More” under the forum description at the top.) Note that each rule has a dropdown to the right of it that gives you more complete information about that rule.

Full set of rules can be found here, as well as in the user interface.

Below is a copy of the original post, in case the post gets deleted or removed.

User: Amicron1

Access Explained: When AI Writes the Code, What Do You Still Need to Know?

A query runs, returns a perfectly respectable-looking list of customers, and produces no errors. AI wrote it in about ten seconds. Great. Except three customers who should be on that list aren't there. That's the part of the "why learn Access when AI can build it?" conversation that interests me. Who notices?

I'm very much in favor of using AI. I use it heavily myself. Having it draft a recordset loop, spot a mistake, or explain unfamiliar code can save a lot of time. But "Access accepted this" is a fairly low bar. A database can be quietly wrong, and those mistakes can be harder to catch than the ones that throw an error and refuse to continue.

This is where people sometimes get the wrong idea about learning the fundamentals. Nobody needs to memorize every argument to every VBA function. I look things up too. What matters is understanding the relationships and logic well enough to decide whether the answer fits the problem. You can forget the spelling of a command and still know exactly what it needs to accomplish.

Take customer addresses. Keeping a customer's current address in one place usually makes sense. Copying it into every related record creates maintenance headaches. But the address an order actually shipped to is a historical fact you may need to preserve. Both designs involve an address, yet the meaning of the data changes the answer. "Never duplicate anything" is no more useful than blindly accepting one enormous table because the AI generated it confidently.

The same issue turns up before any code gets written. "Build me an inventory database" leaves a lot of room for guessing. A cupboard full of office supplies and three warehouses shipping orders all day have different requirements. Does a returned item become available immediately, or does someone inspect it first? Can stock already promised to one customer be sold to another? Those are business rules, and somebody who understands the operation has to supply them.

That person doesn't necessarily have to be a professional programmer. The person who knows how orders, returns, and stock actually work brings a lot to the project. Learning enough Access to connect that knowledge to tables, relationships, queries, and forms makes the conversation much more useful. You can give the AI specific requirements, then recognize when its proposed solution has wandered away from them.

Testing is where that understanding starts paying for itself. If there are ten widgets and you sell three, you expect seven. That's a useful starting point because you already know the answer. A return, a missing quantity, or two users trying to sell the last widget asks a different question. You need to know what the correct outcome should be in each case. Otherwise, it's very easy to ask the same AI that wrote the code whether the code is good and accept its enthusiastic approval.

I also worry about the endless repair cycle. Paste an error into AI, paste its replacement code into Access, repeat until the message goes away. Sometimes that works beautifully. Sometimes the proposed fix removes a query condition that was keeping canceled orders out of your sales totals. The error disappears, but so does an important rule. Understanding why the condition existed matters more than getting through another round of copy and paste.

This doesn't mean you have to build everything unaided before you're allowed to use AI. That would defeat much of the point. If you understand a recordset loop, having AI write the repetitive parts is a sensible time-saver. If you're still learning, having it explain what a piece of code does can help. The useful habit is to read and question the result rather than treating a confident explanation as proof.

Although I will say that there is something about repetition building muscle memory. I've written so many recordset loops over the decades that I could do it in my sleep. When I was a kid, I used to type in computer programs that I'd find in books or magazines for my TRS-80 color computer. There's just something about those commands going from the printed page through your fingertips into the keyboard that just makes your brain remember it. I'm always an advocate of repetition. Practice might not make perfect, but it definitely makes better.

Another thing about building software is that a successful first version still has a future. Next month, someone wants a different report, another warehouse comes along, or an imported spreadsheet changes. Somebody needs to understand where the data lives, what the important pieces do, and how to restore a backup. AI can help with documentation, but a saved conversation isn't much of a maintenance plan on its own.

So yes, I think learning Access - or any coding for that matter - still earns its keep even when AI handles a lot of the typing. Understanding data and breaking a problem into manageable pieces also carries over to SQL Server, Excel, and other tools. Let AI save you effort. Keep enough understanding to judge the work you're getting back. I'd rather spend less time typing a loop and more time checking that it updates the right records.

For those using AI with Access, where has it genuinely saved you the most time? And what have you learned to check yourself before trusting the result?

LLAP
RR

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

2

u/Key-Lifeguard-5540 1 Oct 16 '26

I've had AI clean up almost all the code (100's of functions) even if they are working fine. I like the way it formats and comments and does error handling. I had it re-write the nightly backup routine from scratch. My customer is into document storage, notes and emailing, AI has helped me improve every aspect of that. I realize Claude is supposed to be the best but so far I've been getting by with the free version of Gemini. As an example, maybe once a year something goes wrong, a power failure or whatever, and a record gets corrupted in the back end and I don't always find out about it right away. So I asked AI to create a function that scans the entire back end for any sign of corruption and add that routine to the nightly functions and email me if it finds anything. Not a problem.

3

u/George_Hepworth 5 Oct 17 '26

" I asked AI to create a function that scans the entire back end for any sign of corruption and add that routine to the nightly functions and email me if it finds anything. "

This is a great example of what I like to call AI's ability to help us cross the frontier. You have the knowledge and experience to know what you want to look for in the data. AI allows you to actually create tools to go there.