VFP has two realms that concern datatypes: the DBF table, and the types of variables and .value property. There are 3 differences: objects, numerics, and chars. There is no Object type of DBF field, and DBF has different kinds of numerics: integer, float, currency, etc. as where numeric variables are all stored in floating point. VFP automagically converts back and forth when it moves data between memory and disk. As far as I know this should not concern anyone – it has been this way for years, and no one has ever suggested that there are any pitfalls to be aware of.

 Moving memos to memory does the same thing, it ends up as a character variable type. — Mike Helland

Ok, I got bit: Currency’s don’t play nice with Pad L() – you have to use MtoN(). Thanks Bill

Read More

The VFP function that commits changes made to a view or buffered table to the underlying data store.

The syntax is;

TableUpdate(nRecords, lForce, cAlias, ArrayName)

nRecords is a number (0, 1, or 2) where:

0 updates only the current record

1 updates all records but stops on the first record that fails

2 update all records and will continue to update additional records after a record fails to update

(this first argument still supports the older syntax of a logical where .T. is identical to 1 and .F. the same as 0)

Read More