The Microsoft Access Security Mistake That People Still Make - QQ 94

Ready for another batch of Microsoft Access brain food? This week's Quick Queries is loaded with useful (and sometimes cautionary) tales from the wild world of Access. Whether you are wrangling database security, opening PDFs from a form, troubleshooting quirky installs, arguing with Task Scheduler, or just debating whether Access is more than a 1990s relic, there is plenty in here for you - along with a few tips on taming AI that occasionally thinks it's smarter than it actually is.

If you have ever locked down your Access interface - ribbon hidden, shift key disabled, startup options frozen - only to find users still poking around your tables, well, you are not alone. One of the most common security mistakes with Access is thinking you can make it truly bulletproof with these tricks. Here's the deal: hiding tables and disabling shortcuts is great for keeping the honest folks honest, but if your data is really sensitive and someone is determined, Access just is not designed to stop a skilled hacker. If you must keep out the bad guys, bite the bullet and move your data to SQL Server. Access then works wonderfully as a front end, and you can sleep a bit easier at night.

Got a question about opening PDFs from an Access form? Absolutely doable! Instead of cramming PDFs into an image control, just build your file path dynamically from things like the date, supplier, or an ID. Then use VBA's FollowHyperlink to launch the PDF with whatever reader Windows likes best. Fast, clean, no wrestling with embedded files, and your database stays lean. There is a short video that demonstrates this step by step - link down below the video, if you want the nitty gritty details.

I had someone recently wrestling with running Access over a network - could not open their database using an IP address path, and Access would not trust the location. Welcome to the sometimes-dark art of network paths. Access really prefers mapped drives or what we call UNC paths (think double backslashes and folder names, not raw IP strings). Opening databases directly over the Internet? That is like buying a ticket for "Corruption Island." Unless you want a database that comes with free sadness, just do not do it. Keep it local, wired, and split into front and back end if you value your data's health.

The age-old question: Is Access still useful? Short answer - yes. Sure, it is a fantastic learning platform, like training wheels for SQL newbies, but that does not mean you toss it once you have learned. I have clients still running systems I built decades ago, and for small and medium businesses, Access is perfect for line-of-business apps, inventory, CRM, reporting, and more. Would I try to run Amazon on it? Only if I liked living dangerously. But for most businesses? Access is still a workhorse.

Ever get weird errors after installing a new version of Office or Access? Old versions can tangle things up royally. The classic trick is to uninstall every stale version before putting in a new one. Those "box" versions (2010, 2016, etc.) do not always play nice together. Microsoft 365 is a bit more civil, but even then - one version at a time, thank you very much. Saves a ton of headaches.

And on to the "should I store images and PDFs inside Access?" discussion. Technically, you can - but your database will bloat faster than you can blink. Attachments and OLE objects sound fun until you hit that 2GB wall and performance grinds to a halt. The pro move is storing your files in a folder, then keeping just the file paths in your table. Use VBA to link back and forth as needed. Faster, cleaner, and way easier to manage long-term.

Quick shout to everyone trying out Windows Task Scheduler for Access automation - great tool for running batch jobs, backups, or sending mail at odd hours. If you are just starting with VBA, I always say: start with the basics and build up. I have got intro videos and developer courses for every level, so take it step by step and do not fall for the temptation to shortcut your learning with AI that is prone to a little creative hallucination. Use the bots to speed up boilerplate code if you like, but always double-check their work. Treat them like eager junior devs who sometimes reinvent the wheel - and try to attach it to your database backwards.

Lastly, for anyone using image subfolders to display pictures in forms - yes, the same trick works for reports too. Just make sure your paths and file names are spot-on. Access is picky, and one stray typo can leave your report looking mighty empty.

That is about it for this week's Quick Queries. We covered everything from Access security reality checks, smarter ways to handle documents, AI code skepticism, troubleshooting wonky Office installs, and my all-time favorite analogy: compact and repair is pretty much "defrag" for your database. For full walkthroughs and plenty more, hit the embedded video above.

Live long and prosper,
RR

Will Your Windows 11 PC Stop Working On June 24th? Will Microsoft Access, Word, Excel Still Run?

If you've been online lately, you've probably stumbled across some dramatic headlines warning that your Windows 11 PC is going to fall over and die come June 24th. Supposedly, Microsoft Access, Word, Excel, and maybe your dog are all going to be affected. Let's take a step back, breathe, and actually look at what's going on, minus the panic-inducing hype.

