Mike, thanks for your reply.

I use buffering extensively in new applications.
This particular project is a FPW 2.6 convert, which uses Memory Variables extensively (M.Fileldname) .

I have tested a few screens converted (There are probably 300-400 screens in total) and only o/s problem is bringing up multiple screens and use of memory variables.

If there was a way of Localizing the memory variables to the screen, this should sort the problem out... I thought if I Looped through the files and 'Privatised' all the M.fieldnames it would have worked.. maybe its the way Iam going about it.

My main query now is : Is there a way of making Memory Variables (M.fieldanme) local to each instance of a screen if I display multilpe instances at the same time ?

Regards,

Gerard







>>Typically, I have a button on the screen which Scatters Memo Memvar and all the fields have M.MyfieldX as Control Source. (At this stage, I dont want to change to Views Yet)
>
>You don't need to use views to do this. You can buffer your tables, and bind the controls directly to the tables. Then, if you'd rather cancel all the changes, you can use TableRevert() to forget all the changes in the buffer, or TableUpdate() to commit them.
>
>With a couple reusable code chunks, this is easier than it probably sounds. If you have autolinks enabled the word buffering shoudl link to a good article by John Koziol on the subject. Just an idea.