We help IT Professionals succeed at work.
Troubleshooting Question

Suddenly getting an error on an Access based program that has been stable for a long time

57 Views
Last Modified: 2020-08-31
The error that suddenly appeared is  

run time error '3049'

cannot open database 'select from [sorted donors] where active = True'. It may not be a database that your application recognizes or the file may be corrupt.

next error message

Class not registered
Looking for object with
clsid:(000000010-0000-oo10-8000-00AA006D2EA4)

How can this error be corrected?
Comment
Watch Question

ste5anSenior Developer
CERTIFIED EXPERT

Commented:
Run a repair installation of Office.
Use a copy of your back Access database.

When the error still occurs, then test whether a newly created database works (create it, close Access, open it). If so, then create a new master database by creating an empty database and import all objects from your old database.
dovidfCEO

Author

Commented:
It seems that Microsoft Office was updated to Office 15. Someone may have tried to use a new version of Office. This seems to be the problem. How should this be corrected?
ste5anSenior Developer
CERTIFIED EXPERT

Commented:
Are you using the same database file in a network using different Office versions?

Then you're probably doomed. At least for shared front-ends. Using a shared back-end works.

You need one front-end copy for each user. You should create/develop it in the lowest used Office version. Depending on the problem behind you need to deploy a second adjusted copy for the newer Office version.
dovidfCEO

Author

Commented:
There is only one active machine and the Office version was changed on it. I don't have multiple versions deployed. Can the error be corrected by going back to an older office version or by some other method?
dovidfCEO

Author

Commented:
In program files only 15 shows up. ln program files x86, office 10 is present. How do I drive the application to use office 10?
ste5anSenior Developer
CERTIFIED EXPERT

Commented:
Okay. Back to the start:

What kind of Access application?
Do you have a split application?
Do you use a local copy of the front-end?
How many users?
What is the Office version of you and the others?
Especially, what bitness?
Did you run an Office repair installation?
Is that Office version complexly patched/updated?
Does your application use special plugins or references?

The error message itself is a strong indicator for a corrupt Office installation. The next possible thing are used, external libraries which were deployed with earlier Office versions, but are no longer part of Office.
dovidfCEO

Author

Commented:
Replying to your questions

What kind of Access application?

d> do you mean what version of Access - 2002 sp3. The main user application is being used by one user on a dedicated machine

Do you have a split application?

d> everything is on one system with only one user

Do you use a local copy of the front-end?

The full interface and data is on a single computer. I used to use replication of input from another system for data input but that stopped some time ago.

How many users?

d> basically one and I sometimes get external data and import it into the active Thsystem

What is the Office version of you and the others?
Especially, what bitness?

d> The online single user system has 10 and 15 was added and is causing the problem 10 is 16 and 15 is 32

d> On the other support computer there are 10, 11, 12, 14, 15

Did you run an Office repair installation?

d> No

Is that Office version complexly patched/updated?

d> The office versions aren't patched to my knowledge

Does your application use special plugins or references?

d> not to my knowledge

The error message itself is a strong indicator for a corrupt Office installation. The next possible thing are used, external libraries which were deployed with earlier Office versions, but are no longer part of Office.

d> I believe the unintentional install of 32 bit windows 15 on the main entry system caused the problem

I would like to back up the main entry system to uninstall the 32 bit version of windows and see if that solves the problem
ste5anSenior Developer
CERTIFIED EXPERT

Commented:
Okay, sounds like a mix of problems.

But I have to admit that I don't entirely understand why or how your user is using different Office versions at the same time..
Also your Office environment mentioning Access 2002 up to 2015 sounds weird.

Can you rephrase and elaborate those points?

In general it sounds like you should provide a clean OS with a clean Office installation.
dovidfCEO

Author

Commented:
I've discovered that Microsoft has made some changes that clobbers Access
Here is a detailed article with fixes
https://www.devhut.net/2019/11/14/access-bug-error-3340-query-is-corrupt/

ste5anSenior Developer
CERTIFIED EXPERT

Commented:
Yup, but I assumed that you have an updated version of Access.

But your error message does not come from that bug.
dovidfCEO

Author

Commented:
I found that I can't get into Access on an older machine with a different error which may be covered by the ones in the article. 
ste5anSenior Developer
CERTIFIED EXPERT

Commented:
No. The mentioned link is about the November update, which crippled all affected Access 2016+. But it was fixed.

Did you recreate the file? Does it throw the same error on the affected machines? Then you can exclude corruption, then it is indeed an installation problem.
dovidfCEO

Author

Commented:
I've solved the problem on one computer based on the following article by Developers Hut

https://www.devhut.net/2020/08/17/access-bug-mdb-jet-broken-by-latest-round-of-updates/

The latest windows update clobbered older Access and reversing the update cleared up the problem
ste5anSenior Developer
CERTIFIED EXPERT

Commented:
Are you running your application as *.mdb file?
dovidfCEO

Author

Commented:
There is a front end visual basic program and there are also functions done in mdbs

CEO
Commented:
This problem has been solved!
(Unlock this solution with a 7-day Free Trial)
UNLOCK SOLUTION