Link to home
Start Free TrialLog in
Avatar of Seb
SebFlag for United States of America

asked on

the microsoft jet database engine cannot open the file <File Name> make sure it exists and that its name is spelled correctly

Hello Experts,

Firstly let me just say that I'm a novice at best with Access so please try to make the explanations more detailed than usual.

Now to the issue at hand.

I have an Access database that has a link to a central database off site.  All has been working well and recently we did an update to the Data Source Connection and all worked OK for the last 2 months and now when the user tries to access the database on the computer and run a query the following message comes up "the Microsoft jet database engine cannot open the file dbo_prospect make sure it exists and that its name is spelled correctly"

I've rebooted the server, ran a chkdsk and looked for answers online but have not been able to find a resolution. I did find this from Microsoft ( http://support.microsoft.com/kb/287696 ) but as I mentioned before I'm a novice w/ Access so this was of no help to me.
I've also added the image of the error in case it's needed.

Any help would be appreciated and thank you in advance.

Sebastian  User generated image
ASKER CERTIFIED SOLUTION
Avatar of RemRemRem
RemRemRem
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Seb

ASKER

Thanks for the quick reply, I'll test it today and will get beck to you.
Avatar of Seb

ASKER

Hello again RemRemRem,

Followed your steps and your recommendation to  "check the server to see if the table called Prospect is actually ON that server location." found me the problem.  IT turns out that the dbo_Prospect table was not Linked since the last update of the database. Once I reconnected it  it all came back to normal.
Thank you so much for your help. It is appreciated.

Sebastian
Avatar of Seb

ASKER

Followed recommendation to  "check the server to see if the table called Prospect is actually ON that server location." found me the problem.  IT turns out that the dbo_Prospect table was not Linked since the last update of the database. Once I reconnected it  it all came back to normal.