Computer tutorials, tips, and tricks to help you learn Microsoft Excel, Access, Word, and lots more. Visit our full site at www.ComputerLearningZone.com.
Time for a quick Microsoft Access forms quiz. These are beginner-level questions, but they cover some of the little details that can make form design either smooth and painless or oddly frustrating. Grab a piece of paper if you want to keep score, and try to answer each question before checking the answer.
The questions below cover form record sources, bound controls, attached labels, resizing the Detail section, and one very common misconception about changing a text box's colors. The T-Rex is staying behind the fence. Hopefully.
Question 1: Which form property tells Access which table or query supplies its records?
A. Record Source B. Record Source C. Caption D. Default View
The answer is Record Source. A form's Record Source is where Access gets the records displayed on that form. It can point to a table, a saved query, or even an SQL statement in more advanced situations. The Caption merely changes the text shown in the form's title bar, and Default View controls how the form is displayed.
Question 2: You drag a Short Text field from Add Existing Fields onto a blank form in Design View. What normally appears?
A. A new table and a query B. A label containing every record C. An unbound text box only D. A bound text box and an attached label
The answer is D, a bound text box and an attached label. Access creates a text box that is bound to the field you dragged onto the form, plus a label that displays a friendly caption for that control. The text box shows and edits data from the underlying record. The label is just the descriptive text sitting next to it.
Question 3: You want to remove an attached label but keep its text box on the form. What should you delete?
A. Only the label B. Only the text box C. The field in the table D. Both controls, then save the form
The answer is A, only the label. The label and text box may be attached to one another for moving and positioning purposes, but they are still separate controls. Select the label itself and delete it. Do not delete the text box unless you also want to remove the control that displays and edits the field's data. And definitely do not delete the field from the table just because you do not like the label. That would be using a chainsaw to open an envelope.
Question 4: A form has a large unused area below its controls. How can you reduce that space in Design View?
A. Make every text box taller B. Delete records from the table C. Drag the bottom edge of the Detail section upward D. Change the form's Record Source
The answer is C, drag the bottom edge of the Detail section upward. In Design View, the Detail section has a lower boundary that you can drag upward to eliminate unused space. This is a simple cleanup step, but it makes forms look much more intentional. Nobody needs a form with three controls at the top and a football field of blank space underneath.
Question 5: You change an editable text box's background to gray. What does that change do by itself?
A. Prevents users from typing in it B. Changes its appearance but does not prevent editing C. Changes its field to AutoNumber D. Removes it from the tab order
The answer is B, it changes the appearance but does not prevent editing. Changing the Back Color property is cosmetic. A gray text box can still be editable unless you change other properties, such as Locked or Enabled, or otherwise control editing through the form's settings. Color can suggest that something is read-only, but Access does not enforce that suggestion automatically.
How did you do? A perfect 5 out of 5 means you are well on your way to saving the park and all of its customer data. Missed a couple? No worries. These are exactly the kinds of form basics that become second nature once you spend a little time building real forms.
If you want to see these concepts in context, watch the embedded video. The related Access Beginner Level 1 lesson covers more about building and cleaning up a customer form.
Security is important. Fraud prevention is important. Protecting customer data is absolutely important. But there is a point where security stops protecting your business and starts actively preventing people from doing business with you. If a legitimate customer can't complete an ordinary purchase, your system may be very secure, but it is also failing at its basic job.
I ran into this while trying to buy tickets for a Rush tribute band. I had two excellent front-row seats in my cart, a valid credit card, and every intention of giving this venue my money. I had bought tickets from them before. I had supported the place for years. Yet their checkout system decided that apparently I was too dangerous to sell concert tickets to.
The checkout page claimed that my billing information did not match my credit card statement. So I did what any reasonable person would do: I checked the address, checked the ZIP code, checked the card number, tried again, and got the same error.
Then I tried other cards. Mastercard, Visa, American Express, Discover. Different browser. Different computer. Phone. At some point, I was no longer purchasing tickets. I was performing unpaid quality assurance testing for their website.
To their credit, support responded quickly. The explanation was that the billing information had to match the card statement exactly. Not just the house number and street name. Apparently even something as minor as "Terrace" versus "Ter" could matter. On some cards my name appears as Richard Rost, while on others it is Richard D. Rost. Those little differences can trigger address-verification and fraud systems.
Fine. That is not entirely unreasonable. Card processors use address verification systems, and exact matches can help catch fraudulent transactions. The problem was that I followed the instructions, matched the information as closely as possible, even used the ZIP+4, and the transaction still would not go through.
What made it worse was that the system could obtain authorizations from my bank. An authorization is not necessarily a completed charge, but it can still temporarily tie up funds or appear as a pending transaction. So now I had multiple authorizations on several cards, no tickets, and a bunch of extra stuff to keep an eye on.
The eventual answer from the venue was, "Call the box office."
Now, I understand that sometimes a human needs to step in. But the whole reason I was using the website was because I wanted to buy tickets online, quickly, without sitting on hold or having to explain that, yes, I really do live at the address shown on my credit card. By the time I got around to dealing with it, those front-row seats were gone.
That is the real lesson here: security controls have to fit the risk, but they also have to leave legitimate users with a practical path forward. A system that blocks everything is easy to secure. It is also easy to make useless.
This applies far beyond ticket sales and online shopping. It applies to websites, customer portals, Access databases, internal business software, and anything else people have to use to get work done.
Think about the systems you have used where every action produces another warning. Delete a record? "Are you sure?" Click Yes. "Are you really sure?" Click Yes again. "This action cannot be undone." Yes, yes, yes. Eventually users stop reading. They do not become more careful. They simply learn where the Yes button is.
And that is not good security. If people automatically click through every warning because there are too many warnings, the important warning gets ignored right along with the pointless ones.
In an Access database, for example, you may be tempted to lock everything down because you are worried someone will accidentally delete or alter important data. That concern is valid. But rather than forcing users through five confirmation prompts, consider whether the mistake can be made easier to recover from.
Could you archive records instead of permanently deleting them? Could you use a status field such as Active, Inactive, Cancelled, or Archived? Could you provide a restore option for an accidental deletion? Could you allow someone to correct a spelling error without giving them unrestricted access to rewrite the entire database?
Those are usually better questions than, "How can I make this impossible for anyone to touch?" Sometimes you do need strong restrictions. Sensitive financial information, payroll data, medical records, permissions, and irreversible actions deserve serious safeguards. But an ordinary typo in a customer address should not require a meeting with the database administrator, three forms of identification, and a blood sample.
Good security gives users clear feedback. If an order fails, tell them why in language they can understand. If the address does not match, tell them which part appears to be the problem. If the system cannot verify a transaction, provide a useful next step that actually has a chance of resolving it.
Do not make users guess. Do not send them in circles. And do not make them repeat the same failed attempt over and over while your website quietly creates pending authorizations on every card they own.
It is also worth testing your system from the customer's perspective. Try a normal purchase. Try entering an apartment number. Try a street abbreviation. Try a middle initial. Try a recently moved customer whose billing address may not look exactly like the formatting in your database. Try an ordinary user fixing an ordinary error in your software.
Security rules often look perfectly sensible when you are staring at a settings screen. They can look much less sensible when they prevent a long-time customer from buying the thing they came to buy before it sells out.
Fraud prevention should protect your customers and your business, not punish the people who are trying to give you money. Make your safeguards appropriate, make failures understandable, and make recovery possible. Otherwise, your perfectly secure system may end up securing you right out of a sale.
As for the Rush tribute show, I never did get those seats. But there was a happy ending: next month I will be seeing the actual Rush in Tampa on their 50-something tour. That is a pretty decent upgrade.
You can watch the embedded video for the full story and a few more thoughts on balancing security with usability. The same principle applies whether you are building an e-commerce site, an Access database, or any other system people need to use without fighting it every step of the way.
The Microsoft Access Expression Builder can look pretty intimidating the first time you open it. There are lists of objects, categories, functions, operators, and mysterious symbols everywhere. The good news is that you do not need to memorize all of it. The Expression Builder is simply a tool to help you assemble expressions when you need Access to calculate something, compare values, filter records, or pull information from an open form.
An expression is anything Access can evaluate to produce an answer. That answer might be a number, text, a date, True or False, or sometimes no value at all. For example, multiplying Quantity by Unit Price to get a line total is an expression. Combining FirstName and LastName is an expression. Comparing a due date to today's date is an expression. Access does the work, but you have to tell it what you want.
If you have been working with Access for a while, you may find it quicker to type expressions directly. I usually do. But the Expression Builder is extremely useful when you are learning, when you cannot remember the name of a function, or when you need to reference a control on a form and cannot remember what you named it three years ago. Which, of course, never happens to any of us.
You will usually open the Expression Builder from the place where you are entering an expression. In Query Design View, click in a Field row or Criteria row, right-click, and select Build. Depending on your version of Access, you may also have a Builder command available on the ribbon.
On forms and reports, certain properties can accept expressions. The most common example is the Control Source property for a text box. Those properties often have a small button with three dots beside them. Clicking that button may open the Expression Builder, although be careful: Access has several different builders, so not every three-dot button opens the one you want.
You can also use Ctrl+F2 in many supported locations. Make sure it is Ctrl+F2, not Shift+F2. Shift+F2 opens the Zoom box, which is useful in its own right, but it is not the Expression Builder.
Once the Builder opens, the expression itself appears at the top. That is where you can type, edit, and insert the pieces of your expression. If you only see a small window at first, click More to expand it and reveal the lists underneath.
The bottom portion of the window is divided into three lists: Expression Elements, Expression Categories, and Expression Values. Think of these as a filtering system. You choose a broad category on the left, narrow it down in the middle, and then pick the specific item you want on the right.
For example, if you are looking for a function, expand Functions, choose Built-In Functions, select a category such as Date/Time, Financial, or Math, and then choose the function you need. Access will insert it into your expression and often show helpful information about its arguments.
You can also browse the objects in your database. Tables, queries, forms, reports, and other database objects are available from the list. This is especially handy when you need to refer to a field or a control but do not remember its exact name.
Let's start with a simple calculated field in a query. Suppose your order detail records include a Quantity field and a Unit Price field. You want another column that calculates the total for each line item. If a customer orders three items at $10 each, the answer should be $30. If they order two items at $7.50 each, the answer should be $15.
In Query Design View, click in an empty Field cell, right-click, and choose Build. In the Expression Builder, you can double-click the Quantity field and then the Unit Price field. Access will place both field references in the expression box. You still need to tell Access what to do with them, of course. Two field names sitting next to each other do not mean anything useful.
For a line total, use the multiplication operator, the asterisk. The basic expression is:
[Quantity] * [Unit Price]
When you click OK, Access puts the expression into the query design grid. It may initially name the field something like Expr1. That works, but it is not very descriptive. Give the calculated field a useful alias, such as:
Line Total: [Quantity] * [Unit Price]
You could call it Extended Price instead if that is the terminology you use. The name is up to you. The important part is that Access now calculates a separate total for every record returned by the query.
Always run the query and check a few results by hand. Expressions can be perfectly valid from Access's point of view while still giving you the wrong answer because you asked the wrong question. Computers are funny that way. They are very obedient, even when obedience is a terrible idea.
The Expression Builder is also very useful when building criteria based on an open form. Suppose you have a Customer form open and a query that normally shows all customer orders. You may want the query to show only the orders for the customer currently displayed on that form.
In the query design grid, place your cursor in the Criteria row beneath CustomerID, then open the Expression Builder. Browse through your database objects to Forms, then choose Loaded Forms. Loaded Forms means forms that are currently open. Select your Customer form, then find the control that contains the customer ID.
Access builds the proper reference for you, which will look something like:
Forms!CustomerF!CustomerID
The exclamation points are often called "bangs" in Access and VBA circles. The first part identifies the Forms collection, the second part is the form name, and the last part is the control name. You do not need to type all of that by hand if you let the Builder insert it for you.
Once that reference is placed in the CustomerID criteria row, the query can compare each record's CustomerID to the CustomerID on the open form. Run the query while viewing Customer 1 and you see Customer 1's orders. Navigate to a different customer, run the same saved query again, and now you see that customer's orders. No typing an ID number into the query every time.
This is one of the biggest reasons beginners should get comfortable with the Expression Builder. It helps you avoid tiny spelling mistakes in form names and control names, and tiny spelling mistakes are more than enough to make Access throw a fit.
Expressions can be used in lots of places throughout Access. You can create calculated query fields, specify criteria, set control sources on forms and reports, create validation rules, set default values, and build conditional formatting expressions. You can join text together, calculate dates, test values, return messages, and much more.
A few basic rules are worth keeping in mind. Square brackets identify field names and control names, particularly if the names contain spaces. Text values need quotation marks, such as "Paid". Functions use parentheses, such as Date() for today's date. Operators such as +, -, *, /, =, and & tell Access what action to perform.
You do not need to master every function and every punctuation rule today. Start with small expressions where you can easily verify the result. A simple line total is a great place to begin. Then move on to form references, date functions, concatenated names, and conditional expressions such as IIf when you are ready.
The Expression Builder is not something you have to use forever. As you gain experience, you will probably type many expressions directly. But it remains a handy reference tool, especially when you need to browse available functions or find the exact name of a form control without digging through every object in your database.
Watch the embedded video for a full walkthrough of the Expression Builder, including the query calculation and open-form criteria examples. Once you start recognizing where expressions can be used, you will find them all over Access.
Think you have your Access VBA and SQL INSERT statements under control? Good. Now let's see if your code survives a few very common traps: inserting records without overwriting old ones, using the correct destination fields, handling Null values, and making sure your field order does not quietly scramble your data. Mars colony records are optional. Bad data is not.
This is a developer-level Access quiz with five questions. Give yourself a few seconds to answer each one before reading the explanation. If you want the full quiz experience, watch the embedded video and pause it before each answer.
Question 1: Your VBA button needs to add one new log record to a table without changing any existing records. Which type of SQL statement should you send to DoCmd.RunSQL?
The correct answer is INSERT INTO ... VALUES. An INSERT query adds a brand-new row to a table. An UPDATE query changes data in rows that already exist, which is definitely not what you want if the job is simply to add another record. SELECT queries retrieve or create data based on a query, but they are not the normal choice for adding one record from a form button.
Question 2: Suppose your INSERT statement includes a field named Commission, but the destination table does not actually have a field by that name. The form may have a text box named Commission, but that does not help the table. What fixes the problem?
The answer is to add the expected Commission field to the destination table, assuming Commission is data you really intend to store. The field list in an INSERT statement refers to fields in the table, not controls on your form. Access does not care that you have a nicely labeled text box on screen if there is nowhere in the table to put its value. Your form controls and table fields often have similar names, but they are not the same thing.
Question 3: Long SQL strings are often split across multiple VBA lines. You will usually see an ampersand followed by a space and underscore. What are those characters doing?
The ampersand concatenates, or joins, pieces of text together. The underscore is VBA's line-continuation character. It tells VBA, "I'm not done with this statement yet. Keep reading on the next line." This makes long SQL statements much easier to read and maintain. Without it, you end up with one giant ugly line of SQL that eventually wraps itself around the moon.
Question 4: An unbound text box can contain either a Null value or an empty string. If your validation code stops when IsNull(Me.Notes) is true, which reset value will make that guard work again on the next click?
The answer is Null, not an empty string. Setting the control to Me.Notes = Null gives it an actual Null value, so IsNull will return True later. Setting it to "" gives it a zero-length string instead. It may look blank on the screen either way, but VBA sees those as different values. This is one of those tiny details that can make validation seem broken when it is actually doing exactly what you told it to do.
Question 5: This is the field-order bug. EmployeeID starts with a value of 7 and Commission starts with a value of 50. The SQL statement is built using those values, and then EmployeeID is changed to 9 afterward. The INSERT statement's field list is ordered as Commission, EmployeeID, but the VALUES portion supplies EmployeeID first and Commission second. What gets inserted?
The result is Commission = 7 and EmployeeID = 50. SQL matches values to fields by position, not by the variable names you used while building the string. If your field list says (Commission, EmployeeID), then the first supplied value goes into Commission and the second goes into EmployeeID.
Also remember that changing EmployeeID after the SQL string has already been built does not change the SQL string retroactively. Once VBA has assembled that text, it is just text. The later value of 9 is irrelevant to the statement that was already created.
The safest habit is simple: when you write an INSERT statement, read the field list and the VALUES list side by side. Make sure each value is in the exact same position as its destination field. Your query can run perfectly without errors while putting the wrong information in the wrong columns, which is much worse than an error message. At least an error message has the decency to complain.
How did you do? If you missed one or two, no worries. These are exactly the kinds of details that separate SQL that merely runs from SQL that stores the right data. Watch the embedded video for the quiz walkthrough, and if you want more practice adding records with VBA and resetting forms for the next entry, check out the Microsoft Access Developer Level 2 material.
Calling Microsoft Access the "worst database" is certainly an attention-grabbing way to start a conversation. But the real story is a lot more interesting than a thumbnail slogan. Access became hugely successful because of timing, pricing, Office distribution, and, most importantly, because it helped people build complete business applications without needing a team of programmers and a six-month development schedule.
To judge Access fairly, you have to look at the world it entered, the tools it competed against, and what businesses actually needed their databases to do. Running a query quickly is nice. Entering orders, printing invoices, producing reports, and making changes when the boss says, "Can we add one more thing?" are nice too. In fact, those are usually the parts that pay the bills.
When Access arrived in the early 1990s, desktop database developers were already using capable products such as dBASE, FoxPro, Paradox, and Clipper. These were not toy programs. Businesses ran serious applications on them, and plenty of developers, including me, spent years working with those tools before Access entered the picture.
But the computer world was changing. DOS applications were largely text-based, keyboard-driven programs. They could be powerful, but they did not look or feel like the new Windows software that businesses were starting to expect. Suddenly, users wanted buttons, menus, mouse-driven screens, and applications that looked more like Word and Excel than a text terminal with boxes drawn on it.
The established database products had a challenge: move forward into Windows while continuing to support customers with existing DOS applications. Some old software could keep running as-is, of course. But converting an old DOS database into a good Windows application was not just a matter of slapping a mouse pointer on it. Forms, reports, code, menus, and user expectations all had to change.
Access did not have that particular baggage. It arrived as a Windows product. It was designed around the graphical interface that users were beginning to expect, and that gave it a real advantage at exactly the right moment.
Microsoft also made it easy to try. Access launched with a $99 introductory price, which was aggressive compared to many of the established database products. It did not stay at that price forever, but it lowered the barrier for people who were curious about this new database tool.
Then came the Office connection. Access was later included with Office Professional, alongside Word, Excel, and PowerPoint. If a company was already buying Microsoft Office, having a database tool included in the package was awfully convenient. That absolutely helped Access spread through offices everywhere.
That is how a lot of people discovered it. They already had Office installed, noticed this thing called Access, and thought, "Well, let's see what this does." Before long, somebody had built a contact list, an inventory tracker, an order-entry screen, or a report that replaced a pile of spreadsheets.
But distribution alone does not explain why people kept using Access. A product can be bundled with every computer in the world, but if it is useless, people eventually stop opening it. Access stuck around because it gave users an unusually practical set of tools in one place.
You could create tables to store data, define relationships between those tables, build queries to find and calculate information, design forms for data entry, create reports for printing, and add automation when the application needed to do more. That combination matters.
Consider a simple order system. You might have one table for customers and another for orders. Each order is connected to a customer, so the employee does not have to type the customer's name, address, phone number, and other details over and over again for every sale. That is basic relational database design, and it is still good design today.
Next, you need queries that pull together the information you need. Maybe you want to see this week's orders, calculate totals, identify unpaid invoices, or find customers who have not purchased anything recently. The query is the part that asks useful questions of the data.
But the business cannot stop at the query window. Somebody has to enter the order. Somebody needs an invoice. The owner wants a monthly sales report. Staff members need buttons that open the right screen or print the right document without making them memorize a dozen steps.
This is where Access earned its place. It was not just a database engine sitting in the background. It was a development environment that let someone build the whole application: tables, queries, forms, reports, macros, and eventually VBA programming when needed.
FoxPro, for example, deserved its reputation for speed and strong data processing. dBASE had an important language and a large developer community. Paradox was a capable development tool in its own right. Clipper was associated with the dBASE language and allowed developers to compile applications into executable programs. These tools were not interchangeable, and each had strengths.
However, saying that one product could process certain queries faster does not automatically make it the better choice for every business application. Better at what? Faster is important, certainly. Nobody enjoys clicking a button and waiting long enough to make coffee. But development time, reporting, usability, maintenance, and the ability to make changes all count too.
If one tool gives you a slightly faster query but takes considerably more work to produce an order-entry screen, invoice, and management report, that is a meaningful tradeoff. The employee entering orders on Monday morning generally does not care which database engine won a benchmark ten years ago. They care whether the form is easy to use and whether the invoice prints correctly.
Access also made it possible to start simply. A beginner could use the built-in designers to create a table, make a query, and put together a form. As the application grew, that same developer could add more sophisticated queries, automation, VBA code, and custom user interfaces. You did not have to begin as a full-time software engineer to solve a useful business problem.
That was a major part of Access's appeal. It shortened the distance between "I need to track this information" and "Here is a working application people can use." For small businesses, departments, consultants, and internal developers, that was a very big deal.
There is also a historical detail worth keeping straight: Rushmore. Rushmore was FoxPro's query optimization technology. In plain English, it helped the database locate records more efficiently when running certain queries. Microsoft acquired Fox Software in 1992, but Rushmore was not part of the original Access 1.0 story.
Access became available in late 1992. Contemporary coverage of Access 2.0, released in 1994, described the addition of FoxPro's Rushmore technology to improve set-query performance over Access 1.1. That means Rushmore was an important improvement in Access 2.0, not a feature that was already present in the original Access release.
That may sound like a small detail, but version history matters. If you are comparing Access 1.0 to competing products, you should compare what actually existed at the time. Access improved significantly as it developed, just as its competitors did.
The same kind of care is needed when discussing FoxPro's eventual discontinuation. Microsoft bought Fox in 1992, but FoxPro did not vanish immediately afterward. Visual FoxPro 9.0 was released in 2004, and extended support continued until January 2015. That is a long product life, not a quick trip to the software graveyard.
It is reasonable to say that Microsoft eventually consolidated products and technologies. It is also fair to recognize that some FoxPro developers were disappointed by the decision. But claiming that Microsoft bought FoxPro simply to destroy it and make Access dominant is a statement about motive, and that requires more evidence than a timeline alone provides.
Today, the conversation often gets distorted in a different direction: "Access is obsolete," or "Access cannot handle real databases." That is just as lazy as calling it the worst database. Access is not the right solution for every situation, and it never was.
If you have massive amounts of data, large numbers of concurrent users, strict enterprise security requirements, web-based users, or applications spread across multiple locations, you may need a server database such as SQL Server. That is not a failure of Access. It is simply choosing the right tool for the job.
And it does not have to be Access versus SQL Server. One of the most useful setups is Access as the front end and SQL Server as the back end. SQL Server stores and protects the data, while Access provides familiar forms, reports, queries, and user interfaces for the people doing the work.
In other words, an employee can still use an Access form to enter an order, print an invoice, or run a report, while SQL Server handles the underlying tables. That can be an excellent solution when properly designed. Moving tables to SQL Server does not magically fix bad queries, poor form design, or weak security planning, of course. There is no magic button labeled "Make It Enterprise." You still have to build the application correctly.
The important point is that Access remains useful when you understand where it fits. It is especially strong for desktop business applications, internal tools, rapid development, reporting, and front-end applications connected to more powerful data platforms.
Popularity does not prove that Access was technically superior to every competitor in every category. Microsoft had enormous advantages in Windows, pricing, marketing, and Office distribution. Those facts should be part of the story.
But technical comparisons should not be reduced to a single number on a speed test either. A database application is more than a query engine. It is the data structure, the interface, the reports, the workflow, the maintenance burden, and the ability to adapt when the business changes its mind. And businesses always change their minds. Usually on Friday afternoon.
Access dominated desktop databases because it arrived at the right time, was easy for people to obtain, and gave users a practical way to build complete applications. That is a much more accurate explanation than calling it the worst database.
If you are deciding whether Access is worth learning or using, start with the requirements of your own project. Consider the size of the data, the number of users, your security needs, where the application will run, and how quickly you need to build and maintain it. Then pick the tools that make sense for that job.
You can watch the embedded video for the full discussion, including more historical context about Access, FoxPro, dBASE, Paradox, Clipper, Rushmore, and the role Office played in Access's success.
Once you start building reusable tools in Microsoft Access, copying forms, modules, and functions from one database to another gets old fast. It is also a great way to end up with six slightly different versions of the same code, none of which you are completely sure is the right one. A shared library database solves that problem nicely, but it creates a new question: how do you safely maintain, protect, and distribute that library?
That is the focus of Access Developer Level 64. This class continues the shared library database system begun in Developer 63 and takes it from a useful development idea to something much closer to a professional deployment setup. You will learn how to keep reusable tools in one master library, make them available to multiple Access applications, and package the finished library as a protected ACCDE file.
A shared library is especially useful when you have common routines that belong in more than one application. Maybe you have standard validation functions, utility code, report helpers, import and export tools, or custom dialog boxes. Instead of maintaining copies of those objects in every database, you can place them in one library database and reference that library from your other applications.
One of the practical projects in this class is building reusable custom dialog boxes. These are forms that can be opened from another database, ask the user a question, and return the answer to the application that called them. That may sound simple, but once you understand the pattern, you can create all kinds of shared interface tools: confirmation prompts, selection dialogs, data-entry helpers, message windows, and more.
The class also addresses a few of the questions that naturally come up once you begin using library databases. What kinds of objects belong in the library? Can queries be shared? When does it make sense to move a form, report, query, or code module into the library instead of leaving it in the front-end database? And how do you distribute the library to users without handing them a file full of editable VBA source code?
That last point is where ACCDE files come in. An ACCDE is the compiled version of an Access database. It helps protect your VBA source code, prevents design changes to forms and reports, and reduces the chance that someone will accidentally "fix" something that was working perfectly five minutes earlier. If your shared library is being used by multiple databases, compiling it before distribution is generally a very good idea.
Of course, manually producing an ACCDE every time you make a small change is tedious. You have to compile the project, create the ACCDE, deal with the existing file, make sure the current version is preserved, and then reopen your master database. It is not difficult, but it is exactly the kind of repetitive process that computers should handle for us. Otherwise, why are we programming?
That is why this class builds a separate automatic ACCDE builder utility. The goal is a one-button process that compiles the library, preserves the prior version, replaces the old compiled file, and returns you to the master library database when the job is finished. It is a small utility with a big payoff if you update your library regularly.
This is not just about saving a few clicks. Having a consistent build process makes your library easier to maintain and safer to deploy. You know which file is the editable master, which file is the compiled version that users should reference, and where the previous version went if you ever need to roll back. That sort of organization becomes increasingly important as your Access applications grow beyond a single database sitting on your desktop.
Developer Level 64 is designed for Access developers who are ready to stop treating every database as an isolated project. If you have reusable code and tools that you want to share across applications, this material will show you how to build a more maintainable library system and automate one of the more annoying parts of keeping it current.
Watch the embedded video for an overview of the class, then visit the course page for the complete training and full implementation details. By the end, you will have a solid approach for writing your code once, using it across multiple Access databases, protecting it in an ACCDE, and rebuilding that ACCDE without doing the same manual dance every single time.
One of those little Access quirks that can make you question your sanity is when a function works perfectly in a query, form, report, or VBA procedure, but suddenly gets rejected when you put it in a table-level validation rule. The classic example is Nz. You know it works. Access knows it works. Yet the table validation property looks at it and says, "Unknown function." Thanks, Access.
The important thing to understand is that table-level validation rules do not use the exact same expression environment as queries, forms, reports, and VBA. They support many common expressions, but not every Access function is available there. So when Access complains that Nz is unknown in a validation expression, the problem usually is not spelling, syntax, broken references, or anything else you did wrong. It is simply an unsupported function in that particular context.
Nz is normally used to replace a Null value with something more useful. For example, in a query you might use it to treat a missing amount as zero. In a form control, you might use it so the user sees a blank string instead of Null. It is one of the handiest functions in Access, and I use it constantly.
But if you try to use something like Nz([Amount],0) in a table-level validation rule, Access can reject it with an "unknown function" message. That error is misleading because Nz is not unknown to Access in general. It is unknown to the validation-rule engine.
So what do you use instead? For table validation rules, rely on the expressions that Access does allow in that property. The most useful tools for dealing with missing values are Is Null and IIf, depending on the rule you are trying to enforce.
For example, suppose an Amount field is optional, but if a user enters a value, it cannot be negative. A table-level validation rule can allow either a missing value or a value greater than or equal to zero. The basic logic is: the field is Null or the value is non-negative.
That distinction matters because Null is not zero. A Null means "no value has been entered." Zero is an actual value. Sometimes treating Null as zero is exactly what you want, especially for calculations. Other times, it can hide missing data that ought to remain missing. Before automatically converting Null to zero, make sure that zero genuinely means the same thing for your business rules.
If your validation depends on more than one field, table-level validation rules can still be useful. For example, you might require an end date to be later than a start date, unless the end date has not been entered yet. In that situation, test for Null explicitly before applying the comparison. Otherwise, Null can cause the validation expression to behave in ways that are not immediately obvious.
This is also a good reason to keep table-level validation rules reasonably simple. They are excellent for protecting the data regardless of how it gets entered: through a form, directly in the table, through an append query, or from some other process. That is a big advantage. A form's validation code only runs when someone uses that form. Table rules help protect the data at the source.
On the other hand, if the validation starts getting complicated, you may be better off handling the user-facing part in a form's Before Update event. There, you have much more flexibility, better error messages, and access to the full range of VBA functions. Just remember that form-level code is not a substitute for table-level protection when the data can be edited through other paths.
The practical takeaway is simple: do not copy an expression from a query or form into a table validation rule and assume every function will be supported. If Nz gets rejected, you are not crazy, and it does not mean that your database is broken. Rewrite the rule using explicit Null checks such as Is Null, along with the comparison logic the rule needs.
Watch the embedded video for the full walkthrough and demonstration of this odd little Access limitation. Once you know table validation rules have their own expression restrictions, this particular error becomes much less mysterious.
