Quick Queries #100
By Richard Rost
2 days ago
Why Won't Microsoft Office Install? Excel? Access?
In the 100th episode of Quick Queries, we cover common reasons Microsoft Office installation fails and a practical troubleshooting order, including removing old Office installations, checking 32-bit versus 64-bit conflicts, updating Windows, disabling third-party antivirus software, and downloading a fresh installer. We also answer questions about Access queries, backups, recordset types, TempVars, SQL Server conversions, and relational database design.
Theo from Portland, Oregon (a Platinum Member) asks: I've been trying for three hours to install Microsoft Office, but it just keeps stopping and telling me, "Something went wrong. We couldn't install Office." I've rebooted, I've tried it again, and I'm about ready to throw my computer out the window. What am I doing wrong, and what should I try next?
Prerequisites
Links
Recommended Courses
Up Next
Keywords
TechHelp QQ Quick Queries, Office installation failed, Microsoft Office uninstall tool, Office 32-bit 64-bit conflict, Office install error, remove old Office remnants, pending Windows updates, Office installer troubleshooting, third-party antivirus conflict, 3-2-1 backup strategy, TempVars vs module variables
Intro In the 100th episode of Quick Queries, we cover common reasons Microsoft Office installation fails and a practical troubleshooting order, including removing old Office installations, checking 32-bit versus 64-bit conflicts, updating Windows, disabling third-party antivirus software, and downloading a fresh installer. We also answer questions about Access queries, backups, recordset types, TempVars, SQL Server conversions, and relational database design.Transcript Why won't Microsoft Office install even though you've tried everything?
Before you start threatening your computer with a trip up the nearest airlock, let's look at a handful of things that actually cause most Office installation failures.
Welcome to another TechHelp Quick Queries video brought to you by Access Learning Zone. I'm your instructor, Richard Rost.
Today, we're going to talk about why Microsoft Office sometimes refuses to install, what the most common causes are, and the simple troubleshooting steps that solve the vast majority of installation problems without making stuff worse.
We've got that, plus your answers to YouTube comments, questions from my website forums, emails, and lots more.
Now, before we jump into today's questions, I just want to take a second because this is Quick Queries number 100. That's kind of hard for me to believe.
I started this series back in March of 2021. At first, it wasn't even a weekly thing. I'd collect whatever interesting questions came in from emails, my website forums, YouTube comments, and then when I had enough, I'd put together a Quick Queries video.
And somewhere along the way, it turned into a tradition. Now I try to get one out every Friday, or at least by the weekend if life gets in the way, which happens more often than not nowadays.
But the best part isn't that we've made it to 100 episodes. The best part is that every one of these videos exists because somebody asked a good question.
A lot of the ideas that end up in my TechHelp videos, my Quick Queries, my full courses, even features I've added to my own database, all started with conversations like these.
So if you've ever left a comment, posted a question in my forums, or sent me an email, thank you. Thank you for giving me homework to do.
But some of my best videos have come directly from your questions, so it's homework that I love doing. So thanks for being part of this series and for helping me reach 100 episodes. I really do appreciate it.
All right, let's get to the questions.
Today's first question comes from Theo in Portland, Oregon, one of my Platinum members. Theo says, "I've been trying for three hours to install Microsoft Office, but it keeps stopping and telling me something went wrong. We couldn't install Office. Very, very helpful error messages, aren't they? I rebooted and I've tried it again, but I'm about ready to throw my computer out the window. What am I doing wrong and what should I try next?"
Well, Theo, relax. Don't panic. Don't throw your computer out the window just yet. Let's take a look. It's usually one of a couple things that causes these kinds of problems.
All right, so there's about 10,000 videos on YouTube that promise to fix Microsoft Office installation problems. Half of them have you editing the registry within the first 30 seconds.
So before you start doing that or sacrificing a goat to the Office gods, let's take a look at the things that actually cause most Office installation failures.
In my experience, almost every failed Office install comes down to one of a handful of problems.
First is old Office remnants. Usually, a previous version didn't uninstall cleanly. The new installer can get confused and simply refuse to continue.
What I strongly suggest is, if you have another version of Office on the machine, uninstall it completely before installing a new version.
So if you're upgrading from Office 2016 or 2013 or whatever, remove that version completely before you try to install a newer version or you try to move to Office 365, for example. All of those old Office remnants will cause issues.
I'd say about 95% of the time Office can deal with it and move on, but there's that 5% that, yeah, that's a problem.
Next is the classic 32-bit versus 64-bit conflict. I've done a few videos on this before. This one bites Access users all the time, especially if you're installing the Access Runtime or the Access Database Engine.
Here's a video I did about the 64-bit Access version, especially if you're trying to install the Runtime Edition on a machine that already has 32-bit Office, or vice versa. So check this video out for more information. I'll put a link down below.
Now, sometimes the problem isn't Office at all. Windows itself may have pending updates, installer problems, low disk space, or just might need a reboot before it'll cooperate with you.
Security software can also interfere. Some third-party antivirus programs are a little overprotective and can block Office from installing correctly.
Anybody who knows my videos knows I hate third-party virus protection. Get rid of them. The stuff that comes with Windows, what do they call it? Windows Defender or Windows Security, whatever they're calling it today, is just fine. It works perfectly fine. It has everything you need.
And finally, don't forget that sometimes it's not you. Microsoft occasionally has service outages or problems with their download servers. It's rare, but it does happen.
It happened to me once a couple of years ago. I was actually at a client site trying to install Office, and none of the machines would install it. I was pulling my hair out. But it turned out it was a Microsoft outage.
So the good news is that these are all things you can check systematically. Start with the simple stuff first. It'll save you a lot of time and frustration, and then just move on to the more difficult stuff.
And here's the order I'd tackle it.
First, restart Windows. I know everybody rolls their eyes when I say, "Have you tried rebooting?" But it works more times than not. Pending updates, installer locks, files waiting to be replaced, they get cleared all the time with a simple restart.
Completely remove any older Office installations. If a normal uninstall doesn't work, Microsoft has its own uninstall tool. Just Google it: Microsoft Office uninstall tool. Make sure you're getting it from Microsoft's website.
It does a much more thorough cleanup job than just a normal uninstall. So make sure Windows itself is fully updated. If you've got a bunch of pending Windows updates sitting there, let those finish first.
If you are running third-party antivirus software, you might want to temporarily disable it, at least while you're installing Office. A lot of security software causes problems with installations.
If you're in a corporate setting, you might have to get the IT guys involved and say, "Hey, you've got to temporarily disable this for me."
The next thing is download a fresh installer directly from Microsoft. Don't use an installer you downloaded three years ago and found buried somewhere in your Downloads folder.
And again, if you're an Access user, remember the extra gotcha: the 64-bit, 32-bit thing. That happens a lot.
So if you've already got Excel 32-bit on your machine, you can't install Access 64-bit. Office is all the same core libraries of stuff.
You'll also find a more in-depth troubleshooter on my website. This is primarily for Microsoft Access, but it works for most Office stuff. A lot of it's common sense: restart Access, restart Office, reboot the computer, reboot clean, all this stuff. Check for known bugs. Try another machine. Check remaining hard drive space. Update device drivers if needed. Remove third-party software.
I don't know how many times I've seen weird third-party software conflict with Microsoft Office.
Now, one thing I generally don't recommend is jumping straight into registry hacks or downloading random utilities from websites you've never heard of.
Yes, sometimes those fixes work, but they're usually solving one very specific problem, not the problem that most people actually have.
I also tend to avoid third-party uninstallers unless I have a really good reason to use them. Microsoft's own uninstall tool is designed specifically for Office, and it's usually the safer choice without you going out and spending extra money on questionable software.
And be careful with those random YouTube videos, too. Some creators have perfectly good advice, but others immediately jump into advanced fixes because they make for exciting videos.
Editing the registry is a lot more dramatic than saying, "Hey, just reboot your computer."
Mystery downloads are another red flag. If a website you've never heard of says, "Download our magical Office repair utility," I'd be very skeptical.
My philosophy has always been to start with the simplest, safest Microsoft-supported fixes first. If those don't solve it, move on to more advanced troubleshooting.
Don't make your system more complicated than it already is, and don't break things that aren't broken.
Remember, if the problem turns out to be something simple like an incomplete uninstall or a pending Windows update, you just spent an hour making registry changes for absolutely no reason.
Now, before I record one of my own videos, I usually spend a little time researching the topic. Even if I think I already know the answer, I want to make sure nothing else has changed.
Microsoft updates things all the time, and somebody might have a better approach than I have. Plus, I like learning new stuff, too.
So for this one, I looked through Microsoft's official recommendations, some support forums, some Reddit discussions, and a bunch of the highest-ranking YouTube videos.
Honestly, I expected to find a lot of conflicting advice. Instead, almost everybody ended up recommending basically the same checklist that I just gave you.
Remove the old Office installation first, reboot, use Microsoft's uninstall tool if necessary, download a fresh copy of the installer, and try again.
There are lots of little differences around the edges, but once you strip away the clickbait titles and the dramatic registry edits, they all came back to those same basic steps.
And that's actually reassuring. When Microsoft and independent creators in the support community all agree on the same approach, it's usually a pretty good sign you're starting in the right place.
So don't overthink it. Start with the simple, supported fixes first, and then if those don't solve it, then you can dig deeper.
And if you're still having problems after this, post a comment in the forums on my website where we can give you some more help.
Okay, let's see what else we've got in the question bin.
All right, head over to the YouTubes.
We've got George O. asking, "If you're looking for the last two orders for a customer, aren't those automatically the most recent orders?"
Well, that's a great question, and this is exactly where a lot of people get tripped up. "Last" sounds like it means the most recent, at least in English.
But in Access, the Last function doesn't mean that at all. It just means return the last record that happens to come through the query.
So unless you've explicitly controlled the order, that's not something you should rely on.
So if you want the two most recent orders, sort by your Order Date in descending order and use Top Two.
And if you're looking for just the most recent date, use the Max function with Order Date.
Think of Last as "last in the current recordset," not "latest in time." Those are two very different things.
For example, if your recordset is sorted by the ID and someone has changed the date, like they entered a new order but backdated it, it's not going to be correct chronologically.
I've got a whole separate video on why you shouldn't use the First and Last functions. Stick to Max and Min if you're dealing with dates. So go watch this video if you'd like more information.
Next up, we've got Shadow Dragon saying, "How about doing some more on backups, things like the 3-2-1 backup strategy, full versus incremental versus differential, and how long you should keep them?"
That's actually a great suggestion. I've done quite a few videos over the years about backing up Access databases, but I really haven't done one much on general Windows backup strategy.
If you haven't seen it yet, this one here has all my thoughts on backing up Access databases.
Personally, I use Macrium Reflect. It does an incremental backup every night and a full backup once a month, and I make sure those backups are stored off-site, too.
These days, hard drives are big enough that I'd rather have too many backups than not enough.
And for those of you who haven't heard of the 3-2-1 backup rule, it's a simple guideline. It's been around for years.
Basically, it says keep three copies of your data, at least: the original plus two backups.
Store those backups on at least two different types of media, like your internal hard drive and an external drive or a network storage, and keep at least one copy off-site, whether it's cloud storage or a thumb drive you keep in your office and take home or whatever.
If your computer dies, if your hard drive fails, if your house gets hit by a meteor, you've still got a backup somewhere else.
That's basically what I do. My main machine runs an incremental backup every night and a full backup once a month. I make sure those backups are copied off-site.
You can even do it with something simple like Google Drive. It syncs up to the cloud.
The exact software doesn't matter as much as having a backup system you actually use.
And just as importantly, once you've made the backups, you've got to make sure you test them and do a restore once in a while so you don't just have a backup. It's both valid and not valid until you test it.
So if you would like to see more videos on backup strategies, the 3-2-1 rule, full versus incremental versus differential backups, disaster recovery, restoring from backups, all that stuff, let me know in the comments.
And if people are interested, I'll definitely put a series together. It's a lot of good stuff, and people, I don't think people back up enough.
I'm pretty obsessive. I've lost hard drives before and lost weeks of work. I had a seminar I was working on years ago, and I had probably 10 hours of video recorded and ready to go. Then the hard drive crashed, and I didn't have it on a different drive. It set me back weeks.
So back up your stuff, folks.
But yeah, let me know if you guys want to see more videos on backups. I'll be happy to make some.
Next up, Jade Dragon says they're really enjoying the new video quizzes. And they're also wondering if I should try YouTube's built-in quiz feature, so people can answer questions right in YouTube instead of posting the scores in the comments.
I like seeing the scores posted in the comments. You guys have been posting a lot of them.
I'm really glad you guys are enjoying the quizzes because I've had a blast making them. I've already done a couple. I've got more on the way.
The nice thing is the quizzes are fun, they're interactive, and I can produce them pretty quickly. That lets me keep something new coming out every day on the channel while I spend more time on bigger projects like my Access Developer course and the SQL Server series that I'm way behind schedule on.
I haven't played with YouTube's built-in quiz feature yet, but I'll definitely take a look.
My only hesitation is I also post these quizzes on my website, so I don't know if I want to tie them in too closely to YouTube's quiz engine.
What do you guys think? If you guys use the YouTube quiz feature, is it something you'd actually participate in, or do you just prefer the way we're doing it now?
I like seeing people post in the comments with their scores. So let me know. Post a comment down below. I'm genuinely curious what you think and if you've used YouTube's quiz thing before.
And I'll put links to video quizzes one and two down below.
Next up, Kevin said he accidentally changed a form's Recordset Type to Snapshot once and spent forever wondering why none of his forms would let him edit data. He thought he'd broken the database when it was really just one property.
Yeah, I've done the same thing.
Snapshot is great when you just want to display data because it's read-only. And it can be a little faster since Access doesn't have to worry about record locking or updates.
But if you accidentally switch an editable form to Snapshot, it suddenly behaves like it's broken because you can't add records, you can't edit records, and you start questioning your life choices.
If you're working with DAO recordsets in VBA, the default is Dynaset, which does allow you to edit records. A Snapshot is read-only, and a Table-Type recordset is available when you're opening a local Access table directly.
So make sure you've got the right recordset type for what you're trying to do.
And yeah, I know what you mean about small fonts and monitor resolution. That's one of the reasons I'm excited about the new form zooming built into Access.
Now I can't wait until it's in Design View, too. It seems that's where I need it the most, in design.
I still have to use the Windows Magnifier sometimes to get it to zoom in on those little grid dots.
So thanks for the question or comment.
This one's just, again, to remind everyone: I have zero control over when the audio translations are available on YouTube.
I've got them all turned on for every language that's available. I do know that sometimes it can take a couple days to a week or whatever before our YouTube server gods do whatever they're doing and make the translations.
But I've got them all turned on. So if yours isn't available yet, sorry, you'll have to wait. It'll be available as soon as it's available. I have no control over this whatsoever.
Speaking of that video quiz, Brock said he answered "foreign key" for question four instead of "field." He admits he was being too specific, but he's still hoping for credit.
And he did say, "Live long and prosper," so I'll give you partial credit.
Technically, you are correct. If you look at what I put in the quiz, I did highlight this, which is in the Order table, and it is technically a foreign key.
But this was a beginner, easy video based on my Access Beginner Level 1. So they don't know foreign keys yet.
So I'll give you partial credit. But sadly, no fabulous prizes, no new car, and no all-expenses-paid trip to Risa.
But your comment is actually one of the reasons I decided to make future quizzes all multiple choice. It removes some of the ambiguity, and it also lets me have fun coming up with two believable wrong answers and one completely ridiculous choice just to see who picks it.
Next up, TaxFree4603 says, "Still didn't fix my problem. So annoying."
Well, I'm sorry to hear that, but I've got absolutely no idea which problem it is because you didn't tell me.
"It still didn't work," but you didn't give me anything to go on.
I get this a lot in my forums, and people email me like, "It's not working."
Okay. What? What are you doing? What have you tried? Are you getting an error message? If so, what's the error message?
"It didn't work" or "It didn't fix my problem" tells me nothing.
Help me help you, folks. The more details you give me, the better chance I can actually point you in the right direction.
So right now, I'd just be guessing, and I don't like to guess.
So post another comment and let me know. And don't reply to this one because then I won't see it. Post a fresh one.
Next up, we've got Lucy. She said she'd come back to Access after a 25-year break.
Well, welcome back.
She found one of my older image videos helpful and mentioned she keeps all of her pictures in one folder, storing just the file name in the database, and that's what I recommend that you do.
First of all, welcome back. Twenty-five years is quite a break. The last version that you used was probably 97.
There wasn't a 98. There was Office 98, I think, but it was for Mac and it didn't have Access.
So you've got, let's see, we had Access 2.0. That's the one I started with. I never used 1.0. That was, like, what, 1994, I want to say?
Then there was 95, 2000, 2003, 2007. 2007 was the first major revision that brought us the Ribbon, which I hated. I couldn't stand it. They got rid of the File, Edit, View menu.
But now I love it. Once I got used to it, I loved it.
And there have been a bunch of them since then: 2010, 13, 16, 19, 21, 24, or just get Microsoft 365 now and it's all just the same thing.
But yeah, for pictures, I still recommend storing the images in one central folder and just saving the file name or the relative path in the database.
So if you've got multiple users, you can put that folder on your shared network drive. I use a Z drive myself. It could be your D drive or whatever letter you want, or use a UNC path. That's fine, too.
And if it's just for one user, if it's a single-user database, you can use CurrentProject.Path and keep the images in a folder under your database.
That's what I do for databases where I'm the only person using them, which is most of my databases.
But I've got to sometimes be a little more forward-thinking.
But I've got several newer videos on handling images since that one came out. And I think in the extended cut for that video, we talk about file browsing and all kinds of stuff.
So there's lots more resources available on my YouTube channel and on my website.
So again, welcome back to Access, and glad to see you. Thanks for the comment.
Next up, Xavier says he prefers using module variables instead of TempVars whenever possible.
Don't let Adam hear that. Adam will fight you for TempVars.
No, but that's a perfectly valid approach. Module variables are fast and they work great.
Personally, though, I like TempVars because they're a little more forgiving, especially when I'm developing.
One nice thing about TempVars is they'll hold pretty much whatever you want to throw at them. You don't have to declare a type ahead of time. Throw a date in there, a string value, a number, whatever.
And more importantly, they survive VBA resets.
So if you're writing code and you hit an unhandled error or you stop your code with a debugger, all of your module variables disappear.
Then you've got to reload your startup forms, reopen your main menu, recreate all that state. TempVars just keep right on trucking.
Now, for a finished end-user application where you've got proper error handling, that's not usually a big deal. So if you like module variables, great. There's nothing wrong with that.
I just find TempVars to be a little more developer-friendly while I'm building and debugging a database.
Because when I'm building and debugging, or if I'm recording a video, you guys see it. I throw errors all the time. Now it's like, "Crap. Now I've got to reload the main menu, reopen the customer form, go back to here."
So all those variables reset. TempVars, not a problem.
Plus, another thing I like about TempVars is they're easy to make dynamic.
In other words, since you're referencing them by name, you can build those names in code.
So you could say TempVars and then, in a string, MyValue, and then an X and put a value there. So you can have MyValue1, MyValue2, MyValue3.
You could put them in a loop. You could do all kinds of stuff.
You can construct that name on the fly with a string variable and then retrieve or store the value without having to declare a bunch of separate variables or work with arrays.
Arrays are a pain in the butt. Or arrays. I call them arrays. I don't care what you guys say.
I mean, there's lots of other ways to accomplish the same thing. I just find TempVars make that kind of dynamic programming nice and straightforward and easy.
Next up, we've got Jose. He says, "Great insights on SQL Server. How would you handle Access functions like IIf or IsNull when you move your queries over to SQL Server?"
That's one of the biggest hurdles when people first move from Access to SQL Server. That was one of mine.
SQL Server is very similar, but it's not identical. And a lot of the Access-specific functions simply don't exist in T-SQL, so you have to translate them.
For things like the IIf function or IsNull, in Access, you'd say IIf(IsNull(FirstName), "Unknown", FirstName).
In SQL Server, it's written like this. You don't even need the IIf function. You just say IsNull(FirstName, "Unknown"), and then the value to use if it's null.
So it's a different way of thinking.
Or you could also use Coalesce, which is a different function.
In the WHERE conditions, for example, you might say WHERE IsNull(FirstName), and in SQL Server, you need WHERE FirstName IS NULL, spelled out like that.
Which you can also do that in some places in Access, too. So it depends on what you're doing.
But the good news is this is exactly one of the things that AI is really good at.
You can take an Access query and hand it to ChatGPT or whatever AI you're using and say, "Convert this to T-SQL from Access." And it usually does a pretty good job.
In fact, that's exactly what I'm doing in my Access Web Publisher. This is a tool that I'm building to migrate your tables, queries, and forms up to the web from Access.
But I've got a query migration tool.
For example, the ampersands and the double quotes. If you test this on SQL Server, it doesn't like that because of the ampersands and that.
So you can use AI to convert it to T-SQL. Success.
And then it rewrites it using the pluses and the little single quotes there.
So that's just one of the tools I've got in my Access Web Publisher, which is in beta right now, by the way.
This is what it's cool for, is the form publisher.
You could take your forms. Here's the TechHelp Free Template. You guys have all seen it. Here's the Customer form. Here's the same form in a web browser. That's what this project does.
So it's still in beta and I'm working on it. If you're interested, post a comment down below. Maybe I'll accept some new beta testers.
And next up, I've got a couple comments from a few people like, "Hey, how did you build the main menu?"
You can't really jump in and work on many of these. This is my Fitness series. I think I'm on, like, part 73. So there's lots of videos before this one. You've got to go watch those ones.
It's like for my full course. You can't just jump in at Access Developer 42 and expect to understand everything that came before it. You've got to watch all the stuff that came before it.
It's like when you go to school. You can't just jump into a calculus class if you don't know basic arithmetic.
So go watch the first 72 videos and you'll know what's going on in 73. They're all free. Enjoy.
And finally tonight, we've got a beginner question from Grimlock, commenting on my Access Beginner 1 course.
He's asking whether each customer has their own separate contact history table or if all of the contacts are stored together and then filtered for each customer.
And this is a great beginner question because it's one of the first things people wonder when they're learning relational databases.
No, you don't make a separate contact table for each customer.
You have one customer table that holds all your customers. Here, I'll show you in the database.
Here's a customer table. This holds all of the customers.
And then you have a contact table, a single contact table that has all of the contacts in it. Contacts being every time you talk to this person, that's a contact.
One contact table holds all of the contact records. Each contact record has a CustomerID field in it.
This is called a foreign key. This relates back to this table. That tells Access which customer this contact belongs to.
This is customer one. These are customer twos. These are customer threes, and so on.
So customer two has three contacts stored in the contact table with CustomerID. Contact IDs 15, 16, 70. Those are irrelevant. Those are the primary key in this table, but this is what links it back to the customer table.
And that's one of the biggest advantages of relational databases. One table can hold millions of contacts for thousands of customers without you having to create thousands of separate tables.
So stick with it. Access Beginner 1 only goes over the real basics of relationships. I get into more of those when you get up into my Expert series.
But I'd also recommend you take some time to go watch this video, too. This free one. It's all the different kinds of relationships. Go watch it. I'll put a link down below.
Hey, if you haven't, please like and subscribe. It helps the channel out. It helps more people find my videos, and I'll love you forever.
Before you go, don't forget to stop by my website. Check out what's new. I'm always adding new videos, updates, templates, random bits of Access goodness over there.
So check it out, and you might see something pretty cool.
Don't forget to check out the Captain's Log, where I post my thoughts about whatever I happen to be thinking that day. Sometimes it's Access. Sometimes it's science. Sometimes it's random weird stuff.
I recently updated the customer service spot on my website. I programmed it with a whole bunch of new stuff about the website. So you've got to be logged on to use it.
But if you've got questions about memberships or what's covered in what class, this is the place to go.
I also received my MVP Award renewal. It's number six. So, yay me.
And yeah, I broke my forums briefly. Just something stupid. But it happens to all of us.
You can see Jerry and I are putting out a lot of Engine Room Faggots. Check out the merch store. Get a hat, get a coffee mug, get a mouse pad with your favorite logo on it.
Check out my book on Amazon.
If you've got questions about Access stuff, post them in my forums.
If you're looking for a tutor or a consultant or a developer to help you with your project, check out my Access Developer Network.
And don't forget to get on my mailing list so I can bug you when I release new stuff.
But there you go. That is Quick Queries 100.
I feel like I've gotten a lot done with 100 of these.
But that's going to be your Quick Queries TechHelp video for today. I hope you learned something, and I hope you've learned something over these last 100 or so episodes.
Live long and prosper, my friends. I'll see you next time.Quiz Q1. What is a good first step when Microsoft Office will not install?
A. Restart Windows
B. Edit the Windows registry
C. Download a random repair utility
D. Reinstall all device drivers
Q2. Why can an older Office installation prevent a new Office installation from working?
A. Older files and settings may not have been removed cleanly
B. Older Office versions automatically disable Windows Update
C. Office can only be installed once per computer lifetime
D. Older Office installations remove all available disk space
Q3. What should you do if the normal Office uninstall does not remove an old installation completely?
A. Use Microsoft's official Office uninstall tool
B. Delete random Program Files folders
C. Install a third-party registry cleaner
D. Rename the Office installation folder
Q4. What type of Office conflict commonly affects Access users installing the Runtime or Database Engine?
A. A conflict between 32-bit and 64-bit Office components
B. A conflict between Word and PowerPoint fonts
C. A conflict between Excel worksheets and Access tables
D. A conflict between local and cloud documents
Q5. If a computer already has 32-bit Office installed, what should generally be avoided?
A. Installing a 64-bit Office component alongside it
B. Opening an Access database
C. Updating Windows
D. Creating a new Excel workbook
Q6. Why should pending Windows updates be completed before trying to install Office?
A. Pending updates can leave installer files or system changes waiting for a restart
B. Windows updates permanently remove Office installers
C. Office cannot be installed on an updated computer
D. Updates automatically change Office to read-only mode
Q7. How can third-party antivirus software affect an Office installation?
A. It may block or interfere with installation files
B. It can convert Office documents into PDFs
C. It automatically upgrades Office licenses
D. It changes all Office applications to 64-bit
Q8. Why is it better to download a fresh Office installer directly from Microsoft?
A. An old installer may be incomplete or outdated
B. Fresh installers use less disk space forever
C. Microsoft installers do not require an Internet connection
D. Old installers always contain viruses
Q9. What is the recommended approach before trying registry hacks for an Office installation problem?
A. Start with simple Microsoft-supported troubleshooting steps
B. Delete all Windows user accounts
C. Reformat the computer immediately
D. Install several repair tools at once
Q10. In Access, what does the Last function actually return?
A. The last record in the current recordset order
B. The most recent record by date
C. The record with the largest primary key
D. The last record entered by the current user
Q11. What is the best approach for finding the two most recent orders for a customer?
A. Sort by Order Date descending and use Top Two
B. Use the Last function without sorting
C. Sort by CustomerID ascending
D. Use the First function on the customer table
Q12. Which function is generally appropriate when you need the most recent date?
A. Max
B. Last
C. First
D. Count
Q13. What does the 3-2-1 backup strategy recommend?
A. Three copies of data, two types of media, and one off-site copy
B. Three cloud accounts, two passwords, and one USB drive
C. Three full backups every day, two restores every week, and one new computer
D. Three users, two administrators, and one shared folder
Q14. Why should you periodically test a backup by restoring it?
A. A backup is only useful if it can actually be restored successfully
B. Restoring automatically makes future backups smaller
C. Testing backups prevents hard drive failures
D. Restoring changes an incremental backup into a full backup
Q15. What happens if an Access form has its Recordset Type set to Snapshot?
A. The form becomes read-only
B. The form automatically deletes duplicate records
C. The form can only show charts
D. The form becomes a table-type recordset
Q16. Which Access recordset type normally allows records to be edited?
A. Dynaset
B. Snapshot
C. Read-only
D. Archive
Q17. What is an advantage of TempVars over module variables while developing and debugging Access applications?
A. TempVars survive VBA resets
B. TempVars can only store numbers
C. TempVars automatically create database tables
D. TempVars replace all form controls
Q18. How should images generally be stored for an Access database?
A. Store image files in a folder and save the file name or path in the database
B. Create a separate image table for every customer
C. Store all images only inside a form control
D. Put every image in a separate Access database
Q19. In a relational database, how should customer contacts usually be stored?
A. In one contact table with a CustomerID field linking each contact to its customer
B. In a separate contact table for each customer
C. In the customer table as repeating Contact1, Contact2, Contact3 fields
D. In a separate database file for each contact
Q20. What is the purpose of a foreign key such as CustomerID in a contact table?
A. It links each contact record to the related customer record
B. It uniquely identifies every contact record in the entire database
C. It prevents users from opening the customer table
D. It stores the customer's phone number
Q21. In SQL Server, how would you test whether FirstName contains a null value?
A. WHERE FirstName IS NULL
B. WHERE IsNull(FirstName)
C. WHERE FirstName = Null
D. WHERE FirstName = ""
Q22. What can be used to replace an Access expression such as IIf(IsNull(FirstName), "Unknown", FirstName) in SQL Server?
A. ISNULL(FirstName, 'Unknown')
B. Last(FirstName, 'Unknown')
C. IIf(FirstName = Null, "Unknown")
D. FirstName & "Unknown"
Answers: 1-A; 2-A; 3-A; 4-A; 5-A; 6-A; 7-A; 8-A; 9-A; 10-A; 11-A; 12-A; 13-A; 14-A; 15-A; 16-A; 17-A; 18-A; 19-A; 20-A; 21-A; 22-A
DISCLAIMER: Quiz questions are AI generated. If you find any that are wrong, don't make sense, or aren't related to the video topic at hand, then please post a comment and let me know. Thanks.Summary In today's Quick Queries video, I answer a collection of questions about Microsoft Office installation problems, Microsoft Access, backup strategies, SQL Server, TempVars, database relationships, and a few updates from my website and YouTube channel.
This is Quick Queries number 100, which is hard for me to believe. I started this series in March 2021 as an occasional collection of interesting questions from emails, website forums, and YouTube comments. Over time, it became a regular feature, usually released every Friday or over the weekend when life gets in the way.
The best part of creating these videos is that they are driven by your questions. Many of my TechHelp videos, Quick Queries episodes, full courses, database features, and other projects begin with someone asking a good question. I appreciate everyone who has commented, emailed, posted in the forums, or otherwise helped provide ideas for these lessons.
One of the most frustrating problems people encounter is Microsoft Office refusing to install. Unfortunately, Office installation errors are often vague. You may see a message such as "Something went wrong" or "We couldn't install Office," which does not provide much useful information.
Before making complicated registry edits or downloading random repair tools from the Internet, I recommend checking the most common causes of Office installation failures. In my experience, most Office installation problems come down to a small number of issues.
A very common cause is remnants from an older Office installation. If an earlier version of Office did not uninstall cleanly, the new installer may become confused and refuse to continue. If you are upgrading from Office 2013, Office 2016, Office 2019, or another older version, uninstall the previous version completely before attempting to install the new version or Microsoft 365.
Office can often handle older components and continue anyway, but sometimes leftover files, registry entries, services, or installation records interfere with the new installation.
Another common problem is a conflict between 32-bit and 64-bit Office components. This is especially important for Microsoft Access users. For example, if you already have a 32-bit version of Excel or Office installed, you generally cannot install a 64-bit version of Access, the Access Runtime, or the Access Database Engine alongside it.
Office applications share many core libraries, so the installed components generally need to use the same bitness. If you are having problems installing Access Runtime, the Access Database Engine, or another Office-related component, verify whether your existing Office installation is 32-bit or 64-bit before downloading anything else.
Sometimes Office is not actually the problem. Windows itself may have pending updates, installer services that need to restart, files waiting to be replaced, low disk space, or other system issues that prevent Office from installing properly.
Security software can also interfere with Office installation. Some third-party antivirus products are overly aggressive and may block installers, prevent files from being created, or interfere with Microsoft services. I generally recommend relying on the protection included with Windows, such as Microsoft Defender or Windows Security, rather than adding a separate antivirus suite unless you have a specific reason to do so.
In a business environment, you may need to speak with your IT department if company security software is blocking the installation. They may need to temporarily allow the installation process or disable a particular security rule.
It is also possible, although less common, that Microsoft is having a problem with its download or activation servers. I have seen situations where multiple computers could not install Office because Microsoft was experiencing a temporary service issue. In that situation, no amount of local troubleshooting will solve the problem until the service issue is resolved.
When Office will not install, I recommend following a simple troubleshooting order.
First, restart Windows. I know this sounds basic, but rebooting clears pending installer locks, finishes file replacements, restarts services, and resolves many temporary Windows issues. A restart is often more effective than people expect.
Next, remove any older Office installations. Use the normal uninstall process first. If that does not work, Microsoft provides an official Office uninstall tool that can remove Office more thoroughly than the standard Windows uninstall process. Search for the Microsoft Office uninstall tool and make sure you download it directly from Microsoft's official website.
After Office has been removed, make sure Windows is fully updated. Install pending Windows updates and restart the computer again if necessary. Office installation can fail when the operating system is waiting for updates or has incomplete system changes pending.
If you are using third-party antivirus software, temporarily disable it while you install Office. If that solves the problem, you may need to adjust the antivirus settings or consider whether the software is causing more trouble than it is worth.
Always download a fresh Office installer directly from Microsoft. Do not use an old installer sitting in your Downloads folder from several years ago. Microsoft frequently updates Office installers, and an old installation package may not work correctly with your current version of Windows or your Microsoft account.
Access users should also confirm the 32-bit versus 64-bit requirement before installing anything. For example, if you have 32-bit Excel installed, you should normally install 32-bit Access as well. Mixing Office bitness is one of the most common causes of installation problems involving Access Runtime and the Access Database Engine.
There are many videos and articles online that immediately recommend registry hacks, third-party uninstallers, or mysterious repair utilities. I generally do not recommend starting there. Registry edits may solve one very specific problem, but they can also create new problems if you change the wrong setting. Similarly, unknown cleanup tools and repair utilities may not be trustworthy.
Start with simple, safe, Microsoft-supported steps. Restart Windows, remove old Office components, run the official uninstall tool if necessary, update Windows, download a fresh installer, and confirm that your Office bitness matches. In many cases, those steps solve the problem without making your computer more complicated.
For Microsoft Access users, I also discussed a question about finding the last two orders for a customer. This is an area where people often misunderstand the Access Last function.
In everyday English, "last" often means "most recent." In Access, however, the Last function does not necessarily return the newest record by date. It returns the last record that happens to be present in the current recordset. Unless the recordset is explicitly sorted, you should not assume that Last means the latest record chronologically.
If you want the two most recent orders for a customer, sort the records by OrderDate in descending order and return the top two records. If you only need the most recent date, use the Max function on the date field.
Think of Last as meaning "last in the current recordset," not "latest in time." Those are very different concepts. If your records are sorted by an ID field, for example, and someone entered a newer record with an older date, the Last function may not return the record you expect. For date-based questions, Max and Min are generally more reliable than First and Last.
Another question concerned backups and the 3-2-1 backup strategy. This is an important topic because many people do not back up their files often enough until they experience a hard drive failure, ransomware attack, accidental deletion, or other disaster.
The 3-2-1 rule is a simple and useful guideline. Keep at least three copies of your data: the original file plus two backups. Store those copies on at least two different types of media, such as an internal drive, external drive, network storage device, or cloud service. Finally, keep at least one copy off-site.
An off-site backup can be stored in the cloud, at another location, or on a drive that is kept somewhere other than your home or office. The point is that if your computer fails, your building is damaged, or your local storage is destroyed, you still have a copy of your important information elsewhere.
I use Macrium Reflect for my own backups. My primary computer creates an incremental backup every night and a full backup every month. I also make sure that backups are copied off-site.
A full backup contains everything selected for backup. An incremental backup stores only the changes made since the previous backup. A differential backup stores changes made since the last full backup. Each method has advantages, but the specific software and backup method are less important than having a reliable backup system that you actually use.
You should also test your backups periodically. A backup is only useful if you can successfully restore it. Try restoring files occasionally, and make sure you understand how to recover your system before you are facing an emergency.
I also discussed the video quizzes that have been appearing on the channel. I have enjoyed creating them, and they provide a quick interactive way to review Access concepts. Multiple-choice quizzes are particularly useful because they remove some ambiguity from the answers while allowing me to include a few believable incorrect options and, occasionally, an obviously ridiculous choice.
When asking for technical help, remember that saying "It didn't work" is usually not enough information for someone to solve the problem. If you need assistance, provide details about what you were trying to do, what happened, any error messages you received, what version of Access or Office you are using, and what troubleshooting steps you have already tried.
The more information you provide, the more likely someone can help you quickly. Without details, anyone trying to help is forced to guess, and guessing is rarely productive when troubleshooting technical problems.
I also answered a question from someone returning to Access after a long break. If you are storing images in an Access database, I generally recommend keeping the actual image files in a central folder and storing only the file name or file path in the database.
For a multi-user database, the image folder can be stored on a shared network drive or accessed through a UNC path. For a single-user database, you can store images in a folder beneath the database folder and refer to that location using CurrentProject.Path.
Storing image files externally instead of embedding them directly in Access tables can help keep your database smaller and more manageable. It also makes it easier to update, replace, move, and organize images.
Another question involved TempVars versus module-level variables in Access VBA. Both approaches are valid, and each has advantages.
Module variables are fast and convenient. However, they are cleared when VBA resets. For example, if an unhandled error occurs, if you stop code while debugging, or if the VBA project resets for another reason, module variables lose their values. You may then have to reopen forms, reload menus, or recreate application state.
TempVars are often more forgiving during development because they survive VBA resets. They can hold different types of values without requiring you to declare a specific variable type in advance. You can store dates, numbers, strings, and other values as needed.
TempVars can also be useful when you need dynamic variable names. Since TempVars are accessed by name, you can construct names in code and use them to store or retrieve related values. There are other ways to handle this kind of situation, including arrays and collections, but TempVars can be a simple option for certain Access applications.
For finished applications with solid error handling, module variables are perfectly reasonable. I just find TempVars especially useful while building, testing, debugging, and recording lessons because they do not disappear every time an error stops the VBA project.
I also discussed moving Access queries to SQL Server. Access SQL and Transact-SQL are similar, but they are not identical. Many Access-specific functions do not exist in SQL Server, so you must translate them when converting queries.
For example, Access commonly uses IIf and IsNull in expressions. SQL Server may use ISNULL, COALESCE, CASE expressions, and other T-SQL syntax depending on the situation. Null checks are also written differently. In SQL Server, you generally use IS NULL or IS NOT NULL rather than relying on Access-style expressions.
String concatenation also differs between Access and SQL Server. Access commonly uses ampersands and double quotes in expressions, while SQL Server has its own syntax and conventions.
AI tools can be helpful for translating Access queries into T-SQL. You can provide an Access query and ask an AI tool to convert it to SQL Server syntax. The results should still be reviewed and tested carefully, but this can save time when moving a database from Access to SQL Server.
This kind of query conversion is also part of the work I am doing with my Access Web Publisher project. The goal of that project is to help migrate Access tables, queries, and forms to web-based applications. It is currently in beta development.
I also addressed a question about building a main menu in a larger Access database project. When you are following a long series, it is important to start near the beginning rather than jumping into a later lesson without the necessary background.
Access development is cumulative. If a project is on lesson 73, that lesson may rely on tables, forms, VBA procedures, queries, and design decisions created in the first 72 lessons. It is similar to trying to take calculus without first learning arithmetic and algebra. The earlier lessons provide the foundation needed to understand the later ones.
Finally, I answered a beginner question about contact history tables and customer records. You should not create a separate contact history table for every customer.
Instead, use one Customer table containing all customers and one Contact table containing all contacts. Each contact record should include a CustomerID field that identifies which customer the contact belongs to.
The CustomerID in the Contact table is a foreign key. It links each contact record back to the appropriate customer record. One customer can have many contact records, while each contact record belongs to one customer.
This is one of the main benefits of a relational database. You can store millions of contacts for thousands of customers in a single Contact table without creating thousands of separate tables. The relationship between the tables keeps the data organized.
I have also continued making updates to my website, customer service resources, forums, templates, and other Access-related materials. I recently renewed my Microsoft MVP Award for the sixth time, which I greatly appreciate.
If you have questions about Microsoft Access, Office, Windows, backups, database design, or other technical subjects, you can post them in my forums or leave a detailed comment. Your questions often become the basis for future lessons.
You can find a complete video tutorial with step-by-step instructions on everything discussed here on my website at the link below. Live long and prosper, my friends.Topic List Common causes of Microsoft Office install failures
Removing older Office installations
Using Microsoft's Office uninstall tool
Resolving 32-bit and 64-bit Office conflicts
Installing pending Windows updates
Third-party antivirus installation conflicts
Downloading a fresh Office installer
Avoiding unsafe registry hacks and repair toolsArticle Microsoft Office installation failures are usually caused by a small number of common problems. Before trying registry edits, downloading unknown repair utilities, or making major changes to Windows, start with the simplest and safest checks.
The first step is to restart your computer. A restart can clear pending updates, temporary installer locks, and files that Windows is waiting to replace. It may seem obvious, but it resolves more installation problems than people expect.
Next, check whether an older copy of Office is still installed. A previous installation may not have been removed completely, and leftover files or settings can prevent the new installer from continuing. If you are replacing an existing Office installation, uninstall the old copy first. If the normal uninstall process fails or the new installer still reports an error afterward, use Microsoft's official Office uninstall tool. This is designed to remove Office components more thoroughly than the standard Windows uninstall option.
Another common cause is a conflict between 32-bit and 64-bit Office components. Office applications generally need to use the same architecture. For example, if Microsoft Excel is installed as a 32-bit application, installing a 64-bit edition of Microsoft Access or the Access Runtime can fail. This is especially important for Access users who install the Access Database Engine, Runtime, or other Office-related tools. Check what is already installed before choosing an installer.
Make sure Windows is fully updated before trying again. Pending Windows updates can interfere with installations, especially if they involve system components, installers, or security updates. Install all available updates, restart the computer, and then try the Office installation again.
Also check that you have enough free disk space. Office itself may not require a huge amount of space, but the installer needs room to download, unpack files, create temporary files, and complete updates. Low disk space can cause vague installation errors that do not clearly explain the real problem.
Third-party antivirus and security software can sometimes block or interrupt Office installations. If you use a separate antivirus product, temporarily disable it while installing Office, then turn it back on when the installation is complete. In a work environment, security policies may be controlled by your IT department, so you may need their help to allow the installation.
Always download a fresh installer directly from Microsoft. Avoid using an old installer from your Downloads folder, a copied installer from another computer, or a file obtained from an unfamiliar website. Older installers may be outdated, incomplete, or incompatible with your current Windows configuration.
It is also possible that the problem is on Microsoft's side. Although uncommon, Microsoft download services and activation services can have temporary outages. If multiple computers cannot install Office at the same time, or the installer consistently fails during downloading, wait a while and try again later before making major changes to your system.
A sensible troubleshooting order is to restart Windows, remove older Office installations, run Microsoft's official uninstall tool if needed, apply Windows updates, verify disk space, temporarily disable third-party security software, and download a fresh installer from Microsoft. Then confirm that all Office components you are installing use the same 32-bit or 64-bit architecture.
Avoid jumping immediately to registry changes or random repair tools found online. Those methods may solve a rare, specific problem, but they can also create new issues and make future troubleshooting harder. Start with supported fixes first. Most Office installation problems are caused by incomplete old installations, pending updates, architecture conflicts, security software interference, or a corrupted installer download. |
