Hi

I have a problem with a component we have running under COM+ this component is set to "require a transaction" here's what it does:

- Get a cursor from customers containing about 50 000 records
- Get a cursor from Transactions containing abount 500 000 records
- Make some changes to each customers
- Copy the 500 000 transaction records to a history table (Same structure)
- Start sending back to SQL Server 2000

This transaction takes about 1 hour to finish. The problem is as long as the transaction is not comitted, a customer record which has been updated is not available. So clients querying an updated customer record will get a query timeout. What would be a better logic approach to solve this locking problem ?

Thanks.