Computer Learning Zone

In part two of this Microsoft Access inventory database series, learn how to connect locations, areas, subdivisions, and items with proper one-to-many relationships and referential integrity. The focus is on keeping inventory data organized so items cannot be assigned to locations that do not exist, while avoiding the risks of cascade deletes.

Ever put something away safely, then spend six months wondering where it went? This episode introduces a practical Microsoft Access database design for tracking where books, tools, equipment, supplies, and storage boxes are located.

VB, VBA, VB.NET, VBScript, and VB6 share a family resemblance, but they are not interchangeable. The key question is not which version sounds newest, but where the code runs and which objects, libraries, and runtime it depends on.

For Microsoft Access developers, the answer is VBA, or Visual Basic for Applications. Learn why Access VBA examples differ from Excel VBA, why old VB6 projects are different from modern Visual Basic on .NET, and why similar syntax can still lead you toward the wrong help or code samples.

This episode also covers VBScript's aging role in Windows automation, Microsoft's plans to phase it out, and why inherited VBS files need a different maintenance plan. Whether you are writing code behind an Access form, maintaining a VB6 application, or working in Visual Studio, knowing the branch of Visual Basic you are using matters.

Can Microsoft Access hide password characters typed into a standard InputBox? This quick quiz explores why the built-in InputBox cannot display asterisks and why a custom form with a password-masked text box is the better choice when users need a more polished password prompt.

Along the way, it covers practical Access macro design: keeping shared passwords in a settings table, using DLookup criteria to retrieve the correct value, and making sure OpenForm runs only after the entered password matches the expected one.

It also includes an important security reality check. A password prompt can protect a menu path, but it does not secure every route into a database, especially when a plain-text password remains accessible in a table or the database design.

Learn how Microsoft Access QueryDefs let VBA create and save queries dynamically instead of forcing you to maintain a separate query for every possible field combination.

Test your Microsoft Access report skills with a beginner-friendly quiz on customer directories, report layouts, print preview, and mailing labels.

When VBA adds a new record in Microsoft Access, you often need the AutoNumber ID immediately afterward. That ID lets you open the exact order, customer, or log entry your code created instead of guessing based on the highest number or the newest-looking row.

In this episode, Richard explains why relying on Max(ID), sort order, or the last record in a form can fail in a multi-user database. Someone else may add a record at nearly the same time, leaving your code pointed at the wrong row without producing an obvious error.

The discussion uses a recordset and AddNew example from a food log database, showing the basic idea of returning the newly assigned ID from a function. With that key in hand, your calling code can reliably find the new record, move the form to it, or use it to create related records after the save succeeds.

Richard Rost shares his eight-month experience trying to use Tiller as a bridge between financial accounts, Excel, and a Microsoft Access database. The goal was simple: reduce the daily time spent checking balances and recent transactions across multiple accounts.

Instead, the workflow required repeated logins, account reconnections, authentication prompts, unreliable add-in behavior, and too many stale balances. Importing Excel data into Access was never the problem. The real issue was getting consistently fresh data into the spreadsheet without manual intervention.

This is a practical look at the difference between automation that sounds convenient and automation that actually saves time. Richard also explains why a supported API would better fit an Access-based workflow, and why he ultimately returned to gathering data directly from the financial sites he already checks.

What happens when fraud prevention is so strict that legitimate customers cannot complete a purchase? Richard shares his frustrating attempt to buy concert tickets, complete with valid credit cards, matching billing details, repeated authorization holds, and front-row seats that disappeared while the checkout system rejected him.

The bigger lesson applies far beyond ticket websites. Overly aggressive validation, endless confirmations, and rigid permissions can make software feel secure while driving away the people it is supposed to serve.

Good security should match the actual risk, provide clear feedback, and give legitimate users a practical way to recover from ordinary mistakes. A system that blocks everything may be safe, but it is not very useful.

The Expression Builder can look intimidating at first, especially when Access presents a long list of functions, fields, operators, and database objects. This episode explains what an expression is, what the Builder is designed to do, and when it is helpful to use instead of typing everything by hand.

Learn how expressions can calculate values such as an order line total, and how the Builder can help locate the correct name and syntax when referencing a control on an open form. It is especially useful when you know what result you need but cannot remember the exact function, form name, or control name.

Richard also covers common expression basics, including fields, operators, functions, brackets, quotes, and parentheses. The main takeaway is simple: start with small expressions you can verify, check the results carefully, and use the Builder as a guide while the syntax becomes familiar.