Microsoft Access Database Normalization Without the Computer Science Degree - QQ 97

If you have ever felt overwhelmed by all the textbook rules about database normalization - first normal form, second normal form, six millionth normal form - you are not alone. This week, let's clear the fog around normalization and chat about what really matters when building solid Microsoft Access databases, no degree in computer science required. Plus, it was quite the week in the world of Access: forum questions, surprising little usability changes, SQL Server debates, troubleshooting rabbit holes, and the old Access vs. web debate all made an appearance (and yes, a tech story or two snuck in). So grab your cup of coffee, and let's dive into the latest round of interesting problems and shop talk from the Access community.

I'll start with the topic people love to complicate: database normalization. Everyone loves to toss around academic buzzwords, but honestly, for 95 percent of everyday Access developers, you do not need to memorize formal definitions. Let's boil it down to what actually matters when you're building tables.

First rule of building tables: every table should represent only one thing. Customers are customers, orders are orders, products are products - don't mix and match. Keep your customer data (name, address, and so on) in one table, and relate everything else back to it as needed. Which leads to the next classic mistake: duplicating information. If you catch yourself copying customer info onto every order or invoice, it is time to rethink those relationships. Store it once and relate, do not repeat.

If you find yourself adding "phone number 1," "phone number 2," and so on into a table, that's a clear sign you need related tables - a table for phone numbers, email addresses, or whatever categories keep growing. Personally, if you get past three of anything, it is time to split them out. This is especially true if you come from the world of Excel, where copying data everywhere is standard. Proper database design with relationships is what makes Access powerful in the first place - everything else is just icing.

For the perfectionists out there, yes, sometimes you break the rules on purpose. Want to keep a snapshot of a shipping address on each order? That's a valid reason to denormalize - there are always exceptions, but most people are better off learning the basics and playing by them until there's a good reason not to.

Moving on, I spotted a subtle but sweet little UI change in the latest Microsoft 365 subscription builds of Access: when you copy a table, it now names it "TableName - Copy" instead of "Copy of TableName." Not a big deal, but these tiny quality-of-life improvements make my day. Consistency with Windows file naming is always welcome. Speaking of small improvements, wide forms are finally in the works for Access beta users - so if you've been itching for forms wider than 22 inches, your prayers are about to be answered. You can grab the beta to try it now or wait a bit for the feature to go mainstream, depending on how adventurous you're feeling.

There were also a few great questions from the forums. One was about migrating tables to SQL Server: do you have to replace your Access queries with SQL Server views? Nope. Linked tables play nice - your Access queries will keep working just fine 99 percent of the time, even across backends. You can take it slow, moving one table at a time, tweaking and optimizing later rather than all at once. When everything is stable, that's when you think about squeezing out speed with views and pass-through queries in SQL Server. Patience here pays off in smooth migrations and fewer headaches.

Technical glitches always come up, and sometimes the answer is frustratingly simple. A member had a CDO email issue pop up after a Windows update. We ran the usual gauntlet of account settings, passwords, and authentication fuss… and then restarting Access fixed it. It sounds silly, but often, the classic "turn it off and back on again" solves a host of mysterious problems. So before you go down a troubleshooting rabbit hole, close all your Access databases, restart Office, and - very important - fully restart Windows (not just sleep mode). Backups first, of course. Save yourself some gray hairs.

For those dabbling with SQL Server: computed columns are a handy feature, but keep your main business data tables clean. Formatting (like concatenating first and last name) belongs in your queries or views. Tables should store data, not display logic. There are always edge cases for performance or indexing, but for display and neatness, keep those computations out of your main tables.

Another interesting exploration: someone wanted to open YouTube videos from Access while bypassing ads with an ad blocker. As an independent creator relying on those ads, let me just say: please do not. The embedded browser control in Access isn't the same as your full browser, so browser extensions and blockers don't carry over. There's no supported way to sneak around it anyway, and, honestly, if you want ad-free YouTube, just get Premium. Keeps creators afloat and gives you the good stuff interruption-free.

Here's a troubleshooting classic: a user's report wasn't showing the letter body. The likely culprit? The report is trying to pull data from a form that is not open or from a dirty (unsaved) record. If you have ever hit print after editing a record and got nothing, that's usually the cause. Make sure you save forms before generating reports - sometimes just refreshing the data does the trick.

For folks curious about macros and VBA: you can use Access's built-in tool to convert macros directly into VBA. It is a great stepping stone for anyone starting with macros and wanting to dip their toes into real code. Quick tip: when you convert a macro, Access adds robust error handling which is handy, especially if you plan on deploying your database to less-experienced users. While I prefer straight VBA for complex automation, macros are a great training ground and sometimes the only way to add buttons to certain places in the interface.

Someone else asked if you can pass tempvars from Access directly to SQL Server. Not directly - tempvars only live in Access. What you can do is grab the value of a tempvar and send that along as a parameter in a pass-through query or stored procedure. Tempvars are just local variables, so once you pull the value, SQL Server is none the wiser about where it came from.

