IIRC, FoxPro has preference for fields over variables (i.e. it searches the fields first, then memory variables later) -- so by including the m. prefix, you bypass the scanning of table fields. Although each access alone might account for a small amount of time, inside a loop these small differences may accumulate to be noticible.