I have found it helpful with legacy code that uses memvars to (1) use table buffering,(2) bind the fields to the data (3) append blank and (4) at the beginning of my tried, true, and debugged code put 'Scatter memvar' which puts the field values in the m.variabes and at the end of the code put 'Gather memvar'. I don't have any objective proof for this but I think it may be faster and it is sure easier to write 'm.myvar=something' rather than 'replace myvar with something' or 'myscreens.txtmyvar.value=something'. I may pay for this down the road but it sure feels familiar and good now.
A problem is a problem only as long as it has a possible solution. Lacking that, it becomes a FACT!