First of all I introduce myself my name is Javier Prieto (Capilla del Monte, Cordoba - Argentina) and attend a facility with SQLSERVER 2008 R2 STD.

On this issue I tell ...

All client pc run Visual Fox Pro9 ADODB Connection and work against the engine.

To make a reservation, according to the theory, with use the statement

SET TRANSACTION ISOLATION LEVEL SERIALIZABLE UNCOMMITTED

there should be no way that two pc try to lock a record at the same time, however happens.

I understand that if the sentence is utilizace from a stored procedure, maybe meet what I should do. But the sentence the way through ADODB and thus does not have the desired effects. In fact I did not find the way it really is serializable.

What I also came to the concept of having to add that statement is as follows:

select @Pudo=COUNT(*) from Bloqueos with (UpdLock)

With "with (UpdLock)" could greatly reduce the number of users, but I could not remove.

Maybe you know some effective technique that can be used with ADODB.:crying: