Hi Mike,

>Wow! I didn't know that! One more reason to use m., eh?

m. is not a optional on VFP:
1. for not ambiguous programming
2. for performance
( try to use a variable without m. and with 200 fields on the current workarea )

I donnot put m. only when use table with holes on fields list, the hole is filled by the variable with the default value.

Fabio