The core of the anxiety comes from some technical changes Microsoft is making behind the scenes - specifically about something called Secure Boot and expiring security certificates. It sounds scary, but for 99 percent of people, this is truly a non-event. Our computers are not about to self-destruct; Access isn't packing its bags and moving out, and Word and Excel will still happily open your grocery list.

The heart of the whole situation is that Microsoft set up certain Secure Boot certificates back in 2011, and wouldn't you know it, these things are expiring in 2026. The internet latched onto this fact and started spinning up end-of-days scenarios for Windows users. Here's the simple truth: Microsoft is already rolling out updates to replace these expiring certificates, and most users won't even notice anything changing.

So what exactly is Secure Boot? Think of it as the bouncer at the Windows Club, checking ID at the door before your operating system is even allowed entry. Its main purpose is to stop nasty stuff from accessing your computer before Windows even has a chance to fight back. It is not responsible for whether your Office programs (Access, Word, Excel, the usual suspects) run or not. If your PC boots into Windows today, those apps will continue trucking along just fine.

Now, what should you do? The short answer is: likely nothing. If you're curious, you can quickly check your Secure Boot status. Just hit Start, type Windows Security, open Device Security, and take a look at Secure Boot. Green checkmark? Pat yourself on the back, you're good. Yellow? Maybe Windows is still working through an update - just give it a little time. Red? That could mean a firmware update is needed, and if that's the case, head over to your manufacturer's official support site. And I mean official - let's not go downloading random BIOS updates from the wild west of the internet. For most of us, enabling Windows Updates and letting Microsoft do their thing is all that's required.

Here's the real deal: don't create a problem that doesn't exist. Don't rush into your computer's BIOS to start flipping switches you don't understand just because some YouTuber said the sky is falling. Secure Boot being marked as unsupported isn't a sign of imminent doom. If your Windows 11 PC is running just fine and all your software is happy, leave it alone. No need to be a hero or start a weekend project fixing what isn't broken.

As always, keep your system up-to-date, don't panic, and maybe spend a little less time reading sensational headlines. June 24th is not the Windows Y2K. Your Access databases and Office documents will be there in the morning. The best thing you can do is relax, stay updated, and know where your towel is (bonus points if you caught the reference).

If you want to see more of these kinds of breakdowns, or if the scare-mongering headlines had you worried for a second, let me know in the comments. And for those wanting to go deeper, there's a full beginner Windows course available for free on my website and YouTube channel - level 2 is just a buck if you're hungry for more.

Stay calm, stay smart, and let Microsoft do the hard work for you. Your PC and Office apps aren't going anywhere on June 24th. Watch the video above for a deeper dive if you're still curious!

Live long and prosper,
RR

Windows Suddenly Sluggish After Update? Check This First

You know that feeling when you finish a Windows update and suddenly your computer starts acting like it's trudging through molasses? Not outright broken, not blue-screening - just strangely slow in a way that's hard to pin down. It's one of the most frustrating situations for any PC user because if something crashes, at least you know where to start, but when everything is just a little bit off? That sends you straight down a rabbit hole of troubleshooting, and nobody's got time for that first thing on a Monday morning.

Here's the thing: sometimes it isn't a failing hard drive, a bad batch of Windows code, or yet another driver nightmare. In fact, after one routine update on my Lenovo Legion laptop (Windows 11, for the record), I ended up spending hours puzzling over the performance drop - apps lagging and just a general stickiness whenever I tried to do anything. And get this: it turned out to be one little Windows power setting that quietly changed in the background.

So let's talk about what you should check first if your PC is suddenly dragging its feet after a Windows update. First stop, as always, is Task Manager. Open it up and look for anything hogging your CPU, eating RAM, or thrashing your disk. Sometimes, updates like to keep working for a bit even after a reboot; search indexing and update processes can slow things down for a while. If everything looks normal there and the sluggishness isn't clearing up, it might be time to dig deeper.

Now, a big suspect after updates is always the graphics driver. Microsoft and GPU drivers are like that couple who keep breaking up but never really move on. If Windows gets clever and swaps out your graphics driver, things might look okay but feel off. A fresh Nvidia or AMD driver update sometimes does the trick - or at least helps a little.

