Foxpro for DOS icon Visual Foxpro 6 icon Visual Foxpro 9 icon

Converting from Foxpro

Types of files often used by Foxpro

When browsing folders on your computer, you will want to see the file extensions. By default, Windows hides extensions of files whose types are known to Windows. To see the file extensions in a folder, click the Organize pulldown, then select "Folder and search options", the View tab, UNcheck "Hide extensions for known file types". Your version of Windows may be a little different.

Files containing application data

These are files you are likely to see in your application data folder.

.DBFData file for one table
You are likely to have one or more of these.
.CDXCompound index file for a specific table, not always present
.IDXSingle index file for a specific table, not always present
.FPTMemo file for a specific table, not always present
.DBC, .DCX, .DCTDatabase container and associated files
Some applications do not use these.
OtherIf you see other files types in your application folder, ask us.

Project source files

These are files that might be required to compile your application. Normally, a vendor does not provide these. However, some vendors include source files for custom applications.

.PRGProgram source code file
.HHeader source code file, gets included in other types of source files
.SCX, .SCTScreen layout and source file
.FRX, .FRTReport layout and source file (except for labels)
.LBX, .LBTLabel layout and source file
.MNX, .MNTMenu layout and source file
.VCX, .VCTClass files, may contain screens and source code
.PJX, .PJTProject files to control application creation
.QPRQuery program

What good will it do if you have any of these files? For one thing, the availability of source files will ease the process of reconstruction your application in a new implementation. In addition, some of the conversion process might be automated. It must be noted that the syntax and semantics of the Foxpro programming language are very different from those of other programming languages. There is no "export" or "import" available to make a conversion completely automatic. Similarly, the screen (form) and report layout files are structured differently from the corresponding files for other systems. Therefore, any conversion is going to be labor-intensive. Nevertheless, it may be possible to partially automate some file conversions. Annotations inserted into the output files would indicate where manual modifications are required.
Copyright © 2016, Express Software Production
Last Reviewed or Updated: November 28, 2016