> I'm working with Visual FoxPro 5.0 and I've a "little" problem using > transaction. > In my database there are several tables linked by Reference Integrity. When > I delete a record from master table > and for reference integrity there are very lot of records to update, > TableUpdate stop after having updated 500 records If I comment BEGIN / END > TRANSACTION all the records are updated. > > What can I do to solve the problem ? Is a real problem, or I've something > to set ? I found out how to kill a Novell server using a FoxPro program a few months back: Issue a SET MULTILOCKS ON and then try to issue 10,000 record locks. It will fill the memory in the server and cause it to come crashing down. It was really quite amusing. I expect this is similar to what's happening here. You're issuing a bunch of RLOCK()s as part of the transaction, and it just runs out of memory. The only option may be to rewrite the delete triggers, such that they are something like: select child do while seek(parent.key) delete enddo /Paul