>>Depends on what you mean with "access the memo field". Maybe you have some >problem with scoping the variables - if you scatter them in one >procedure/method, and gather in another, make sure they are equally visible.
>
>Interesting point, my form has and edit button which executes an Rlock() manually on the current record, I reread with another scatter (with memo option) to ensure latest copy of the record, then provide additional button to edit the memo field. In the click event of the memo button I call another form and pass the memory variable to it with the command 'do form memEdtfrm with M.re_info'
>It's at this point I get the error..... did I goof somewhere here ?
>

Don't have the original message available at the moment (UT Nav :), so I don't remember what the error was. Further action largely depends on the memEdtfrm.init(), what does it do with the parameters passed. I also have a routine for editing memos and strings in general in a separate form (just an editbox, ok and cancel buttons), but I pass it a name expression containing the controlsource for the editbox - that is, the memo or variable name, and not its value or the variable itself. Works fine with both memos and strings.

I've posted another message today regarding some memory speculations for editing long strings in memvars vs memos (see thread "Limit the size of character variable"), you may find it useful (well, maybe at least informative :).