Link to home
Start Free TrialLog in
Avatar of Sandra Smith
Sandra SmithFlag for United States of America

asked on

Can a CDX FoxPro file be opened by another application

I have a client with an old FoxPro application that they want move into either ACCESS or SQL Express.  However, I do not have FoxPro and just need to open the tables, is there a way to convent/move such files?
Avatar of Kanti Prasad
Kanti Prasad

Hi

The below list of programs can open .cdx extensions

http://extension.nirsoft.net/cdx
Avatar of Jeffrey Coachman
You can "Link" the Foxpro tables into Access, and view the contents:
In Access:
External Data-->ODBC-->Link
Click: New
Select the (English) FoxPro Driver
Then select the location of the FoxPro file...
Avatar of Sandra Smith

ASKER

The list did not have what I needed and Jeff, I tried but still does not work.  I think part of the problem is this database is so old that no driver will recognize it.  I an open in Notepad, but it is a jumble and not what I need.
ASKER CERTIFIED SOLUTION
Avatar of Pavel Celba
Pavel Celba
Flag of Czechia 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
Then investigate what Kanti Prasad posted.

As a longshot, see if Excel can open the file.
Thanks, will try what pcelbal suggested.  I did try excel, but there  was no way to parse as the data came in as one long string and whomever created the tables had column upon column with unintelligble names.
Keep in mind that in their infinite wisdom (?), MS deprecated the feature that allowed linking to .dbf files from Access 2013 so you'll need to use an earlier version.
Access never allowed to read pure Visual FoxPro files without VFP ODBC driver. And the ODBC driver causes newer Access versions crash in many cases.

And yes, Access 2013 data engine does not allow to read dBase DBF files any more.

Microsoft is incompatible internally...
I had to dig around and find an old version of ACCESS, both 2000 and 95.  Fortunately, hubby is also a computer network engineer out of NASA and Never throws anything out. (Our garage is a computer museum!)    Based on the information you provided, he was able to get the correct driver and pull the data into SQL Server rather than ACCESS.  It was a trial but finally got the data.  Thank you all for the help and suggestions.  I now have my client's historical data as well as current and can create an application that will really meet their needs.
Great!