Access 2007-2019
Access 2000-2003
Access Seminars
TechHelp Support
Tips & Tricks
Access Forum
Course Index
Topic Glossary
Insider Circle
Home   Courses   Seminars   Templates   Help   TechHelp   Forums   Contact   Join   Order   Logon  
Home > Troubleshooter
By Richard Rost   Richard Rost on Twitter Richard Rost on LinkedIn Email Richard Rost   3 months ago

Microsoft Access Database Troubleshooting Checklist

 S  M  L  XL  FS  

I get emails all the time from people with Access issues. All of the problems and questions from many of you have inspired me to start this: the Access Debugging and Troubleshooting Checklist.

I know I've pulled my hair out with strange Access problems that sometimes seemed to get fixed by the strangest things. I went nuts one day trying to fix a bug and it turned out I just needed to reboot the PC. Low system resources can cause any number of problems, including forms not opening, reports not printing right, crashes, etc.

So, here's my list of troubleshooting tips when you've got that Access problem that just will NOT go away. I have tried to rank these in the order you should check. The least painful fixes (quick and easy) are first. Try each one in order. If that doesn't work, move on to the next one.

Backup First

My standard disclaimer applies. Before doing ANYTHING with your database, you should always make sure you have a good backup. 'Nuff said.

Restart Access

Close and restart your database.

Restart All Access Databases

Close and restart any and all Access databases. You may also want to check the Windows Task Manager and make sure that all instances of Access are closed. 

Compact & Repair

From inside your database, go to Database Tools > Compact & Repair. See this video for more on the Importance of Compact & Repair.

Compile the Database

In the VB editor window, go to Debug > Compile [Database Name]. You'd be surprised what bad code in one Module will do to another. Usually this just highlights syntax errors, but you'd be surprised sometimes. 

Restart Office

Close and restart any open Microsoft Office Applications. They share DLLs so even a misbehaving Excel file can keep Access doing weird things.

Reboot the PC

That game you were playing last night might have eaten up your available memory. Those Recorsets that you DIM'd and forgot to set to Nothing at the end of your loop... yeah, you may have memory leakage or other low system resources. Give it a quick reboot. I know rebooting is a pain. Go get coffee.

Reboot Clean

If you have any other applications that load with Windows (virus scanners, etc.) reboot without them. Run your Access database on a clean, fresh startup. Something else might be interfering with your database.

Google It

Try a quick Google search for your problem. You never know, someone else might have experienced this exact same issue before and has a fix for you.

Try a Backup

Sometimes the problem may be due to something you recently added to your database. SAVE your current database (set it aside, rename it) so you don't lose any data. Then try restoring your most recent backup. If that works, then the problem was caused by something you changed. If that still doesn't fix the problem, try your next oldest backup. That should help you nail down when the bug crept in to your database. 

Try Another PC

Believe it or not, I had a database once that would not work on one specific computer. The client called me in several times and I couldn't figure the problem out. It worked fine on every other machine in the office, and no other application (Word, etc.) had issues. Just my database. Turns out it was a faulty keyboard. For some reason, there was a short that affected Access in some way. No idea why. Replaced the keyboard. Database ran fine. Weird? Yes. But that's technology for ya.

Office Update

Bugs happen. Microsoft is fixing bugs all the time. Sometimes an update creates a bug. The best way to make sure you don't have a problem with a known bug is to run an Office Update if something doesn't seem right. In any Office application, go to File > Account > Office Updates.

Windows Update

If you're sure you have the latest version of Office installed, make sure Windows is up to date too. The two are closely related. Bugs in Windows can cause your database to act weird. It's happened to me. Run a Windows Update. From the Start Button just search for "Windows Update."

Scan for Viruses

If you share or download files, you could have a virus. In which case your system could exhibit any number of odd behaviors. Open "Windows Defender." Make sure your virus definitions are up to date and run a complete scan of your system.

New Database File

Sometimes ACCDB files get weirdly corrupted. Even after a C&R it might not be acting right. Create a blank new ACCDB file and import the misbehaving object(s) into it. If they work, the problem is a bad file. Proceed to import the rest of your objects until you find the culprit.

Remove 3rd Party Components

Your problem might be with a 3rd party DLL, OCX, or other plugin.

Reinstall Office

