>>As you are probably aware, VFP locks records in the DBC when opening a view. If multiple users access the same DBC, there can be contention and delays while VFP waits for a lock. For this reason, it is common to put a separate copy of the view DBC on each workstation. The same problem can occur with ParallelFox, but at a local level. Multiple workers (instances of the same EXE) can hit the view/DBC at the same time and cause contention issues. To work around this, I have compiled the DBC into the EXE, thinking that each worker would essentially get its own copy of the DBC. However, "Attempting to lock..." still blinks while multiple workers access the same view. Anyone know what happens behind the scenes when you compile the DBC into an EXE? Is it copying it to a temp location and sharing it across all EXEs?
>>
>>Thanks.
>
>Use CAs instead of Views :-)

Yes, that would solve the problem, but would also mean rewriting the entire app. Not feasible for us. I'll live with the contention issues if I have to, but I'm curious why compiling the DBC into the EXE didn't work.