Of course, the old debate of Access versus web applications came up (again!). Honestly, whether Access forms look "professional" is a design choice, not a technology limit. You can make Access look as clean or as cluttered as you like. The critical question is: what problem are you solving? If you need rapid development for local PC users, nothing beats Access for speed. But if your users need browser access - on Macs, phones, or tablets - then sure, build a web front end and connect it to the same SQL Server backend. You do not have to toss out Access; use it where it makes sense and supplement with web parts as needed.

Occasionally, I get requests to build complex, industry-specific databases (like pathology labs or insurance). Here's the thing: the Access part is easy. The tricky part is learning your business and data. Once you know your processes, the fundamentals of tables, relationships, queries, forms, and reports apply to almost any industry. If you know your business, you can apply Access skills to fit the puzzle together.

There were a few more troubleshooting chats - one user struggled with a check register calculation. The usual advice applies: double-check your formulas (credit minus debit), make sure your fields are bound correctly, and always review your spelling. Experience says 99 percent of "broken" queries are really typos or accidental misbindings. And if a video has tens of thousands of views with no revolt in the comments, chances are the formula works, and it is a minor mistake with the implementation.

Final tip of the week: if you want to learn VBA, recording macros in Word or Excel and reading the generated code is a great learning technique. While Access does not have a macro recorder, converting macros to VBA gives you a peek under the hood and helps you bridge the gap from drag-and-drop to real coding.

That's a wrap for this week's adventures in Access. We covered the practical side of normalization, weighed the Access-versus-web debate (spoiler: you can use both), talked SQL Server migrations, shared simple troubleshooting wisdom, and touched on some cool improvements coming soon. For all the gritty details and the full round of questions and screen demos, check out the embedded video above.

Live long and prosper,
RR

How to Use Macros in Microsoft Access

Ever found yourself wishing you could make a single button in your Microsoft Access database run a whole sequence of actions? Automate reports, open several forms, run queries, and more - without needing to learn how to write VBA code? That is exactly where macros come into play. If you are looking to make your database a little smarter but have no intention of turning into a full-blown programmer, let's talk about how Access macros can make your life easier.

Most of us who use Access fall into one of two camps: those who want to go deep and learn VBA to build full-blown applications, and those who just want to knock out repetitive tasks quickly without diving into code. If you are in that second group - the unofficial Access wrangler in your office, the department manager, the small business owner, or, let's be honest, the person who inherited Steve's database when Steve retired - macros are definitely for you.

Here is the lowdown: a macro in Access is just a list of actions that run one after another. Imagine giving Access a checklist: open this form, run that query, pop up a message box, print a report, export some data - whatever you need. You build that list visually, by picking actions from a dropdown. No coding in sight. Just pick, stack, and let Access do the work for you.

This idea of "macros" often throws people who come from Excel or Word, because over there, macros are recorded - click Record Macro, do your thing, hit stop, and you get a bunch of VBA code. Access does not work that way. There is zero recording, and you are not going to end up staring at a wall of VBA. Instead, you pick actions from a menu and put them in order. It is almost funny that Microsoft chose the same word for two such different features.

Macros in Access are for the regular humans - those of us who have a job to do, want to automate it, and have better things to do than click through the same five forms every single morning. Think of the things you do all the time: run a weekly report, prep a mailing list, open a handful of forms and run a set of queries as soon as you start your day. These are exactly the kinds of tasks a macro can help with.

Sure, there is the built-in command button wizard in Access which is great for simple stuff. Want one button that opens a form or prints a report? The wizard has got you covered. But as soon as you want a button to do multiple things - run several queries in sequence, export some data, show a message, then open a report - macros step up to the plate. Now you are free from being limited to just one action at a time.

So what does this actually look like? Open the Macro editor in Access (Create tab, Macros and Code group), and you'll see a list of available actions like opening forms, running queries, showing messages, and more. Want to open your Customer form? Just pick "OpenForm" and select the form. Want to add a message box that pops up? Drop in "MessageBox" anywhere in your list with the text you want viewers to see. The interface is simple. You can reorder your actions, drag and drop commands, and experiment until you get the workflow you want.

One tip: the order of your actions really matters. If you want a warning message to pop up before anything else happens, that "MessageBox" command should be at the top of your list. Want to open two forms? Stack two "OpenForm" actions and rearrange them if you need the second one on top. If you want to clean up, add or remove actions, everything is a click away - undo is your friend. And remember, not every mistake can be solved with Undo; sometimes closing without saving is the better move.

When you are happy with your macro, save it and hook it up to a button on your main menu form. Use the command button wizard (under Miscellaneous actions) and set it up to run your macro. Give it a friendly label like "Open Customers Macro" and now your users get an easy, guided way to kick off some automation without ever having to dig through the database's guts. Less time spent teaching people where to find things, more time spent on real work. If you want to go a step further, you can even add macros to the Quick Access Toolbar at the top - just drop them into the toolbar via the "More Commands" menu and you have one-click access for yourself or everyone who uses the database.

