• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1291
  • Last Modified:

Importing Custom FoxPro 2.10f Database into Access 2003

Hi-
A friend of mine has a custom program written about 15 years ago based on Fox Pro 2.10. I assume it's 2.10 because when I start up FoxDoc (the only FoxPro program that works right now on my DOS emulator) it says "Version 2.10f". As a sidepoint when I try to open the main FoxPro file (fox.exe or foxpro.exe) the command prompt tells me "EXE and OVL file do not match".

Anyway, I need to figure out how to import the data fom this database into Access. What files am I looking for? There is no export function in the custom database, but the data has to be stored somewhere on the HD.

Would it be one file or many files (1 for each table)?

Any help would be greatly appreciated.

Thanks,
Daniel
0
DanielHochman
Asked:
DanielHochman
  • 4
  • 2
  • 2
  • +1
1 Solution
 
TimCotteeHead of Software ServicesCommented:
Hi DanielHochman,

The first thing to find are the .dbf files. These should be individual tables, there will also be .ntx files which are indexes for the tables though you probably won't need to worry about these. You can then create import or linked tables in access using the dBase IV odbc driver.

Tim Cottee
0
 
DanielHochmanAuthor Commented:
I found many .dbf files. When I try to import any of them into Access it tells me "Index not Found". What is dBase IV odbc driver?

Thanks,
Daniel
0
 
TimCotteeHead of Software ServicesCommented:
DanielHochman,

It is possible that you also have .mdx files which are a compound index file and would normally have the same name as the base .dbf file. When you import into access you would need to specify the location of the compound index file so that access can use this.

The dBase IV odbc driver is one of the available options when you select files to import, you usually have Excel files, csv files, dBase III, dBase IV etc and "odbc data source" as options. The best if you have it is to create an Odbc datasource using the Microsoft Visual Foxpro driver though this is not always available by default.

Tim
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
DanielHochmanAuthor Commented:
I was able to import some .dbf files but none I think I need. The others say "No Index Found" I was not able to find any .mdx or .ntx files - I did a complete search of the HD.
Some of the files I was able to import came up as gibrish (this might be because some of the databases were written in a foreign language (Hebrew). I don't know if you would know how to fix that. It's also possible they were imported wrong.

If you have any suggestions about the "No index found" let me know.

Thanks,
Daniel
0
 
CarlWarnerCommented:
FoxPro never used .ntx files for index files.  So, don't look for them.  And FoxPro never supported .mdx type files that have multiple tags in them.  That was a dBASE IV thing that FoxPro never had in it.  As far as index files in FoxPro, FoxPro at that stage used .idx files.  Look for any .idx files that generally, but not always, have the same file name (without extension) as the dbf files.  Also, if there are any .fpt files present that match dbf file names without the extension, pull them along.  Those are the memo files that get created when a memo field is part of the structure/scheme in FoxPro.  You shouldn't be able to open a dbf that is supposed to have a memo file if the .fpt file is missing.

And don't bother using a dBASE IV ODBC driver.  Just go ahead and use the freely download VFP ODBC driver from MS here:

Visual FoxPro ODBC Driver
http://msdn.microsoft.com/vfoxpro/downloads/updates/odbc/default.aspx

ACCESSING YOUR VFP DATABASE IN ACCESS
http://www.foxite.com/articles/032.htm
0
 
DanielHochmanAuthor Commented:
I've done a complete search for .idx and .fpt files and have come up empty. Not one on the whole HD. I have found some .cdx files with the same name as my .dbf files. Are these indexes? If so, how do I tell access that these are the indexes when importing.
Also, the FoxPro database does have memos attached. Is there another possible file type besides .ftp that these could be?

Thanks,
Daniel
0
 
DanielHochmanAuthor Commented:
Oh I did find the fpt files.- I was accidentally searching for .ftp...
0
 
CarlWarnerCommented:
Yes, .cdx files are legitimate for FoxPro.  Unfortunately, I didn't mention them before because I couldn't tell which version of FoxPro you had.  The version you listed was really for FoxDoc and not for FoxPro.  If you do have .cdx files, those are differently the newer index file types than the older .idx ones that actually are still supported.  Both types are still supported even in today's VFP9 version.

Just be sure to have the .cdx files and the .fpt files in the same folder as the dbf files.  If the .cdx file types are the same filename as the dbf file names, by default they get opened with the dbf when a request is made to open the dbf.  The VFP ODBC driver should be able to automatically take advantage of that arrangemernt if it exists.
0
 
rabeeCommented:
Its simple in Visual basic. In VB you can read/write to both foxpro and access. Try reading from Foxpro and insert to access. But if you are having many files it is a lengthy process because of foxpro file is having a diffrent structures.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

  • 4
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now