Dear Jim
Performance seems to depend on the number of fields in the currently selected table. Without the m., presumably VFP has to check field names and use the field if there is one so named.
Whether this matters will depend on the task. If the code makes dozens (? hundreds) of variable assignations in a loop with a wide table selected, developers may choose to select 0 or prefix with m. to minimise performance hit.
Anyway I was impressed that MS responded so quickly and recorded this as a Bug.
Regards
JR
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1
