I think I know what the problem is. I created a large free table on the server and ran a query against it on two computers simultaneously, the time response was great. I think the culprit is the complex DBC. The application is Sales Commissions System, so you can imagine how complex it can be. The DBC contains 100+ files & views, and most of the forms have at least 7 tables/views (because of conditions, rules, rules, and many rules!). I'll move the views to another DBC. Also free up large history tables from the DBC that aren't required in forms. We'll see if that'll help. Maybe even free up all the tables and trash the DBC altogether! (thread #615842) I'll post the results tomorrow.

>It takes lots of users, but eventually yes. Every view record is locked each time a user runs a query. It seems though that the lock is held while the query string itself is extracted, not for the duration of running the query itself.
>
>>Great idea... I'm going to give it a try...
>>
>>Nope, my old app did not use a DBC. Multiple users accessing DBC slows it down?
>>
>>>SQL Server can be better, but I don't think it necessary here. You create your table tabledbc.DBC and store it on the server.
>>>
>>>The views.DBC contains views like this...
>>>
>>>create sql view someview as ;
>>>select field1, field2 ;
>>>from ;
>>>tabledbc!table1
>>>
>>>etc.
>>>
>>>Your old app didn't use a DBC right?
>>>
>>>>snipped<<