If updates and drivers both look fine, you can check with tools like SFC and DISM. These handy command-line options can repair Windows system files that might have been jostled during the update. For those interested, I've got videos on SFC and DISM - you can always ask for more details if you want to dive in.

But here's where it gets sneaky: sometimes, Windows will flip your system into a lower power mode behind your back. On my machine, after the update, it snuck me into "quiet mode." Manufacturers call this all sorts of things - quiet mode, eco mode, battery saver, whisper mode, save-the-penguins mode - but what it really does is throttle back your CPU and GPU to keep things cool and quiet. That's great if you're working at a coffee shop, not so great if you're running your machine like the workhorse it's meant to be.

The solution? Go straight to your Power Options in Control Panel. Yes, I know Microsoft has been trying to hide Control Panel for years, but it's still where all the advanced good stuff lives. Click Start and type "Control Panel," head into Hardware and Sound, then Power Options. Look for any modes with names like "Performance," "High Performance," "Ultimate Performance," or whatever your manufacturer calls their top speed option. Turn off any low-power modes if you want that instant responsiveness back.

If you want to dig even deeper, check "Change plan settings" and then "Advanced power settings." Set your minimum processor state to 100 percent when plugged in if you want your CPU to always run at full throttle. Just be careful: the advanced options are powerful, and changing things randomly is a bit like flipping switches on the Starship Enterprise just to see what happens. If you want a nerdy deep dive on these power tweaks, let me know - a future video could definitely cover it.

Remember, different PC brands might layer their own fancy software over Windows power options - Lenovo, Dell, ASUS, MSI, Alienware, you name it. I can't cover every custom app out there (unless anyone wants to send me a free gaming PC, in which case I humbly accept donations), but the principle is the same: check for any performance-bottlenecking modes and shut them down if your machine is always plugged in and needs to work hard.

One small rant before we wrap up: always do Windows and Office updates on your own schedule, not theirs. Update regularly, but never let your PC decide to do it the night before a big project. I like to handle major updates when I have downtime and can troubleshoot if something goes sideways. And yes, if folks want a full walkthrough on permanently disabling automatic Windows updates (because Microsoft likes to make this harder than it should be), just say the word.

Bottom line: if Windows suddenly slows down after an update, check your power plan settings before you panic, reinstall drivers, or start eyeing your backup drive. The fix could literally be just a few clicks away, saving you hours of hair-pulling troubleshooting.

If you want all the juicy step-by-step screenshots and tricks, check out the full video embedded above. And remember, you can always find my complete free Windows Beginner Level One course over on my site or YouTube channel, plus more advanced stuff for those ready to go down the Windows rabbit hole.

Live long and prosper,
RR

User-Controlled Display Order, Sorting, and Renumbering in Microsoft Access - Fitness 76

Letting users control the order of items in a Microsoft Access list can be a real game-changer. Instead of Access deciding how things are sorted, why not let users tweak and organize to their hearts' content? Whether you're building a fitness database like in my example or wrangling appointments, task lists, or products, the techniques I'm about to talk through will fit right in.

Most Access tables (and their forms) default to whatever order the database feels like. That is rarely what your users actually want. If they want "chest" before "quads" or "calves" to start the day for some reason, that should be easy. The trick is to set up a custom display order field - something the user can directly control - and then wire up Access to handle the sorting and renumbering for them. No more random jumps or headaches when you try to move stuff around.

The first thing to do: add a SortOrder (or DisplayOrder, if you prefer fancy names) field to your detail table. Here's a pro tip - make this a Double, not an Integer. Why? Moving records means you'll sometimes want to slide something between two numbers. If everything's just 1, 2, 3, 4, what happens when you want to stick a new item between 2 and 3? With a Double, toss a 2.5 in there, then renumber later for that clean, neat order. Plus, users can type in whatever they want for fine control, and it will all smooth out with a quick re-sort.

While we're talking tables, ditch zero as the default display order. Make it Null - trust me, makes life a little easier because you can catch and fix anything that slips through. Also, think about defaults for other fields: nobody goes to the gym and does zero sets, at least not on purpose (or unless you subscribe to my patented "sit-around-and-watch-everyone-else" method).

Once you've got the SortOrder field, stick it on your form so users can see and edit it. Doesn't matter if it's fitness routines, inventory products, or whatever else - same concept. Add the field to your subform, tidy up the tab order, and make it look like someone cares about UI design, at least a little bit. Align things left and leave enough room for your numbers. And remember, if someone needs three digits for sets, they're either superhuman or accidentally pounding keys.