Sometimes files get corrupted and an Office Update won't repair them because it doesn't know to look for them. I've had bad DLL files before that have wrecked havoc on my system, and everything was up to date. Sometimes you need to completely uninstall Office first, so that everything is deleted, and then reinstall it. Don't just install over an old copy. If you have remnants of older versions of Office on your system, delete those too.

Upgrade Office

I'm not usually someone who pushes "the latest and greatest" upgrade on people. I've always been of a mindset "if it ain't broke, don't fix it." However, sometimes problems with older versions can go away in a newer one. Sometimes they fix things that you might not have known were broken.

Reinstall Windows

Sometimes you might have a corrupted Windows DLL file. You may need to try working from a fresh install of Windows. If you have tried everything else AND your database works fine on another computer, this may be your only option.

Get Help

If you've checked everything off on this list and you still need help with your database, let me know. I try to make myself available as much as possible to answer questions. Your first line of support is the Access Forum. Post your problem there. I try to check them as much as I can, plus Alex and some of the other students help out a lot (and I'm super appreciative of that!). Beyond that, if you need help with your database, FREE help is available via my TechHelp page, and PAID support is available on my Consulting page. If it's business critical, I'm here for you. 

Specific Issues or Error Messages

The above items are for generic "weird" problems that don't always have a specific problem you can pinpoint. The following are some common issues or error messages that may come up and solutions on how to fix them. I'll add to this list as time permits.

Got Questions?

Feel free to post 'em below.


VBA Decompile Upload Images   Link 
Chris Bezant 
4 months ago
You mentioned your trouble shooter process and I would like to add one more thing.
From time to time I get a Bad DLL message out of the blue.
This seems to happen after a long development session. Read More...
Richard Rost
4 months ago
Yes, Chris. You're 100% correct. I haven't needed to use this trick in YEARS, but it did come in handy for me once a while back. I haven't covered this at all, but it would make a good video. Someone else asked me a question about this months ago but I put it on the back burner.
Add a Reply
Other Troubleshooting Ideas Upload Images   Link 
Richard Rost 
6 months ago
Make sure your database is in a TRUSTED folder or is, itself, set as a trusted database. Otherwise VBA code and many macro commands will not run.
Richard Rost
6 months ago
Spelling! Spelling! Spelling! I've seen so many peoples' databases not work because they spelled a field name wrong. If you're getting an "Enter Parameter Value" from a query and you're not expecting it, you've spelled something wrong. If your VBA code isn't working, like an OpenForm command, you've spelled something wrong. Make sure you have OPTION EXPLICIT set in your modules so that Access will flag any variables you haven't declared. This will root out spelling issues too.
Add a Reply
Windows Firewall Exception Upload Images   Link 
Richard Rost 
7 months ago
I have not verified this, but someone I was chatting with in an online Forum said that adding Access to the Windows Firewall Exception list solved a problem he had with Access crashing often.

Start > Control Panel > Security > Windows Firewall > Allow a Program Through Windows Firewall > Add Program on the Exceptions tab. Read More...
Add a Reply

Start a NEW Conversation
Only students may post right now. Click here for more information on how you can set up an account. If you are a student, please LOG ON first.

You may want to read these articles from the 599CD News:

5/14/2021Quick Queries #4
5/9/2021Access D29 Started
5/9/2021Access Developer 30
5/9/2021Access Developer 30 Lessons
5/9/2021Access Developer 30
5/8/2021Data Entry
5/2/2021Split Commissions
4/30/2021Close Form
4/30/2021Close All Forms

Access - index
Excel - index
Word - index
Windows - index
PowerPoint - index
Photoshop - index
Visual Basic - index
ASP - index
Account Login
Online Theater
Lost Password
Student Databases
Change Email
Latest News
New Releases
User Forums
Topic Glossary
Tips & Tricks
Search The Site
Code Vault
Collapse Menus
Customer Support
Web Site Tour
Consulting Services
Affiliate Program
Richard Rost
Free Lessons
Mailing List
Video Tutorials
Learning Connection
Idiot's Guide to Excel
Volume Discounts
Payment Info
Terms of Sale
Contact Info
Support Policy
Email Richard
Mailing Address
Phone Number
Fax Number
Course Survey
Blog RSS Feed    Twitter

YouTube Channel    LinkedIn
Keywords: TechHelp Access debugging troubleshooting page checklist Fix Errors, Problems, Workarounds, Issues, Corruption, troubleshooter  PermaLink