Computer Learning Zone

Test your Microsoft Access VBA knowledge with five quick questions about private procedures, procedure parameters, Select Case statements, ElseIf chains, and operation-specific validation.

Learn why a Private Sub stays local to its form module, how arguments such as "Add" are passed into a procedure, and why Select Case can make a calculator-style routine easier to read and maintain.

The quiz also covers a common control-flow detail: ElseIf stops checking later conditions after a match, while separate If statements continue evaluating. Plus, see why divide-by-zero validation belongs inside the division case, right before the calculation happens.

When an Access form is already open, filtered, and positioned on the record you need, switching views just to reach its VBA code can be an annoying interruption. This episode covers a small developer customization that adds a Quick Access Toolbar button for opening the code module behind the form currently in use.

Using Screen.ActiveForm, a public VBA function can identify the active form and open its corresponding Form_ module. A simple RunCode macro provides the bridge needed to place that function on the Quick Access Toolbar.

It is a modest productivity improvement, but it saves repeated clicks, avoids unnecessary Design View detours, and helps preserve your place while developing and debugging Microsoft Access forms.

Test your Microsoft Access control formatting knowledge with a quick quiz on text colors, RGB expressions, and macro-driven property changes.

Learn the difference between ForeColor and BackColor, why RGB(0, 0, 255) produces blue, and how RGB expressions help Access assign usable numeric color values. It also covers changing FontSize with a macro and a common snag when pasting hexadecimal color-picker codes like #FF0000 into a SetValue action.

A useful refresher for anyone building Access forms that need clear visual cues without accidentally repainting the whole control.

Test your Microsoft Access relationship knowledge with five questions about parent and child tables, subdatasheets, orphaned records, and referential integrity.

Find out what happens when you try to delete a customer who still has related contact records, why Access normally blocks that deletion, and when cascade deletes can change the outcome. It is a useful reminder that deleting a parent record without considering its children can create data problems fast.

The quiz also covers the requirements for enforcing referential integrity, including compatible field data types and a unique parent key. See whether your CustomerT and ContactT relationship is properly protected or leaving records to wander around without parents.

Test your Microsoft Access relationship skills with five expert-level questions about parent and child tables, one-to-many relationships, subdatasheets, orphaned records, and referential integrity.

Find out what happens when you try to delete a customer who still has related contacts, why Access blocks deletions in a properly enforced relationship, and when cascade deletes can change the outcome. It is a useful refresher for avoiding broken customer and contact records.

The quiz also covers the database setup Access needs before it can enforce referential integrity, including compatible field data types and a unique parent key. See whether your relationships are protected or wandering around without parents.

Continuous forms give you much more design control than a datasheet, but hiding a field can leave awkward blank gaps in every row. This episode looks at a practical VBA pattern for letting users choose which fields they want to see while keeping the remaining controls neatly aligned.

Learn how checkbox-based field selectors can show or hide both detail controls and their matching labels, then reposition the visible fields using their Left positions and actual widths. The result is a compact, configurable list that still looks like an intentionally designed Access form.

It is a useful approach for forms with different audiences, especially when some users need a simple view while others want additional columns. The discussion also covers when Datasheet View may be the better choice and how this basic technique can grow into saved layouts, user preferences, and reusable form layout management.

Run-time error 9, "Subscript out of range," usually means VBA is trying to access something that does not exist. Often it is an array position outside its valid range, but it can also involve missing collection items or keys.

This episode explains what a subscript is, why indexes can be too high or too low, and why zero-based arrays created with VBA's Array function are a common source of off-by-one mistakes. Three values might sound like positions 1 through 3, but VBA may actually number them 0 through 2.

Learn how to use LBound and UBound instead of hard-coding loop limits, how to inspect the failing line in the VBA editor, and why "On Error Resume Next" is not a real repair. It is less like fixing the engine and more like covering the check-engine light with tape.

Conditional formatting can flag an entire field, but that is not much help when a long notes box contains several paragraphs. In this episode, Richard Rost shows how to highlight every occurrence of a search word or phrase inside a Microsoft Access text box without changing the original table data.

The discussion uses VBA, rich text controls, HTML-style formatting tags, and the Replace function to create a separate display field with highlighted matches. It also covers why quote handling matters, how case can affect displayed search text, and why this approach is especially useful for large plain-text notes fields.

Richard also explains important limitations, including complications with existing rich-text formatting and why an unbound rich-text display does not behave correctly in continuous forms.

Do you really need to replace a working Microsoft Access application just because remote employees, mobile devices, or web access are entering the picture? Often, the answer is no. The important question is not whether Access is old, but what business problem actually needs to be solved.

This episode separates the Access front end from the database backend and explains why they do not have to be replaced together. A business can move shared data to SQL Server, keep familiar Access forms, reports, queries, and VBA for office staff, and add a focused web or mobile interface only where it is needed.

Learn why opening an ACCDB file directly over the internet is a bad idea, why the 2 GB Access file limit does not necessarily mean an Access application cannot grow, and when remote desktop, SQL Server, a customer portal, or a full web application makes sense.

A mature Access database often contains years of business rules, automation, reports, and hard-earned exceptions. Before rebuilding it all, make sure you are solving a real requirement instead of reacting to marketing.

BOF and EOF are easy to memorize in Access VBA, but understanding what they mean can save you from some very confusing recordset behavior. This episode explains why EOF alone does not prove a query returned no records, especially after code has moved past the last row.

Learn how DAO recordsets track a current record, what happens when you use MoveNext or MovePrevious, and why BOF and EOF are boundary positions rather than actual records. The key empty-recordset test, rs.BOF And rs.EOF, makes much more sense once you can visualize what is happening.

We also cover practical details such as where a normal recordset starts after OpenRecordset, why RecordCount can be misleading, and why navigation and deletions can affect what those flags tell you.