Running Querries Is Locking Out Other Users

[LadyScot101]

I created a Purchasing Database. It went live and everything is fine except when someone wants to run a query or just ran a query. It locks everyone else out that is not in and the ones that are in doesn't seem to be affected. The database has no locks set and it's set to shared. Why would it lock out people wanting to enter the database when they are running the query or ran a query? The database is out on our network. Any help would be greatly appreciated!

 

[Pat Hartman]

Is the BE Jet/ACE or SQL Server?

I'm assuming the query that is locking out the other users is an action query (insert/update/delete). A select query wouldn't lock records.

What is being updated? Can the bulk updates be scheduled for overnight? Can the bulk updates be split and run in smaller chunks?

 

[LadyScot101]

It's on a SQL Server that it's loaded on. The employees are entering orders that will create a report that is turned in for approval. It can't be done at night, it's live during the day. It's not a push. The querries are financials that are run off the data that the employee enters. Those reports are created off of querries that are pulled from the tables that the data is stored in. I did a test and had an employee go in during and after and he didn't get locked out. I talked to a guy in IT and he feels it's because they might be on different versions of Access or Win7 vs XP. I checked and they are the same systems/programs loaded on their computers, so that's not it. I don't think different models of computers would do it.

 

[Pat Hartman]

Are the queries SELECT queries or are they UPDATE queries. SELECT queries shouldn't lock out anyone unless someone has set pessimistic locks on the database and that would be very unusual.

 

[LadyScot101]

They are SELECT queries. Your right. I'm thinking it's a gliche.