>The reason why all of this is so interesting to me is that, despite all the warnings, I think I've found some reliable and useful ways to use public memory variables and other static thread-local storage within an MTDLL to substantially increase the efficiency of the MTDLL. So far, so good. And I've been doing quite a bit of experimenting.

It would be nice if Client A could set a property that Client B could look at. It would be nice if the MTDLL could "keep" a cursor or file open so that incoming requests would not have to consume resources for their own share.

Nick has a WinSoc project (a VFP Chat Server) that seems have features that could be used to mimic "shared" memeory between threads.

I can comphrend property "retention" for an instanciation. Are you saying that you have been able to transact or view information from another / separate [client] instanciation of a VFP MTDLL?