>>That won't solve that problem. This is not a concurrency issue that a block can help. The issue is with VFP's data caching and using a CS won't solve that problem. Basically, you either have to close and re-open that table to refresh those buffers immediately or wait long enough to guarantee the buffers get refreshed by VFP.
>
>Why would you have concurrency issue if you have only one DataSessionServer that is multi-use? We still have multiple single-use WC servers, but they get their session data from the DataSessionServer.

I didn't read the whole thread. But basically, if you're using a multi-use server you also don't need CS because those by their very nature are queued. You can't make simultaneous calls into a multi-use EXE server.

If you're using multiple WWWC instances and they're all creating DLL multi-use server instances then a CS won't help either because it's cross process and a CS only works interprocess. If this is your game then you need to use mutexes, but again this is all overkill. In the time it takes to make the COM calls and handle the Csections/mutex or whatever you could have closed and re-opened that table.

Basically, a CS is not the right way to handle this any way you look at it.

If you really have this issue at a critical piece in your code consider sticking that piece of data into a SQL server of some sort - concurrency issues can easily be handled properly there.

+++ Rick ---