Linked Table Manager - MS Jet Engine Can't Find the File

[Robert T]

I don't understand why Access developers making simple things so difficult.
On my old computer, I linked Access tables to my Alpha Five data files [dbase
format]. On another computer, the links no longer work so I tried to rebuild
them. However, when I click on the tables in Alpha Five, an Access message
pops up stating the MS Jet Engine can't find the object. Even though I'm
clicking in the table name, the message still pops up.

I had the same problem on my other computer and I think downloading the
Borland DBE resolved it. However, now I can't find the file to download. I
went to Borland's site, the link's there, but the file isn't.

Anyway, can someone please explain why MS makes linking tables so difficult
and how I can resolve this issue?

Thanks,
Robert

 

[jacksonmacd]

Not sure if this will help, but... I have found that Access refuses
to link to DBF files unless they are named in 8.3 format. In other
words, the filename itself is limited to 8 characters and the
extension is limited to 3 characters. For longer filenames, Access
issues a "cannot find file" error message.

*Why* this archaic limitation continues to exist is another question!

I don't understand why Access developers making simple things so difficult.
On my old computer, I linked Access tables to my Alpha Five data files [dbase
format]. On another computer, the links no longer work so I tried to rebuild
them. However, when I click on the tables in Alpha Five, an Access message
pops up stating the MS Jet Engine can't find the object. Even though I'm
clicking in the table name, the message still pops up.

I had the same problem on my other computer and I think downloading the
Borland DBE resolved it. However, now I can't find the file to download. I
went to Borland's site, the link's there, but the file isn't.

Anyway, can someone please explain why MS makes linking tables so difficult
and how I can resolve this issue?

Thanks,
Robert

 

[Douglas J. Steele]

My understanding is that Microsoft didn't write the drivers to connect from
Access to Borland: that it's a Borland limitation.

Fortunately, it's pretty easy to convert a long file name to a short file
name. See http://www.mvps.org/access/api/api0020.htm at "The Access Web"

--
Doug Steele, Microsoft Access MVP

(no private e-mails, please)

Not sure if this will help, but... I have found that Access refuses
to link to DBF files unless they are named in 8.3 format. In other
words, the filename itself is limited to 8 characters and the
extension is limited to 3 characters. For longer filenames, Access
issues a "cannot find file" error message.

*Why* this archaic limitation continues to exist is another question!

I don't understand why Access developers making simple things so
difficult.
On my old computer, I linked Access tables to my Alpha Five data files
[dbase
format]. On another computer, the links no longer work so I tried to
rebuild
them. However, when I click on the tables in Alpha Five, an Access message
pops up stating the MS Jet Engine can't find the object. Even though I'm
clicking in the table name, the message still pops up.

I had the same problem on my other computer and I think downloading the
Borland DBE resolved it. However, now I can't find the file to download. I
went to Borland's site, the link's there, but the file isn't.

Anyway, can someone please explain why MS makes linking tables so
difficult
and how I can resolve this issue?

Thanks,
Robert

 

[Robert T]

Hey Guys:

It had nothing to do with the short name files because one of the 2 files I
was trying to link up with just happened to have 8 letters + a 3 letter
extension [.dbf]. The solution was finally finding a copy of the Borland
Database Engine and downloading it to my computer. As soon as I did that,
everything worked perfectly.

Thanks for your input,
Robert