cannot link Foxpro file as table, access2000

[dgm]

I have to fix a screwy access database made a long time ago. It has a linked
table going to a DBF file. The connect string for the table is:

ODBC;DSN=Visual FoxPro
Tables;SourceDB=\\DPH53501\VOL1\Unitdata\Central_Ops\FCM Cornerstone
Reports\FCMData;SourceType=DBF;Exclusive=No;BackgroundFetch=Yes;Collate=Machine;Null=Yes;Deleted=Yes;

The user receives an email attachment and saves the attachment at the
designated path. The attachment is an Excel spreadsheet with file extension
xls, but is renamed and saved as dbf. I don't know what process is used by
the sender and whether it's really made as an Excel spreadsheet or Foxpro
file.

Things worked a long time, but the file format has changed to have different
columns. Personnel changed, too. Whoever linked the table isn't here anymore.

When I try to make a new link I'm unable. If I use dbase (dbf file type)
III, IV, or V it says I have to have an index table, too. There is no index
table associated with the previous linked table, so that probably isn't
right. If I try to use ODBC as indicated in the previous connect string,
there are Foxpro files, Foxpro tables, and Foxpro database, as options in the
dropdown and none of them work.

If I try to use Excel or "Foxpro files", I get a message saying "you cannot
use ODBC to import from, export to, or link an external Microsoft Jet or ISAM
table to your database". Possibly I should be able to use one of these and
this is an install or configuration issue.

How can I tell what the attachment is? Excel will open it. The dbf file type
is associated with Excel on this machine.

Help would be appreciated.

 

[dgm]

As mentioned, Excel will open the file I need to link to, so I opened with
Excel and clicked "save as" to see if it would show me what type file. The
type suggested was DBF4 (dbase IV) (*.dbf). I have Excel 2003. My Access is
2000, though.

So I went to the Access DB and attempted an import instead of linking and
chose dbase IV as the gfile type. That worked instantly and the table created
had the correct column names.

So why won't it link if it will do an import?

 

[dgm]

After doing the import I deleted the table then tried to link again. I chose
dbase IV as the file type. When the index prompt appeared to select an
associated index file I clicked cancel. And it created the link. What's the
deal? I'm going to reboot and try again in case something was being cashed.

 

[dgm]

The problem appears to be the path being used. If I attempt to link the file
using the UNC path on the LAN I get a dialog asking for an index file and
when clicking cancel it says:

" is not a valid name. Make sure that it does not include invalid characters
or punctuation and that it is not too long.

When I was able to link the file before I did so from the desktop and used
dbase IV as type. The same index dialog appeared, I clicked cancel, and no
problem.

After linking the file from the desktop I used linked table manager and
relinked to the LAN. It said the relink was successful, but when I tried to
open the table I got the invalid file name error shown above.

So I am using dbase IV and not Foxpro, though the original link is Foxpro. I
guess the file will work with either one except for the LAN problem observed.
But I am unable to create a Foxpro link.