Now for the automation. When someone adds a new item, you want Access to automatically stick it at the end of the list. The logic is: look up the highest current SortOrder for just this group or routine, add one, and assign that as the new default. This keeps new stuff nicely appended, and the user can adjust from there. This is typically done in the Before Insert event of your form. Writing code for this is straightforward - a little DMax to get the current highest, and boom, you're set. (If you want to see the VBA, check the video below; I do walkthroughs and show all the code details there, so you aren't stuck guessing.)

But what happens when users actually want to change order - move something up or down in the list? Here's where Doubles shine. If you want to move item 3 above 2, just pop in 1.5. Of course, you don't want to leave the database full of fractional weirdness forever, so after any SortOrder update, run a quick renumber. The code loops through everything in the newly sorted order and reassigns 1, 2, 3, and so on.

The main things to remember when renumbering:

• Make sure the current record is saved (Me.Dirty = False handles that).
• Open a recordset sorted by SortOrder for just the current group (like the items under a single routine).
• Loop through and update SortOrder fields with a neat counter, moving from 1 upward.
• Requery the form to show the new order immediately.

Bonus tip: be careful with the form's Order By property. If you want things always sorted right, you can set this either in the form properties or, better yet, directly in the form's record source SQL. It's easy to mess this up, especially if you manually change things, so pick a method and stick with it. I show both approaches in the demo video below.

Just like that, users can re-order exercises (or widgets, or appointments) to their liking. Add a new item? It appears at the end. Want to move your favorite to the top? Just change that SortOrder field. Want the exact same trick for products, task priorities, or literally any other ordered list? It all works the same way.

Want a little more? In the next part, I go a step further and show how to add up/down buttons so users don't even have to type numbers - just click, and the items shift accordingly.

If you want all the code details, walkthroughs, and some snarky commentary, check out the embedded video. As always, feel free to comment below with your feedback and war stories, or what you'd like to see next.

Live long and prosper,
RR

Are You There? Automatically Log Users Out After Inactivity in Microsoft Access, Part 4

If you have ever needed a way to make sure your Microsoft Access users are actually there at their computers, not just ignoring your database window while they answer emails or binge YouTube, I have a pretty handy trick for you. This builds on my earlier tips about logging users out after inactivity, but now we are cranking it up a notch: we are getting Windows itself to rat out your idle users. No more letting them game the system by just minimizing Access and pretending to be gone while they are secretly still very much present.

So, here is the problem with traditional inactivity tracking in Access: those timer-based approaches work well if your users are actively doing stuff inside your forms, clicking, typing, tabbing around your database. But Access has no idea if someone's actually still at their workstation or just alt-tabbed away. Some clever users might keep Access open in the background, then waste half an hour in Excel, Outlook, or, ironically, watching AccessLearningZone videos. From Access's perspective, it looks like they are just idle. Technically, they are, but in reality, their butts are still firmly in their swivel chairs.

This is where Windows API calls come to the rescue. Windows is always keeping score on when the computer was last touched, whether it is a key press, a mouse wiggle, or something else. With a tiny bit of clever VBA, you can ask Windows directly: "Hey, how many seconds since the user did literally anything?" The answer covers all apps, not just Access. Now you have a way to see if they are truly away from the computer, not just your application.

Now, before anyone panics about "Windows API" code, don't. Using API calls in VBA is a lot less scary than it sounds. You do not need to know how Windows works under the hood, just which buttons to push. All it takes is a little function that does all the grunt work. If you want the full step-by-step code walk-through, I cover it in the video, and Gold members will find it in the code vault.

Here's the big picture: the function - let's call it GetIdleSeconds - checks with Windows, asks for the timestamp of the last key press or mouse move, subtracts that from the current system time, and hands you back how many seconds the PC has been idle. If the call fails for some reason, you get a negative number, so you can check for that too if you want to be extra careful.

