1. Import (if necessary) the description of the xBase/FoxPro data files into the WINDEV or WEBDEV analysis.
2. Program with the HFSQL functions of WLanguage.

The import steps

1. In the data model editor, launch the import wizard: in the "Análisis" pane, in the "Creación" group, pull down "Importar" and select "Import file/table descriptions".
2. Select database type: xBase. A connection to the xBase/FoxPro database is automatically established and associated with the data files imported into the analysis. This connection will have to be used to handle the xBase/FoxPro data file programmatically.
3. Specify whether the data must be kept in the current format (option required to use the Native xBase/FoxPro Connector).
4. Select the data file access mode (xBase Native Connector for WINDEV) and specify the data file directory.
5. Select the tables that will be imported into the WINDEV analysis. These tables can be handled through programming with the HFSQL functions of WINDEV. These tables will be displayed in blue in the data model editor.
   Note: the FoxPro databases (.dbc extensions) are not supported. Each data file (.dbf extension) must be individually imported into the analysis.
6. Validate. The tables are imported into the analysis. In the description of the data files, you will find the xBase subtype of the imported data file (dBase3+, dBase4, FoxPro/FoxBase, Clipper5, Clipper87).

• An item defined as Numeric in FoxPro can be imported as currency into WINDEV and WEBDEV (if the size of the item exceeds the size of a real for example).
• The Logical items in xBase/FoxPro are imported as Text items. Indeed, for a boolean in xBase, you have the ability to specify True and False with the 'T' and 'F' strings.

Taking into account the changes of the xBase/FoxPro data files

• analyze the differences for the imported tables,
• analyze the differences for all the xBase/FoxPro tables.

New features for managing the xBase/FoxPro data files

• Managing an automatic identifier.
• Ability to use HIndex.
• Management of expressions in HFilter.
• Ability to use HChangeDir.
• Using the native xBase access with non-Latin character sets.

• Support of memos in VFP format.
• All the index formats are supported (including the indexes in VFP format corresponding to the .CDX extension). The indexes are read and modified.
• Managing an automatic identifier.
• Management of expressions in HFilter.
• Ability to use HChangeDir.
• Limitation: FoxPro files cannot be reindexed.
• Limitation: it is not possible to create a FoxPro file.

Dynamic description of an xBase data file

// Describe an xBase data file with the following items:
// LASTNAME, string of 20 characters
// FIRSTNAME, string of 20 characters
// AGE, integer on 3 digits
// BALANCE, real on 10 digits and 2 decimals
// MARRIED, boolean
// DOB, date
// INFO, text memo

HDBDescribeFile("DBCUSTOMER", "CD", "C:\FILE\CUSTOMER.DBF")
HDBDescribeField("LASTNAME,C,20")
HDBDescribeField("FIRSTNAME,C,20")
HDBDescribeField("AGE,N,3,0")
HDBDescribeField("BALANCE,N,10,2")
HDBDescribeField("MARRIED,L")
HDBDescribeField("DOB,D")
HDBDescribeField("INFO,M")
HDBCreation()

Opening data files described dynamically

Opening indexes that were described dynamically

Links between the xBase or FoxPro data files

// Read the orders
HReadFirst(ORDER, Ord_Date)
IF HOut() = False THEN
	// Find the corresponding product
	HReadSeek(PRODUCT, ProNum, ORDER.ProNum)
	FileToScreen()
END

Using the Native xBase/FoxPro Connector with non-Latin character sets

1. In the initialization code of the project, add the code used to modify the character set:
   

   ChangeCharset(charsetChinese)

2. Create an xBase connection:
   

   HDescribeConnection("CntxBase", "", "", fExeDir(), "", hNativeAccessXBase, ...
   		hOReadWrite, "OEMTOANSI=WINDOWS;")
   HChangeConnection("*", "CntxBase")