Contest, Детальна інформація

Include the name of the file to which FoxPro exports data.  If you do not include an extension with the file name, the default extension for the specified file type is assigned.

FIELDS

Include FIELDS to specify which fields are copied to the new file.  If the FIELDS clause is omitted, all fields are copied to the new file.  Memo and general fields are not copied to the new file even if their names are included in the field list.

The scope clauses are:  ALL, NEXT , RECORD , and REST.  These are explained in the Overview of the FoxPro Language chapter in the FoxPro Language Reference.  Commands which include operate only on the table/.DBF in the active work area.

You can specify a scope of records to copy to the new file.  Only the records that fall within the range of records specified by the scope are copied to the new file.

The default scope for EXPORT is ALL records.

FOR

If the FOR clause is included, only records that satisfy the logical condition are copied to the new file.  Including the FOR clause lets you conditionally copy records, filtering out undesired records. 

Rushmore optimizes an EXPORT ... FOR command if is an optimizable expression.  For best performance, use an optimizable expression in the FOR clause.  A discussion of Rushmore optimizable expressions appears in the Optimizing Your Application chapter in the FoxPro Developer's Guide.

WHILE

If the WHILE clause is included, records are copied to the new file for as long as the logical expression evaluates to true (.T.).

NOOPTIMIZE

To cause Rushmore not to optimize EXPORT, include NOOPTIMIZE.  For more information, see SET OPTIMIZE and the Rushmore discussion in the Optimizing Your Application chapter of the FoxPro Developer's Guide

.

TYPE

You must specify the type of file to be created.  The TYPE key word is optional, but you must specify one of the following file types.

DIF

When you specify DIF, each field from a FoxPro table/.DBF becomes a vector (column) and each record becomes a tuple (row) in a DIF (Data Interchange Format) file, used by VisiCalc.  The new file name is assigned a .DIF extension if an extension isn't included in .

MOD

Use the MOD clause to export to a file in Microsoft Multiplan version 4.01 MOD format. The new file name is assigned an .MOD extension if you don't include an extension in .

SYLK

A SYLK file is a Symbolic Link interchange format (used by Microsoft Multiplan) in which each field from a FoxPro table/.DBF becomes a column in the spreadsheet and each record becomes a row.  By default, SYLK file names have no extension.

WK1

Include this option to create a Lotus 1-2-3 spreadsheet from a FoxPro table/.DBF.  A .WK1 extension is assigned to the spreadsheet file name for use with Lotus 1-2-3 revision 2.x.  Each field from the table/.DBF becomes a column in the new spreadsheet, and each record in the table/.DBF becomes a spreadsheet row.

WKS

A Lotus 1-2-3 spreadsheet can be created from a FoxPro table/.DBF with this option.  A .WKS extension is assigned to the spreadsheet file name for use with Lotus 1-2-3 revision 1-A.  Each field from the table/.DBF becomes a column in the new spreadsheet, and each record becomes a row in the spreadsheet.

WR1

Include this option to create a Lotus Symphony spreadsheet from a FoxPro table/.DBF.  A .WR1 extension is assigned to the spreadsheet for use with Symphony version 1.01.  Each field from the table/.DBF becomes a column in the new spreadsheet, and each record in the table/.DBF becomes a row in the spreadsheet.

WRK

A Lotus Symphony spreadsheet can be created from a FoxPro table/.DBF with this option.  A .WRK extension is assigned to the spreadsheet file name for use with Symphony version 1.10.  Each field from the table/.DBF becomes a column in the new spreadsheet, and each record in the table/.DBF becomes a row in the spreadsheet.