You do not have to understand the nitty-gritty. In my own demo, I dropped the function into a module (I usually name mine something like "modIdle" so I know what it's for), and set up a one-second timer in my main menu form for testing. When I touch the mouse or a key, the idle count resets to zero - no matter what program I am in. Even if I am typing away in Notepad, not Access, my database instantly knows.

Now, here's my recommendation if you want to put this into action: keep using your usual form-based timer or event systems to track user actions inside Access for the main timer. That way, you do not get your main screen constantly jumping back into focus while your user is working in the VBA editor or another app. But, when it comes to actually making the decision to log someone out, use GetIdleSeconds as your checkmate. Make sure the user is not only inactive in Access, but also idle on the whole PC. Only then drop the hammer and close them out. That way, you avoid kicking people off for doing genuine work in other apps - and you close the loophole of someone just walking away without locking their computer.

You could even take it further: if you know the user has been away for a while, you could not only shut down their Access session but also lock the whole workstation (that is also possible - maybe a topic for a future video if enough folks are interested).

Bottom line: this little Windows API trick gives you the ultimate "Are you actually there?" test. Traditional Access tricks tell you if someone's using your database; the API tells you if they are still at the computer at all. Between the two, there is nowhere left to hide. If you want to see this in action and get the nitty-gritty implementation details, check out the video above.

Let me know if you will use this approach, or if you have any other favorite tricks for managing user sessions and idle timeouts. Share in the comments, and as always, you can find the extended implementation and walkthrough in the full video.

Live long and prosper,
RR

How To List Recently Changed Objects in Microsoft Access (Forms, Queries, Reports & Tables)

Ever sit down in front of your Microsoft Access database after a long weekend (or maybe a vacation) and draw a complete blank about what you were working on last time? Or maybe you managed to restore an old backup but now have no clue which tables, forms, or queries you modified since then. Trust me, you are not alone. Keeping track of design changes in Access can feel like hunting for your keys: you know you left them somewhere, you just have no idea where.

There are plenty of situations where knowing which objects have been changed recently comes in handy. Maybe you are troubleshooting a sudden issue, recovering after a backup, or need to convince your boss that yes, you did make progress last week. Wouldn't it be nice if Access just had a big bright button that said: "Show me everything I changed?" Well, not quite... but it turns out Access does track some details that can help, if you know where to look.

So here's the scoop: Access secretly stores created and last updated dates for every object in your database. That includes tables, forms, queries, reports, and so on. These little details sit in a special, hidden system table called MSysObjects. You just have to know how to ask for them. Before you go poking around, be warned: do not modify anything in those system tables unless you want some exciting new error messages in your life.

To get to these details, you first need to make sure Access is showing system objects. Quick tip: right-click in your Navigation Pane, go into Navigation Options, and check the boxes for showing hidden and system objects. Once you do that, you will see a bunch of tables named MSys... popping up. The one you want is MSysObjects. If you open it up (just to peek, not to touch!), you will see columns like Name, Type, DateCreate, and DateUpdate. That's your motherlode of object details.

Now, you could scroll through all that technical noise by hand, but we are smarter than that. Time for a little query magic. Use the Access Query Designer to create a new SQL query that selects Name, Type, DateCreate, and DateUpdate from MSysObjects. You will want to filter out any system objects (all those that start with "MSys") and probably want it to show most recent updates first by sorting on DateUpdate descending. If you are comfortable with SQL, it looks something like this:

SELECT Name, Type, DateCreate, DateUpdate FROM MSysObjects WHERE Left(Name,4) <> "MSys" ORDER BY DateUpdate DESC;

If you are not familiar with SQL, the design grid view in Access will work just fine too. Tweak your criteria to exclude temporary objects (those that start with a tilde), and you will have a tidy list of what you have changed and when.

Now, a quick word about the Type column. Access uses numbers to represent different object types. For example, queries are 5, tables are 1, forms are -32768 (I'm not kidding), and so on. Microsoft does not officially document all of them, but most are easy to pick out based on your own naming conventions. You do not need to memorize the codes, but it does help to know what you are looking at.

This technique is awesome for tracking design edits to tables, queries, forms, and reports. Make a change, save your object, and bam - the DateUpdate field updates. So if your goal is just to figure out what objects you have been tinkering with recently, this query is your best friend. Add a new column, nudge a button a pixel, or update a query, and you will see it right at the top of the results.

But, and there is always a "but," there is a little catch with VBA code changes. When you change the code behind a form (the form's module) and save, the DateUpdate usually refreshes - most of the time. But if you edit a standard module (like a global module), for reasons known only to the Access gods, sometimes this does not update. I have seen it skip the update entirely, especially with standalone modules.

So if you do a lot of VBA work, be aware: this trick gives you a quick and dirty answer, not a full accounting. It is great for tracking forms, reports, tables, and query design changes, but don't rely on it for every line of VBA code you tweak. If you need to track VBA module changes specifically, you will want to step things up with a little more advanced VBA scripting to build your own audit table. That takes a bit more work - and I cover the full process in the extended cut for members, where you can see how to use the Access object model to get a more accurate, complete inventory of changes.

Bottom line: if you ever find yourself wondering, "What have I actually changed lately in this database?" a simple query against MSysObjects is a fast and surprisingly effective way to get the answer, at least for most Access users. Next time you come back from your break, or need to check your design history after restoring from backup, give it a try. For hardcore developers who live and breathe VBA, check out the members-only video for that next-level technique.

Got your own Access mystery or story about lost work and heroic recoveries? Drop a comment below and let me know. The video up above has the step-by-step demonstration if you want to see this technique in action.

Live long and prosper,
RR

How To Build A Simple Query In Microsoft Access

Need to pull up just the right set of records from your Access database without scrolling for hours or repeatedly fishing through dozens of rows? This is where queries step in to save your sanity. If you're working with customers, orders, or any data you regularly sift through, learning how to build a simple query in Microsoft Access is one of those things you'll wish you picked up sooner.

So, what exactly is a query? In Access, your tables are where data physically lives - think of tables as your database's jam-packed filing cabinets containing all your vital details like customer info, orders, products, you name it. But queries don't actually store data themselves. Instead, a query is basically you asking your database a focused question. Maybe you want to see every customer from Florida. Or only the ones who haven't placed an order in six months. A query lets you filter out the noise and get exactly the rows you want, quickly and reliably.

Running a query is like having a saved search - you set it up once, and any time you want those results, just run the query again. Less clicking, less filtering, more getting actual work done. If you're new and you haven't even created tables yet, I highly recommend checking out my Beginner Level 1 course first, because things make a whole lot more sense once you nail down tables. Links for that and my free TechHelp template database are down below.

Let's walk through a practical scenario. Say you're often looking for all customers from Florida, and you're tired of manually filtering every single time. Instead, you want a reusable tool. Here's how you build it: fire up Access, hit Create, and then Query Design. Choose your table - in this case, let's say "CustomerT." Then pick the fields you want to see in your results, like CustomerID, FirstName, LastName, City, or State. Double-click each field to drop them into your query grid.

Now, the magic happens with criteria. Click under the State column in the criteria row and enter "FL" (with double quotes). That tells Access to only show records where the state is Florida. Run the query - it's the little exclamation mark button - and boom: only the Florida folks. This is what a simple criteria filter looks like. Back in Design View, you can tweak this any time.

A quick pro tip: when you save your query (Ctrl+S is your friend), use a naming convention. I like ending tables with a T, queries with a Q, forms with an F, and so on. Spaces in names might look pretty, but they'll trip you up later if you start doing more advanced stuff, especially with VBA or SQL. Just trust me on this one.

From here on out, to get your trusty list of Florida customers, all you do is double-click the query and run it. No more wrestling with filters every single time - you just open, run, and you're set. That's why queries are one of my favorite Access features; build them once, use them forever.

But here's where beginners trip up: queries don't actually store copies of your data. The live data still sits in your table. So if you edit a record in your query, you're editing the real thing. If you delete a record, it's gone from the table. The query only stores the instructions - the "recipe," not the "soup." So double-check before you accidentally nuke a record you actually wanted to keep! Think of query results as different lenses for the same data, not a detached snapshot.

If you want to go beyond this and get into more advanced stuff like complex criteria, AND-OR logic (for the pros who live dangerously), or parameter queries that prompt users to enter values each time (great for on-the-fly searches), I have separate videos just on those topics. With parameter queries, for example, you don't have to hard-code "FL" - you can prompt the user for any state when running the query… neat little feature, super useful.

And if you're reading this without having watched my Access Beginner Level 1 course, what are you waiting for? It's free, it's comprehensive, and it'll put you light years ahead when it comes to confidently working with Access databases.

So that's the rundown for building a simple query in Microsoft Access. If you have questions, comments, or just want to share your own query-war stories, post them down below. And remember, you can always watch the embedded video up top for a complete click-by-click walkthrough.

Live long and prosper,
RR