Problem with a linked database

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Recently, I got a call from one of the offices I support and they told me
that they had gotten a message on screen saying that the database their
application was linked to could not be found. On further investigation I
found that when I logged into the front end application I also got a message
saying that the back end data could not be found. I went into Access to
relink the tables and when I drilled down to the folder where the database is
to be it was not shown in the dialog form. I decided to look in the folder
from explorer to look for the database should it just have been moved. But I
dicovered that the back end was actually in the correct folder and that
Access was not showing the correct files in the dialog. I moved the back end
file to another folder and it linked up fine in Access. But a day or so ago I
once again got a call saying that there was a message that the back end
database could not be found.

Any ideas what has happen to the front end and back end to result in this
error and why access can't see the file?
 
front end / back end is not a good solution

it is much more reliable to move to SQL Server and Access Data Projects



Seriously; sorry-- Microsoft states in multiple places that 'JET has been
obsolete for a decade'
 
I expect ultimately that this application will be replaced with an ASP front
end and a SQl backend. But I inherited this program and until the replacement
is finished I have to support this program.

So this is a jet issue?
 
Hi Cameron,

Don't worry too much about Aaron: he seems to have far more problems
with Jet than any other hundred thousand users put together.

I have vague recollections of this sort of thing being reported in
connection with Novell networks and long paths or deeply nested folders
or some such. What version of Access are you using? What operating
systems do you have on the workstations and the network?
 
Back
Top