>>>Those 2 are not in the same league - mDot today is still more important than "scatter name" is.
>>
>>That is a matter of opinion, not fact. We build large commercial enterprise systems without mdot, but we do use scatter name in various places. I can't even name one instance where we had any problems with variable-fieldname related bugs in the last decade or two.
>
>embolded part was meant on snipped comparison of scatter memvar vs. mDot. mDot vs scatter name much closer and scatter name might be REALLY necessary if not using table buffering or marshalling to other vfp process - although JSON might be safer/more portable to other languages.
>
>
>>>While beauty is in eye of beholder, mDot is more than safety and speed.
>>
>>Again, I beg to differ, there technically is no need for it.
>
>Here you snipped the "mDot not for read access still necessary if ANY code by others might run inside your app" part.

If you are trying to sandbox 3rd party code, it might be better to run them in separate datasessions. unless the 3rd party brings in tables or query results into the core product code and datasessions, it is more likely the 3rd party code is going to crash rather than ours.