The aim of this work is to show our ability to work with different Microsoft applications & to produce the data exchange between them, using build-in commands, OLE instruments & other possible facilities.
In the practical examples we will show the data transfer process using the following Microsoft Applications: FoxPro, Excel & Word.
Also it is necessary to present the theory about the data transfer for it is impossible to use all of them in the examples.
2. Theory part.
There are several different ways to transfer data from FoxPro to different Microsoft Applications & vice versa.
2.1. Built-in FoxPro commands.
Operator can use several built-in commands of FoxPro such as Export, Import, Copy and Append from.
Now we would like to present some helpful information about these operands.
Use EXPORT to use FoxPro data in other software packages.
If the table/.DBF you are exporting from is indexed, the new file created is created in the indexed order.
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.
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.
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.
If the WHILE clause is included, records are copied to the new file for as long as the logical expression evaluates to true (.T.).
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
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.
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 .
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 .
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.
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.
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.