From the vfpsp3 special enhancements help(vfpsp3.chm):
"the Vfp6t.dll run time also eliminates conflicts in accessing global data from multiple threads by giving each apartment its own copy of global data. The Vfp6t.dll uses thread local storage to give each class instance its own set of data. This means that a variable you declare as PUBLIC is global only to the thread; each thread has an instance of the variable"
However, if you really want to do this, just use a dbf...

>If two clients instaniciate the same MTDLL, can one client's change to a server's property be read by the other client?