I have a DB Written in Visual FoxPro. How do I import the Data into FMP?
terrific! you should mark an answer as correct, even if you own, so others will know.
Thank you for your post!
If FoxPro can export to a Format FileMaker can Import then you can check out Importing Data into either an Existing or New FileMaker Pro file.
Edit: You might also check out the ODBC/JDBC Guide.
I hope this helps!
Doesn't Fox Pro use DBF file format?
Does FMP 15 still support imports from that format?
If so, you can import directly and not have to export to something such as CSV, Tab or Text format before importing.
I wondered the same thing, Phil!
Heed the warnings on this and other import formats.
Here are all the formats possible with FM (natively):
(html table exports only)
I don't know if there are any plug-ins or if ODBC (the Visual FoxPro as source) can be used.
One way is to do as mentioned and export from Visual FoxPro and import into tables in FileMaker.
But since FileMaker and Visual FoxPro both support ODBC https://msdn.microsoft.com/en-us/library/ms710251(v=vs.85).aspx you can also set up FoxPro and FileMaker to talk directly with each other.
If the goal is to move the solution/data to FileMaker as a one time process, then I would take the export/import approach. If it is an ongoing process, transferring transactions or something like this, I would go for the ODBC connection.
If possible, let us know what your aim is. A one time transfer or an ongoing sync of one or more tables from one database to another?
It may be a good idea to move the data to a new solution in FileMaker. Foxpro was taken over by Microsoft, renamed Visual FoxPro, and is discontinued. The final version came out in 2010.
Thanks to all.
I talked to FileMaker Help Desk who said that it appeared that Visual Fox Pro was a DB2 not DB3 or 4 file and wasn't supported by FileMaker.
i haven't been able to find any ODBC drivers for the Visual FoxPro. MicroSoft doesn't have any and pointed to several firms who would sell the drivers, but they didn't seem to be in the business any longer.
can you export as CSV?
Beverly's question about CSV or other table export formats are very relevant.
But the question is still: What is your purpose?
One time, many times, continuously?
And even though Visual FoxPro is a long time dead product and not supported you will probably be able to get help from other FoxPro users to get the drivers. But the main question first:-) what do you want to achieve?
The purpose is to transfer the VFP data into a more useable format.
I have tried to use MS Excel (Mac 2016.)
I tried using MS Access on a Windows Machine.
The data is public data on the electric utility industry collected by the Federal Energy Regulatory Commission. Their IT Department has suggested using MS Access, but the drivers don't load from the MS Web site (you need to have a previous version of VFP to get the drivers -- yes it's very much a circular logic)
So from this I assume that it is a one time export and then the Visual Basic solution is not going to be used again. The data will be used in a new solution in FileMaker.
From FileMaker it is very easy to export to nearly any format, but it is a little bit more tricky from VFP, but it is indeed possible:
FoxPro to CSV Converter is a tool to Convert, Migrate data from FoxPro DBF files to CSV / Delimited Text Files
And you can find other ways of doing it here
I hope it is OK that I ask questions like this:
If not, you may need some help for an hour or two setting up the imports.
The help you need to import into FileMaker you can get here, when you have the data out of VFP, that's a pretty easy task.
Is it OK to ask a few extra questions?
Filemaker 15 does support importing DBF files. Visual Foxpro should be either DB3 or DB4 as Foxbase+ (DOS predecessor) was DB3 according to this MS site Table File Structure (.dbc, .dbf, .frx, .lbx, .mnx, .pjx, .scx, .vcx)(Visual FoxPro Error Message)..
I just tried a version 0x03 Foxbase+ file i have laying around and FM15 imports it fine. I do know from past experience that FM13 had a small problem with DB4 files that had a separate memo file (.DBT). It seems that after the first carriage return in the memo it interpreted the following ones as two. I remember doing some research and this was a know issue. I don't know if it was ever corrected. In this case I used LibreOffice Calc to read the DBF which also pulled in the attached memo as a separate column. I then exported it as an Excel file and imported it which worked fine.
Feel free to contact me if I can be of more assistance.
In the '90s I had a Mac version of VFP, which is no longer functioning under the most recent MasOS.
Most of my experience was taking the DBF files and converting them to XLS.
I don't have any real experience with FMP.
For each yr ( and there are 20 years) there is a zipped file containing the VFP DB of 100 or so US Electric Utilities with around 70 DBF files/tables.
Some of the suggestions contained in this thread sound useful.
Visual FoxPro does not have a working ODBC driver from MS. And, unlike SQL Server, MS does not supply a JDBC driver for the now-defunct (no longer supported in any way from MS) Visual FoxPro.
When I did exactly what the OP wanted to do, I purchased a third-party JDBC driver and did the sync using Java. Another problem you'll have with Visual FoxPro are the MEMO fields and getting that data. The third party driver worked perfectly here too. CSV files are not a solution for some of the data that might be in MEMO Fields.
This third-party driver works both with tables in the DBC (database container) as well as free tables (DBFs).
(I also got the Visual FoxPro into MySQL, which turned out to be a better solution for the queries we needed to do - RegEx and on large tables with sub-second query performance.)
HOPE THIS HELPS.
The easiest and cheapest solution (as in free) is to download LibreOffice for your system, open the DBF with Calc and export it to an Excel spreadsheet with the memo fields which you can import into Filemaker. I've done this so I know it works.
I'd be happy to test one of your zip files if you have doubts.
Your technique might work for simple "Standalone" DBFs, but I am not sure about tables that are part of a Visual FoxPro DBC as that has a different header format.
Have you tried this technique with Visual FoxPro DBC tables -- tables that are part of a Visual FoxPro database container? Unless you have a ancient "dBase" or "FoxPro" application, a DBC is the most common case for Visual FoxPro as it brings nice things like long field names, and other DB cool stuff.
I've played a little with Foxpro many years ago but what little I was just able to dig out on the web it sounds like it's a database container similar in some respects to Access' MDB but I'm not sure. Probably won't work with LibreOffice but it can't hurt to try. I have LibreOffice on my Mac. Happy to test it for you.
Worse comes to worst I'll dig out my old VFP disc and install in one my virtual Windows machines and get the data for you.
I was a VFP developer for over 10 years and still use it for a client (v. 9, the last ever version).
Exporting MEMO files is difficult in VFP. DBC-contained tables (the norm) makes things more difficult. The fact there is no working ODBC driver makes this virtually impossible from my research.
Using the third-party JDBC driver, and a little JDBC code in Java, it was simple and quick to copy the VFP data (both contained DBC table data and "free" table data) to both FileMaker and to MySQL.
Much Thanks Beverly!
Used LibreOffice and it was a miracle.
Thanks to All of you.
Beverly's suggestion (along with VIncedubeau) to use LibreOffice got me to read/write the DBF data into XLS format.
Now I have about 500++ hrs of work to get 20 years of data into xls then FP.
Trying to import a "contained" DBC table did not work correctly in LibreOffice, but it just seemed to be mainly the header row (column names also included the C 10, for example). A bigger problem I had when testing this was that, on a 16 GB RAM machine, LibreOffice crashed with only a moderate-sized DBF (200K rows). Very small tables imported OK. Another test with a 450K table with MEMO fields also crashed. After clicking import, there was just the gray screen in LibreOffice until memory was exhausted. Such is the way of import wizards I guess... (I am using LibreOffice 188.8.131.52).
(Using the Java/JDBC approach, once you write the basic code, the import for both contained DBFs and free tables works with any size table I've tested (500K rows max I've tested) and is completely automated -- no crashes or memory exhaustion -- and completes in less than one minute!)
Retrieving data ...