I have been using ODBC with Foxpro for years, and all has been well. Looks like I need to bite the bullet and go to OLE DB and I am clueless. I am using Access 2007 with mdb's. Any help/direction is appreciated. TIA!

-JS

What are you linking to?

Foxpro free table directory dbf's.

-JS

Foxpro free table directory dbf's.

-JS

So why do you think you have to change the way you're connecting? Did the company say you can't use an ODBC DSN?

Today I looked at a linked table and half the field names don't match the table structure. They don't look like garbage, but don't make sense either. I also understand OLE is the way o go, and ODBC is not recommended, although I have never hand a problem.

JS

Today I looked at a linked table and half the field names don't match the table structure. They don't look like garbage, but don't make sense either.
Are you sure you're using the correct ODBC driver for the version of FoxPro files you have?

I also understand OLE is the way o go, and ODBC is not recommended,

Would be interesting to know where that came from. I've not seen that.

I am using the last release of the Foxpro driver. I have sent an email to the author of the Foxpro tables explaining what I have seen.

From MSDN:
Visual FoxPro ODBC Driver
Please note that the VFPODBC driver has very limited product support. It is currently supported only for Windows 2000, however we strongly recommend using the Visual FoxPro OLE DB provider instead.

And MS
http://support.microsoft.com/kb/277772

Anyways, ODBC has been kind to me over the years and I'll stay the course if I can.

-JS