The Microsoft Jet database engine could not find the object 'Databases'. Make sure the object exists and that you spell its name and the path name correctly.

how can I edit the file? I subscribed, because the system said: pay for solution, and I did, but I don't see the solution anywhere.

Again, I'm trying to open an access file, and I get this error message:

The Microsoft Jet database engine could not find the object 'Databases'.  Make sure the object exists and that you spell its name and the path name correctly.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Sounds like you are linking the access file to another access mdb (backend). Try opening a table, if you cant, you need to locate the access backend and relink the tables to it. Make sure you use the network path if it is not locally stored.

If you do not even get to the databasewindow, what i assume from your desription
this error message may indicate some serious problem with the internal system tables.

what you can try:

make a empty new database

try to import the objects of the damaged database into this new database
in the first menu ("file") the third entry("external data") first entry ("import")

Regards, Franz
Maybe you should show us exactly how you are calling your database.  
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

dkaplan435Author Commented:
Problem solved. I tried all the above suggestions, none of them worked. I purchased a program called AccessRecovery 2.2 and was able to save the file.
jadedataMS Access Systems CreatorCommented:
No comment has been added lately, so it's time to clean up this TA.
I will leave the following recommendation for this question in the Cleanup topic area:

PAQ with points refunded

Please leave any comments here within the next seven days.

EE Cleanup Volunteer
PAQed, with points refunded (500)

EE Moderator

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Just a note on this kind of problem: "Beware of the non-alphabetical characters"

It seems that if there is a dot within the filename (NOT related to the extension of the file) like 'part1.part2.extension', Access refuses to digest it and you would  get the above error message. This kind of problem is very typical when you move a file from a unix environment, where any character is admissible within a name, into a windows workspace, where the rules are not very consistent.

An easy work-around is to substitute the dot ('.') with an underscore ('_') and to import the file using the new filename.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.