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.

+++ Rick ---

>>>When developing West-Wind applications, I made the mistake of using a Multi-use com server instead of a single-use com server and a file that was supposed to be open was being closed by on of the other threads. Variables were losing values or there values were being changed. This Com server which is separate from the West-wind com server must be a single multi-use com server. We need to have one session table opened exclusively serving the data. This separate com server will prevent the data caching that was occuring with multiple single-use com servers.
>>
>>Uhm, not exactly. You should use Single Use EXE servers. multi-use EXE servers will cause all sorts of problems with overlapping memory since the same instance is getting hit by multiple simultaneous requests.
>
>But in this case when we went to single-use, we did have some problems with data caching. I had a post on your site about this a few months back. That is why we have a separate com server just serving the Session data from a table. The way we were hoping to avoid the overlapping memory problems was with the use of critical sections.