The only reason I see to write something like m.lnVar = 3 is so that you can do searches. Personally, I only use the m prefix to diferentiate from a field. Otherwise it looks cluttered.


>It's just now starting to sink in what you were saying there. Though feel free still please to wade thru VFP samples code expecially FoxIS and tell me what you think. If m. prevents referencing a develper's field that may be named the same as a variable then I can see its usage and learned something today. Still, I haven't seen anything close to the frequency of usage of m. that MS uses as compared with yours or others' work
>Thanks