One of the most powerful (and slightly underappreciated) features: the AutoExec macro. AutoExec is a specially named macro that runs automatically every time your database opens. Back in the day, this was your way to set up the database startup experience. Even though modern Access lets you pick a startup form, AutoExec still shines when you need to check whether you are running in a Trusted Location (which determines if VBA will even run) or want to run a sequence of checks before your main menu appears. If your database is sitting somewhere "untrusted," AutoExec can pop up a message to your users telling them how to fix it - way before VBA tries and fails to load your forms.

Macros are not just for beginners, by the way. Even after you have learned VBA, you will occasionally find that the best or even only solution for a particular automation is a macro. You might use one for startup checks, batch processing, or to set up forms when you know users might not have code enabled. They are a great addition to the toolbox rather than a replacement for programming. When you need to do something like clear out a temp table, append two different sets of customers, then open a mailing list report - all in sequence - macro actions make that a breeze. Just drag and drop your queries and report actions in the macro and you are done. Need to tweak the process? Just adjust the queries or change the macro sequence. No redesign needed.

If you are interested in getting a bit more advanced, macros can do a whole lot more: conditional logic, parameter prompts, submacros, business rules, audit logging, and more. There is also a natural progression from macros to VBA if you ever decide you need even more power and flexibility in your database. But for a lot of daily business needs, macros do the job - and make you look like a database wizard in front of the boss (or at least the hero who saves everyone a dozen clicks a day).

The bottom line: macros make it easy to automate the repetitive stuff in Access so you can focus on bigger and better things. They will not replace VBA, but they are a fantastic tool to have whether you are brand new to databases or have been around the block a few times. If you want to see the whole step-by-step process or dig into more advanced techniques, the video above covers the full walkthrough - so check that out for all the hands-on details.

Live long and prosper,
RR

How To Undo Record Changes In Microsoft Access

Ever found yourself in that classic Microsoft Access moment - you are cruising through records, making updates, and then, three customers later, realize you messed up a record way back? Wouldn't it be nice if Undo in Access worked like Control Z in Word and let you gracefully rewind through all your changes?

Let's dig into exactly what Undo can (and cannot) do for you inside Microsoft Access. Spoiler alert: it is not as straightforward as in Word or Excel, but you do have some options - and if you want to get fancy, you can even build something better yourself with a little bit of development magic.

The first thing to understand is that Undo in Access works at the field and record level. As soon as you start typing in a form, the record goes "dirty" - Access's way of telling you data is being edited (watch for that little pencil icon). At this stage, if you want to bail out, you have a couple of options: smash Control Z, hit the Undo button, or simply tap Escape to back out of your changes. Pretty much all will cancel out what you started typing.

It gets more interesting when you edit several fields in a record. Once you've hopped around to different fields and start hitting Undo, you'll notice Access usually undoes just the field you're on - or, if you push it, the entire record. You cannot step back through each field's edits one-by-one like you might expect from Word. There's this odd "second Undo" behavior where, on pressing Undo twice, it sometimes looks like nothing happened. What's really going on is that Undo first reverts your edit in the field, then a second time moves you out of edit mode, and only after that will a third Undo zap the whole record. Yeah, it's weird, but that's how Access rolls.

Now, what if you've already moved off that record? Once you save and shift to the next record, your Undo options shrink fast. Access kindly gives you one "get out of jail" Undo on the last record you changed, but after that - you're out of luck. If you've changed multiple records and only spot your goof several records later, there's no stepping back through history like in Word. Access's focus is being a database, not a document editor, so it just does not keep a giant Undo stack for you.

And don't rely on Redo to save the day, either. Redo in Access is pretty flaky. Sometimes it lets you redo a change if you're still on the right record and field, but a lot of the time - especially after moving around - it just doesn't work. So, if Undo/Redo is part of your workflow, you'll want to stay mindful of these quirks.

If you want to class things up, you can make your own Undo button right on your form. All it takes is attaching a small VBA command like Me.Undo to a button. There's another command (DoCmd.RunCommand acCmdUndo) for folks stuck on ancient Access versions, but Me.Undo is the way to go moving forward. Don't get excited about a Redo command, though - it simply does not exist in VBA.

Now, for folks who want the real deal - a multi-level Undo history - Access does not hand it to you on a silver platter. You can build your own system, but it's a bigger project. The concept is: log every change to a record in a separate table, recording which record and field was changed, the old value, the new value, and maybe a timestamp. With that info, you could create your own Undo (and even Redo) buttons that move back and forth through changes. If that sounds appetizing, there are videos and examples on my site showing how to build a full change log and step through those changes manually using some simple VBA.

This all boils down to: Access will let you Undo a field while you're typing, or the whole record before you save. Once the record's saved and you wander off, you get a single "oops" Undo for that last record - after that, you're on your own. If you want robust multi-level Undo like a word processor, be prepared to get your hands dirty with some change logging and form buttons.

If you are interested in a full walkthrough on building a true multi-level Undo/Redo system in Access (without losing your sanity), let me know in the comments. I love building this kind of stuff and might just make a deep-dive video on it. Either way, keep an eye on those dirty records and don't be afraid to bail out with Undo when you need it.

As always, you can check out the video above for a hands-on demo and to see these little quirks in action. Questions? Comments? Future video ideas? Sound off - I read them all.

Live long and prosper,
RR

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