Hi Mike,
Copy&Pasted from the VFP 8 bèta documentation:
In the Visual FoxPro Documentation
What's New in Visual FoxPro 8.0
Describes the new features and enhancements included in this version of Visual FoxPro.
Data Features Enhancements
Describes additions and improvements to Visual FoxPro data features.
Automatically Incrementing Field Values
You can now increment field values automatically for both DBC tables and free tables using the new autoincrementing feature in Visual FoxPro. You can use the AUTOINC clause in the CREATE TABLE SQL and ALTER TABLE SQL commands to specify values for NEXTVALUE and STEP. You can also select the Integer (AutoInc) data type for a field and set values for the Next Value and Step fields in the Fields tab in the Table Designer. For more information, see CREATE TABLE - SQL Command, ALTER TABLE - SQL Command, Fields Tab, Table Designer, Autoincrementing Field Values in Tables, and Setting Autoincrementing Field Values.
The AFIELDS() function now returns 18 columns instead of 16 due to new support for autoincrementing field values. Column numbers 17 and 18 now specify the NextValue and Step fields, which contain values of Numeric (integer) type. For more information, see AFIELDS( ) Function.
The COPY STRUCTURE EXTENDED command adds the numeric FIELD_NEXT and FIELD_STEP fields to support autoincrementing. For more information, see COPY STRUCTURE EXTENDED Command.
Visual FoxPro modifies the table header when you turn on or add autoincrementing for field values. For more information, see Table File Structure.
Support for Collating Sequences
In previous versions, you needed to use the SET COLLATE TO command to specify a collating sequence other than the default when creating an index or index tag. You can now specify a different collating sequence when you create or modify a table via the Indexes tab in the Table Designer and when you use the COLLATE clause and its parameter with the CREATE TABLE SQL, ALTER TABLE SQL, and INDEX commands. For more information, see Indexes Tab, Table Designer, CREATE TABLE - SQL Command, ALTER TABLE - SQL Command, and INDEX Command.
Implicit Data Conversion for SELECT...UNION SQL Command
The SELECT SQL command with the UNION option now performs implicit data conversion for data types that support implicit conversions. For example, UNION operations with columns of different lengths or that contained different types previously failed unless you explicitly matched the column sizes using a conversion function. Suppose you have the following code:
CREATE CURSOR t1 (f1 c(10))
INSERT INTO t1 VALUES ('1111111111')
CREATE CURSOR t2 (f1 c(2))
INSERT INTO t2 VALUES ('11')
SELECT * FROM t1 INTO CURSOR t3 UNION SELECT * FROM t2 && Fails.
This code failed unless you explicitly match the column sizes as shown:
SELECT * FROM t1 INTO CURSOR t3 UNION SELECT SUBSTR(f1,1,2) FROM t2
You no longer need to specify or use explicit conversion functions for data types that support implicit data conversion. For more information about data type conversion and precedence, see Data Type Conversion and Precedence in SELECT - SQL Command.
Inserting Rows from a SELECT SQL Command
You can now insert rows from a SELECT SQL command when you use the INSERT SQL command with the following syntax:
INSERT INTO dbf_name [ (fname1 [, fname2, ...] ) ]
SELECT [ (fname1 [, fname2, ...] ) ] FROM tablename WHERE condition
You can copy the contents of selected columns or all columns in a row. However, you must make sure the data you copy is compatible with the columns in the rows that you copy to. Visual FoxPro updates the _TALLY system variable with the number of rows inserted.
See Also
What's New in Visual FoxPro 8.0 | Interactive Development Environment (IDE) Enhancements | Language Enhancements | Miscellaneous Enhancements | Behavior Changes Since Visual FoxPro 7.0