dkaplan435
asked on
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.
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.
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
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.
ASKER
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.
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.
PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!
jadedata
EE Cleanup Volunteer
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.
PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!
jadedata
EE Cleanup Volunteer
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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 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.
syntnx